I have class library project that handles the NHibernate interface, including the loading the mapping file (*.hbm.xml) via the Configuration.AddAssembly method. I'm passing the assembly name as a parameter.

When the project DLL is referenced in another Win EXE project, and the library executes the AddAssembly method, a security exception results:

"That assembly does not allow partially trusted callers."

The EXE project is set to Full Trust, and I tried adding [assembly: AllowPartiallyTrustedCallers] to the class library.

Does anyone have any suggestions on how to access an embedded resource like this from a referenced DLL?

Thanks.

Is your DLL also set to full trust? If you're using .NET 2.0 then more information should be available in the SecurityException (FailedAssemblyInfo property). In case the failing assembly turns out to be NHibernate, you can recompile it with the AllowPartiallyTrustedCallers attribute, but note that this is generally insecure (somebody might map a security-sensitive class using NH and manipulate it through NH).

I am using .Net 2.0. The failed assembly info indicates only System.Security.SecurityException. The property pages for the class library projects don't appear to have a section on setting security at that level, like the the EXE project does.

I started down the path of compiling NHibernate in 2.0, but did not want to fuss with signing at this stage in the development process.

I rebuilt everything on another machine in .Net '03, and it works fine. I'm getting a bit frustrated with .Net 2.0. I have to disable the Debugging in the Visual Studio hosting process because the IDE throws an error every time an app is rerun after an exception (VSHoste.exe is in use). You have to restart the IDE every time. Plus, I cannot step into the class library to debug it, even though everything is compiled in debug mode. All of this works under the old version of .NET.

Anyway, any further suggestions would be appreciated.