Saxon

Legacy ID: #7997327 Legacy Poster: Michael Kay (mhkay)

In Saxon 9.1 on .NET, the Saxon-SA code (specifically the SchemaAwareConfiguration class mentioned in the error message) is loaded dynamically from a separate DLL (saxon9sa.dll). I find that the only reliable way to make this work is to ensure that this DLL is in the Global Assembly Cache. Once it is, I've rarely had any problems. (Though there are a million and one ways that dynamic loading can fail under .NET once you start building complex security environments.)

Legacy ID: #7997349 Legacy Poster: Pooja (psha85)

Oh okay.. and how would I add it to the Global Assembly Cache? I've never even heard of that actually... lol. Thanks for your help!

Legacy ID: #7998040 Legacy Poster: Michael Kay (mhkay)

Go to Control Panel > Administrative Tools > Microsoft .NET Configuration > Manage the Assembly Cache > Add an Assembly. Then select the relevant assemblies. It's simplest to add ALL the assemblies (.dll files) issued with the Saxon product, that is, both the Saxon assemblies and the IKVM / Classpath assemblies.

Legacy ID: #7999726 Legacy Poster: Pooja (psha85)

Okay, I did what you said about the assembly cache and then tried the Transform tool again, but got the same result. Is it necessary to restart the computer or something before trying it again? Or should it have worked without that?

Legacy ID: #7999854 Legacy Poster: Michael Kay (mhkay)

No, I've never had to reboot to make this work. Can you list the contents of the GAC (from the same Configuration tool) to check that saxon9sa.dll is in there with matching version number (9.1.0.8) and PublicKeyToken? I'm afraid it's very frustrating when these things don't work, and very hard to debug remotely.

Legacy ID: #7999948 Legacy Poster: Pooja (psha85)

I see two: saxon9 and saxon9api. I'm assuming saxon9 is the one you mentioned...? And yes they have the same version number and public key token. Indeed, it is very frustrating!

Legacy ID: #8000651 Legacy Poster: Michael Kay (mhkay)

The class it's trying to load, SchemaAwareConfiguration, is in saxon9sa.dll - this should be in the GAC along with saxon9.dll and saxon9api.dll. It's occurred to me that you might not be using Saxon-SA at all. If that's the case, don't use the -sa option on the command line. Apologies if that's the solution and it didn't occur to me earlier.

Legacy ID: #8001945 Legacy Poster: Pooja (psha85)

I tried not typing the -sa option in the command line but I got another error. And I don't see the saxon9sa.dll file anywhere. I did a search on my computer but it didn't find it either. I tried installing the Enterprise Edition of Saxon and added those assemblies to the cache (but none of which included saxon9sa.dll). I again tried it with the -sa option and without but then I got an error about a licensing file not being found... I ordered an evaluation copy of Saxon EE but have not received the licensing key yet. I will try it after I receive that and see if it works...

Legacy ID: #8002205 Legacy Poster: Michael Kay (mhkay)

OK, so the original problem was that you were using Saxon-B 9.1, you used the -sa option and it didn't work because that option attempts to load Saxon-SA 9.1. So now you have installed Saxon-EE 9.2, which is the successor to Saxon-SA 9.1. This product needs a license file which you have now applied for and which hopefully has now been delivered to you.

Legacy ID: #8002235 Legacy Poster: Pooja (psha85)

Okay, I got the program to work now. Looks like downloading the EE version and the license fixed the problem. Thanks for your help! =)