Merge pull request #1 from imdj360/xsltnschange

Release v1.0.0: XSLT 1.0 Support and Namespace Improvements

Author: imdj360

.gitignore

@@ -1,4 +1,5 @@
 out
+**/out/
 dist
 node_modules
 .vscode-test/
@@ -13,6 +14,7 @@ obj/
 *.log
 *.tmp
 *.out.xml
+**/*.out.xml
 
 # OS generated files
 .DS_Store

.vscodeignore

@@ -5,10 +5,14 @@ src/**
 .vscodeignore
 .yarnrc
 vsc-extension-quickstart.md
+package.json.backup
+TestData/**
+docs/**
 **/tsconfig.json
 **/eslint.config.mjs
 **/*.map
 **/*.ts
+**/*.sh
 **/.vscode-test.*
 .github/**
 
@@ -69,6 +73,9 @@ logs
 npm-debug.log*
 yarn-debug.log*
 yarn-error.log*
+*.out.xml
+**/*.out.xml
+TestData/**/out/**
 
 # Node modules (should be handled by vsce, but just in case)
 node_modules/**
@@ -116,3 +123,6 @@ VARIABLE-PRINT-GUIDE.md
 # Packaging scripts
 package-darwin.sh
 package-win.sh
+package-all.sh
+test-debug-output.sh
+test-namespace-support.sh

CHANGELOG.md

@@ -2,6 +2,25 @@
 
 All notable changes to the XSLT Debugger extension will be documented in this file.
 
+## [1.0.0] - 2025
+
+### Added
+
+- Shared XSLT 1.0 instrumentation helper used by both engines so Saxon can now debug XSLT 1.0 stylesheets that do not rely on `msxsl:script`.
+- Version-aware Saxon pipeline that switches to the 1.0-safe probes while retaining the existing XSLT 2.0/3.0 instrumentation.
+- Integration coverage for the new Saxon 1.0 path (`SaxonEngine_ShouldCaptureVariables_WhenRunningXslt1Stylesheet`) and console smoke tests for both engines.
+
+### Changed
+
+- Reorganised integration samples under `TestData/Integration/xslt/compiled/` and `TestData/Integration/xslt/saxon/` to mirror the engine split.
+- XsltCompiledEngine now delegates all 1.0 probe insertion to the shared helper, keeping instrumentation logic in one place.
+- Bumped the extension version to `1.0.0` and updated packaging docs to reference the new VSIX build numbers.
+- `.gitignore` / `.vscodeignore` now filter generated `out/` folders and `*.out.xml` artifacts across the tree.
+
+### Fixed
+
+- Ensured Saxon 1.0 runs produce the same breakpoint and variable capture behaviour as the compiled engine by reusing the same probe shapes.
+
 ## [0.6.0] - 2025
 
 ### Added

README.md

@@ -8,25 +8,25 @@ A powerful Visual Studio Code extension that enables debugging support for XSLT
 - **Variable Inspection**: Automatically materialises XSLT variables and context nodes inside VS Code’s VARIABLES pane
 - **XPath Evaluation**: Evaluate XPath expressions in the current context
 - **Inline C# Scripting**: Debug XSLT stylesheets with embedded C# code using Roslyn
-- **Multiple Engines**: Support for compiled XSLT engine (XSLT 1.0) and Saxon engine (XSLT 2.0/3.0)
+- **Multiple Engines**: Support for compiled XSLT engine (XSLT 1.0 + inline C#) and Saxon engine (XSLT 1.0 without `msxsl:script`, plus XSLT 2.0/3.0)
 - **Cross-Platform**: Works on Windows, macOS, and Linux
 - **Probe Tagging**: Instrumented breakpoints and trace messages are tagged with `dbg:probe="1"` so repeated runs stay idempotent
 
 ## XSLT Processing Engines
 
-| Feature           | Compiled Engine                  | Saxon .NET Engine                    |
-| ----------------- | -------------------------------- | ------------------------------------ |
-| **XSLT Version**  | 1.0                              | 2.0, 3.0                             |
-| **XPath Version** | 1.0                              | 2.0, 3.0                             |
-| **Special Features** | Inline C# via `msxsl:script`  | Full XSLT 2.0/3.0 features           |
-| **Best For**      | XSLT 1.0 with inline C#          | Modern XSLT 2.0/3.0 stylesheets      |
+| Feature           | Compiled Engine                  | Saxon .NET Engine                                    |
+| ----------------- | -------------------------------- | ---------------------------------------------------- |
+| **XSLT Version**  | 1.0                              | 1.0 (no inline C#), 2.0, 3.0                         |
+| **XPath Version** | 1.0                              | 2.0, 3.0                                             |
+| **Special Features** | Inline C# via `msxsl:script`  | Full XSLT 2.0/3.0 features, version-aware probes     |
+| **Best For**      | XSLT 1.0 with inline C#          | XSLT 1.0 without `msxsl:script`, plus 2.0/3.0 stylesheets |
 
-**Engine Selection**: Auto-detected based on XSLT version, or manually set with `"engine": "compiled"` or `"engine": "saxonnet"` in launch.json
+**Engine Selection**: Auto-detected based on XSLT version and inline script usage, or manually set with `"engine": "compiled"` or `"engine": "saxonnet"` in launch.json
 
 ### ⚠️ Current Limitations
 
 - Debugging focuses on basic XSLT structures (templates, loops, expressions); complex dynamic calls are not instrumented
-- Cannot step into inline C# scripts
+- Cannot step into inline C# scripts, though Roslyn instrumentation still logs entry parameters and return values to the console for visibility
 - Variable inspection uses "falldown" approach: variables are auto-captured via instrumentation as execution progresses forward (cannot re-run or step back to previous lines)
 - No support for: **step back**, goto targets, set variable, conditional breakpoints, or debug console autocomplete
 - Variable capture limited to `@select`-based variables; complex variables with content children may not be fully captured
@@ -49,10 +49,10 @@ A powerful Visual Studio Code extension that enables debugging support for XSLT
 
    ```bash
    # macOS
-   code --install-extension xsltdebugger-darwin-darwin-arm64-0.6.0.vsix
+   code --install-extension xsltdebugger-darwin-darwin-arm64-1.0.0.vsix
 
    # Windows
-   code --install-extension xsltdebugger-windows-win32-x64-0.6.0.vsix
+   code --install-extension xsltdebugger-windows-win32-x64-1.0.0.vsix
    ```
 
 2. **Create a debug configuration** in [.vscode/launch.json](#setting-up-a-debug-configuration)
@@ -81,19 +81,19 @@ A powerful Visual Studio Code extension that enables debugging support for XSLT
 
    ```bash
    ./package-all.sh
-   code --install-extension xsltdebugger-darwin-darwin-arm64-0.6.0.vsix
+   code --install-extension xsltdebugger-darwin-darwin-arm64-1.0.0.vsix
    ```
 
    **Platform-specific packaging** (build individually):
 
    ```bash
    # For macOS only
    ./package-darwin.sh
-   code --install-extension xsltdebugger-darwin-darwin-arm64-0.6.0.vsix
+   code --install-extension xsltdebugger-darwin-darwin-arm64-1.0.0.vsix
 
    # For Windows only
    ./package-win.sh
-   code --install-extension xsltdebugger-windows-win32-x64-0.6.0.vsix
+   code --install-extension xsltdebugger-windows-win32-x64-1.0.0.vsix
    ```
 
 ## Usage
@@ -202,7 +202,8 @@ Create a `.vscode/launch.json` file in your project workspace:
 - **Falldown Approach**: Variables appear in the Variables panel as execution flows forward past their declarations (not available before declaration)
 - **No Step Back**: Since variables are captured via forward instrumentation, you cannot step backward to re-inspect previous values
 - **XSLT 2.0/3.0**: Full support via Saxon engine with `@select`-based variable capture
-- **XSLT 1.0**: Limited variable inspection via Compiled engine
+- **XSLT 1.0 (no inline C#)**: Saxon engine reuses 1.0-safe probes (value-of/message) for equivalent capture behaviour
+- **XSLT 1.0 + inline C#**: Limited variable inspection via Compiled engine only
 
 ### Log Levels
 
@@ -254,7 +255,7 @@ The debugger supports XSLT stylesheets with embedded C# code using `msxsl:script
 
 - **Extension** ([src/extension.ts](src/extension.ts)): Registers debug type, resolves paths
 - **Adapter** ([XsltDebugger.DebugAdapter/](XsltDebugger.DebugAdapter/)): DAP server, engine management, breakpoint/stepping logic
-- **Engines**: `XsltCompiledEngine` (XSLT 1.0 + C#), `SaxonEngine` (XSLT 2.0/3.0)
+- **Engines**: `XsltCompiledEngine` (XSLT 1.0 + C#), `SaxonEngine` (XSLT 1.0 without `msxsl:script`, plus 2.0/3.0)
 - **Instrumentation**:
   - Breakpoints: Both engines inject `dbg:break()` extension function calls at breakpoint lines
   - Variables: Saxon engine injects `<xsl:message>` elements after variable declarations to auto-capture values

TestData/Integration/AdvanceFile.xml TestData/Integration/xml/AdvanceFile.xmlTestData/Integration/AdvanceFile.xml renamed to TestData/Integration/xml/AdvanceFile.xml

@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<ShipmentConfirmation>
+  <Reference>REF-12345</Reference>
+  <Net>1500.50</Net>
+  <LicensePlate>ABC-123</LicensePlate>
+  <Orders>
+    <Number>ORD-001</Number>
+    <CustomerName>Acme Corporation</CustomerName>
+    <Date>2025-10-31 14:30:00</Date>
+    <OrderItems>
+      <Sequence>1</Sequence>
+      <OperationCode>SHIP</OperationCode>
+    </OrderItems>
+    <OrderItems>
+      <Sequence>2</Sequence>
+      <OperationCode>LOAD</OperationCode>
+    </OrderItems>
+  </Orders>
+</ShipmentConfirmation>

TestData/Integration/ItemsSample.xml TestData/Integration/xml/ItemsSample.xmlTestData/Integration/ItemsSample.xml renamed to TestData/Integration/xml/ItemsSample.xml

@@ -0,0 +1,50 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<ns0:ShipmentConfirmation xmlns:ns0="http://www.example.com/ShipmentConfv2">
+  <ns0:TransportTypeCode>TRUCK</ns0:TransportTypeCode>
+  <ns0:TransportTypeDescription>Truck</ns0:TransportTypeDescription>
+  <ns0:TransportMode>Road</ns0:TransportMode>
+  <ns0:Direction>Outbound</ns0:Direction>
+  <ns0:Reference>REF-REDACTED</ns0:Reference>
+  <ns0:Arrival>2025-07-15T08:30:00Z</ns0:Arrival>
+  <ns0:Departure>2025-07-15T10:45:00+02:00</ns0:Departure>
+  <ns0:LicensePlate>PLATE-REDACTED</ns0:LicensePlate>
+  <ns0:Net Currency="USD">12500.756</ns0:Net>
+  <ns0:Status>Approved</ns0:Status>
+
+  <ns0:Orders>
+    <ns0:Number>ORD-XXXX</ns0:Number>
+    <ns0:Date>2025-07-15T00:00:00</ns0:Date>
+    <ns0:CustomerCode>CUST-XXXX</ns0:CustomerCode>
+    <ns0:CustomerName>LogicApps - iPaaS Tool Helper</ns0:CustomerName>
+    <ns0:OrderItems>
+      <ns0:Sequence>10</ns0:Sequence>
+      <ns0:OperationName>Load truck</ns0:OperationName>
+      <ns0:OperationCode>LD</ns0:OperationCode>
+      <ns0:OperationReports>
+        <ns0:ReportInfo>
+          <ns0:OperationReportDate>2025-07-14T12:00:00</ns0:OperationReportDate>
+        </ns0:ReportInfo>
+        <ns0:ReportInfo>
+          <ns0:OperationReportDate>2025-07-13T09:00:00</ns0:OperationReportDate>
+        </ns0:ReportInfo>
+        <ns0:ReportInfo>
+          <ns0:OperationReportDate>2025-06-15T06:30:00</ns0:OperationReportDate>
+        </ns0:ReportInfo>
+      </ns0:OperationReports>
+    </ns0:OrderItems>
+
+    <ns0:OrderItems>
+      <ns0:Sequence>20</ns0:Sequence>
+      <ns0:OperationName>Second load</ns0:OperationName>
+      <ns0:OperationCode>LD2</ns0:OperationCode>
+      <ns0:OperationReports>
+        <ns0:ReportInfo>
+          <ns0:OperationReportDate>2023-07-12</ns0:OperationReportDate>
+        </ns0:ReportInfo>
+        <ns0:ReportInfo>
+          <ns0:OperationReportDate>2025-07-16T00:00:00</ns0:OperationReportDate>
+        </ns0:ReportInfo>
+      </ns0:OperationReports>
+    </ns0:OrderItems>
+  </ns0:Orders>
+</ns0:ShipmentConfirmation>