|
|
Rank: Newbie
Joined: 6/17/2009
Posts: 2
|
I realize it's not your fault that Microsoft.NET has chosen to play games rather than abide by the W3C standards regarding XML and related technologies. So, please don't take this as personal criticism.
But the reality is that I use XML Spy to create my XSL. I love the user interface and debugging capabilities. But as soon as I take XSL which work fine in XML Spy and try to use them in Visual Studio, it's a gamble whether or not they will actually port.
I have to write code for .NET. So, I'd love to use XML Spy's IDE usability and be confident that my code will work in .NET (an example, .NET's ordinal positioning is all wrong - the first node is actually at node position 2 and the second node is actually at node position 4).
Can you please do us a giant favor? Just as you've written the IDE such that it can create XSL 1.0 and XSL 2.0 stylesheets, can you give us another option to write whatever it is Microsoft's version of XSL/XPath is using? Elsewise, I have to manually convert back and forth whenever I make changes to my XSL/XPath statements (Visual Studio's IDE capabilities for XSL/XPath are a distant second compared to XML Spy's, so sticking to Visual Studio's IDE isn't a preferred option either).
|
|
Rank: Advanced Member
Joined: 12/13/2005
Posts: 2,856
Location: Mauritius
|
Two questions in this regard: did you try to use AltovaXML .NET for your transformations instead of Microsoft's implementation? And as opposite - did you try to setup MSXML as XSLT engine in XMLSpy instead of the default one from Altova?
|
|
Rank: Newbie
Joined: 6/17/2009
Posts: 2
|
Yes, I have set Tools->Options->XSL->MSXML (Choose version automatically)
No, I can't use the Altova XMLSpy processor for production (we work in security and there's a stack of procedures we have to go through to get new 3rd party software installed in production).
|
|
Rank: Guest
Joined: 12/13/2005
Posts: 0
|
Yes,cleary!
|
|
|
guest |
