I'm learning NHibernate, and I am at the point where I can get a simple app up and running with NHibernate 1.2. Right now, I'm playing with SchemaExport, which I normally invoke from the unit test project in a VS 2008 solution.

I've created a simple GUI wrapper to run SchemaExport. The GUI references its own copy of NHibernate, and it uses the cfg.Configure() overload that lets me specify the config file to use:



I am using as my target a project with a known working configuration file and mapping files. But when I invoke cfg.Configure() per above, I get this error from NHibernate:



The InnerException reads:



In other words, NHibernate finds the assembly from the config file when I run MyDemo, but it doesn't find it if I use my GUI to load the config file.

While learning NHibernate, I've read that the config file must be in the project output folder of the application calling NHibernate--in this case my GUI. That would explain why NHibernate finds the assembly when I run MyDrmo but not the GUI.

Can anyone shed any light on this problem? How do I get around it? Thanks for your help.

David Veeneman
Foresight Systems

Answered my own question. The solution turnsout to be fairly simple, if one configures NHibernate from code, using the SetProperty() or SetProperties() methods. For my GUI, that turns out to be what I want to do anyway. The assembly with the mapping files is added to the configuration using the AddAssembly() method.

Once I have the GUI app working, I am planning to post it on CodeProject.com, so you might check there for the utility.