我需要从一个传统的VB6应用程序调用XSLT 2.0转换。我有一个与撒克逊人的命令行版本非常好的previous经验，所以我决定给萨克森的.NET版本一试。这是我与COM / .NET互操作机制的第一次严重的经验，不幸的是，我都快企图使撒克逊.NET提供给我的VB6应用程序失败：根据撒克逊和.NET，我试过了，撒克逊API的版本类要么似乎没有工作或没有，即使在对象浏览器中显示出来。

I need to invoke XSLT 2.0 transformations from a legacy VB6 application. I had a very good previous experience with the command line version of Saxon, so I decided to give the Saxon's .NET version a try. This is my first serious experience with COM/.NET interoperation mechanism and, unfortunately, all my quick attempts to make Saxon .NET available to my VB6 application have failed: depending on the versions of Saxon and .NET that I tried, the Saxon API classes either don't seem to work or don't even show up in Object Browser.

我真的AP preciate，如果你们任何人会分享你的成功经验，利用撒克逊.NET从VB6 / VBA6应用程序（或任何其他COM应用程序）。这将是巨大的，知道哪些撒克逊和.NET的特定版本已经为你工作，而具体的撒克逊组件必须注册COM / .NET互操作。转型与参数的简单VB6 code的例子就是在这个蛋糕巨大结​​冰。 ：）

I would really appreciate it if any of you would share your successful experience with using Saxon .NET from a VB6/VBA6 application (or any other COM application). It would be great to know which specific versions of Saxon and .NET had worked for you, which specific Saxon assemblies had to be registered for COM/.NET interop. A simple VB6 code example of transformation with a parameter would be a great icing on this cake. :)

感谢您！

推荐答案

在Windows上，如果你想使用COM和XSLT 2.0的话，我会考虑AltovaXML还是现在猛禽从Altova的，他们提供的COM自动化：的http://manual.altova.com/RaptorXML/raptorxmlserver/index.html?rxcomnet_aboutcom.htm.例子是的http://manual.altova.com/RaptorXML/raptorxmlserver/index.html?rxcomnet_$c$cex_vbscript01.htm VBScript的。我不认为写的，并为.NET Framework的应用程序适用于COM自动化除非开发商在需要的 http://msdn.microsoft.com/en-US/library/zsfww439%28v=vs.80%29.aspx 所以我不'T认为有撒克逊人的.NET版本将只允许你使用它的COM自动化。

On Windows if you want to use COM and XSLT 2.0, then I would consider AltovaXML or now Raptor from Altova, they offer COM automation: http://manual.altova.com/RaptorXML/raptorxmlserver/index.html?rxcomnet_aboutcom.htm. Example is at http://manual.altova.com/RaptorXML/raptorxmlserver/index.html?rxcomnet_codeex_vbscript01.htm for VBScript. I don't think an application written with and for the .NET framework is suitable for COM automation unless the developer takes steps described in http://msdn.microsoft.com/en-US/library/zsfww439%28v=vs.80%29.aspx so I don't think having the .NET version of Saxon will simply allow you to use it with COM automation.