This video demonstrates use of Saxon-JS tasks for running XSLT 3.0. Please note that NodeJS should be installed you your machine to use Saxon-JS. NodeJS can be installed from here: nodejs.org/en/download/
Please may i know your email contact. I am facing the below issue. everything is configured as per the steps shown by you /usr/bin/bash: -c: line 0: unexpected EOF while looking for matching `"' /usr/bin/bash: -c: line 1: syntax error: unexpected end of file The terminal process "C:\Program Files\Git\bin\bash.exe '-c', '"E:\XSLTProjs/node_modules\.bin\xslt3" "-xsl:E:\XSLTProjs\SRC\Demo.xsl" "-s:E:\XSLTProjs\SRC\Demo.xsl" "-o:E:\XSLTProjs/xslt-out/result1.xml"'" failed to launch (exit code: 1).
I tried following the steps on Windows/WSL... by no means I managed to make the tasks run on WSL instead of powershell. So I ended up having to install NodeJS directly on Windows.
First of all that is an awesome video tutorial. Question do you get in touch with xspec? If yes, do you know how to use xspec with that Visual Studio code extension? Thank you.
Thanks for creating this awesome video. It has helped me a lot. Can you also tell me how can I run a Azure CI pipeline and having this XSLT as a task ?
You can create Compound tasks to achieve this. Create a task with a dependsOn property with a list of tasks for different XML files. See: code.visualstudio.com/docs/editor/tasks#_compound-tasks If you need to process an entire folder, use a top-level XSLT stylesheet that calls the collection function with the folder Uri as the argument, the folder-uri can be passed as an xsl:param from the task. See: www.saxonica.com/documentation11/index.html#!sourcedocs/collections
It is possible to use variable references to use user-input in your XSLT task file. For more info see: code.visualstudio.com/docs/editor/variables-reference#_input-variables
Hi Philip, got the following error message in the terminal when trying to run the xsl: "The terminal process failed to launch: A native exception occurred during launch (Cannot create process, error code: 193)." Do you know what the problem could be?
Looking closer at your error message, a likely cause is that NodeJS is not installed on your machine,. The 'xslt3' node-module that the task attempts to execute is not recognised as an executable script. To fix this, install NodeJS on your machine. NodeJS can be installed from here: nodejs.org/en/download/
Someone else has also reported this issue (github.com/DeltaXML/vscode-xslt-tokenizer/issues/66). Further investigation showed this was a bug that occurred when using Saxon-JS with the Windows OS. This issue was fixed in V0.2.9 of the extension.
Check the tasks.json in your workspace folder has result.html set as the output file. You should see confirmation of this in the terminal output in VSCode (ensuring no error is reported there). If the issue persists please submit an issue at github.com/DeltaXML/vscode-xslt-tokenizer/issues with more details.
![Quando Rondo - Life Goes On [Official Music Video]](http://i.ytimg.com/vi/eIf3fhMXAow/mqdefault.jpg)
This video demonstrates use of Saxon-JS tasks for running XSLT 3.0. Please note that NodeJS should be installed you your machine to use Saxon-JS.
NodeJS can be installed from here: nodejs.org/en/download/
Please may i know your email contact. I am facing the below issue. everything is configured as per the steps shown by you
/usr/bin/bash: -c: line 0: unexpected EOF while looking for matching `"'
/usr/bin/bash: -c: line 1: syntax error: unexpected end of file
The terminal process "C:\Program Files\Git\bin\bash.exe '-c', '"E:\XSLTProjs/node_modules\.bin\xslt3" "-xsl:E:\XSLTProjs\SRC\Demo.xsl" "-s:E:\XSLTProjs\SRC\Demo.xsl" "-o:E:\XSLTProjs/xslt-out/result1.xml"'" failed to launch (exit code: 1).
I tried following the steps on Windows/WSL... by no means I managed to make the tasks run on WSL instead of powershell. So I ended up having to install NodeJS directly on Windows.
is it possible to convert a json file to xml using XSLT3.0. ? Is so, please share a link
Thanks my G, helped out a lot...
First of all that is an awesome video tutorial. Question do you get in touch with xspec? If yes, do you know how to use xspec with that Visual Studio code extension? Thank you.
There is no XSpec support currently, it will be added in the near future.
Dude, I just want to know how to transform xml with xslt in vscode. Should be a 3 minute video.
Thanks for creating this awesome video. It has helped me a lot. Can you also tell me how can I run a Azure CI pipeline and having this XSLT as a task ?
Thanks for the tutorial. How would I go about processing multiple XML files (or all XML files in a folder) in a single build task?
You can create Compound tasks to achieve this. Create a task with a dependsOn property with a list of tasks for different XML files. See: code.visualstudio.com/docs/editor/tasks#_compound-tasks
If you need to process an entire folder, use a top-level XSLT stylesheet that calls the collection function with the folder Uri as the argument, the folder-uri can be passed as an xsl:param from the task. See: www.saxonica.com/documentation11/index.html#!sourcedocs/collections
Thanks very much
It isn't generating the proper xml file, Please help and what if I need to assign source files dynamically?
It is possible to use variable references to use user-input in your XSLT task file. For more info see: code.visualstudio.com/docs/editor/variables-reference#_input-variables
Hi iam trying to use saxon integrated extension but getting error like 2 arguments function could not be found
Hi Philip, got the following error message in the terminal when trying to run the xsl: "The terminal process failed to launch: A native exception occurred during launch (Cannot create process, error code: 193)." Do you know what the problem could be?
Looking closer at your error message, a likely cause is that NodeJS is not installed on your machine,. The 'xslt3' node-module that the task attempts to execute is not recognised as an executable script. To fix this, install NodeJS on your machine. NodeJS can be installed from here: nodejs.org/en/download/
Someone else has also reported this issue (github.com/DeltaXML/vscode-xslt-tokenizer/issues/66). Further investigation showed this was a bug that occurred when using Saxon-JS with the Windows OS. This issue was fixed in V0.2.9 of the extension.
Hi! I tried to repeat after you on my computer. the "result.html" file is created empty. what could be the problem?
Check the tasks.json in your workspace folder has result.html set as the output file. You should see confirmation of this in the terminal output in VSCode (ensuring no error is reported there). If the issue persists please submit an issue at github.com/DeltaXML/vscode-xslt-tokenizer/issues with more details.