Wrox Programmer Forums
Go Back   Wrox Programmer Forums > XML > XSLT
|
XSLT General questions and answers about XSLT. For issues strictly specific to the book XSLT 1.1 Programmers Reference, please post to that forum instead.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the XSLT section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old July 10th, 2003, 04:03 PM
Authorized User
 
Join Date: Jul 2003
Posts: 10
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Thanks for your help and patience.
 
Old July 11th, 2003, 03:47 PM
Authorized User
 
Join Date: Jul 2003
Posts: 10
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Unfortunately, I got too excited too quickly. The transformation did not occur, it only opened my xml document.

Here's my command line from c:\msxsl (xml and xsl docs are in this directory)
"msxsl momandpop.xml order.xsl
Error - 'msxsl' is not recognized as an internal or external command, operable program or batch file.

What am I doing wrong?
 
Old July 12th, 2003, 03:19 AM
joefawcett's Avatar
Wrox Author
 
Join Date: Jun 2003
Posts: 3,074
Thanks: 1
Thanked 38 Times in 37 Posts
Default

If you are sure that msxsl.exe is on your machine, I suggest searching the c drive to be sure then you have a number of options including:
1) Navigate to the folder where msxsl.exe is in a command prompt window and type:
msxsl <full path to xml file> <full path to xsl file>
2) Navigate to the folder where xml/xsl files are in a command prompt window and type:
<full path to msxsl.exe> myFile.xml myFile.xsl
3) Alter your PATH environment variable to include the folder where msxsl.exe resides then you can navigate to the folder where xml/xsl files are in a command prompt window and type:
msxsl myFile.xml myFile.xsl




--

Joe
 
Old July 16th, 2003, 10:22 AM
Authorized User
 
Join Date: Jul 2003
Posts: 10
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Finally got it working. Thanks for the help!
 
Old November 7th, 2003, 01:52 PM
Registered User
 
Join Date: Nov 2003
Posts: 5
Thanks: 0
Thanked 0 Times in 0 Posts
Default

When he says it should be in your 'System' folder, doesn't he mean it should be in your 'System32' folder? I tried this today and it worked.
K





Similar Threads
Thread Thread Starter Forum Replies Last Post
node-set() -- moving from msxsl to saxon, etc. tripecac XSLT 24 May 4th, 2007 01:52 PM
Server.Mappath in <msxsl:script jvleuten XSLT 0 February 6th, 2006 09:20 AM
MSXSL is not recognized as an internal or external GLSmyth XML 2 October 6th, 2005 10:36 AM
MSXSL brawtaman XSLT 1 September 3rd, 2004 04:19 AM
Xslt debugger tools dealing with <msxsl:script> Fero XSLT 2 March 4th, 2004 11:00 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.