Building from inside VS is *not* a 'supported' way to produce NH binaries for subsequent use in other projects. As you have discovered, there are several differences in the compilation process, etc. between the NANT scripts (what is really being invoked by the ShowBuildMenu.bat process) and the settings inside the sln and csproj files that the VS-based compile-build cycle is responding to.
Its best to consider a VS-initiated build as pretty much only useful/trustworthy for the sake of running unit tests and to consider the NANT-based builds to be the 'authoritative' way to provide 'externally-usable' NH binaries (either for official release or for your own 'private' use as 'trunk build'). There are several differences between what MSBUILD is doing and what NANT is doing and while you could pick through them one at a time to discover all the nuances, my recommendation is just to rely upon the 'appropriate' build process for the matching need(s) you have and to ensure that you're using the NANT scripts if you want to produce 'consumable' binaries for your own needs. Hope this helps, Steve Bohlen [email protected] http://blog.unhandled-exceptions.com http://twitter.com/sbohlen On Mon, Dec 19, 2011 at 6:24 PM, DBLWizard <[email protected]> wrote: > Howdy, > > Has anybody encountered this issue? if you use the "ShowBuildMenu" to > build the NHibernate libraries it builds differently than if you open > the NHibernate.Everything.sln and build. When I build with the > ShowBuildMenu then everything is fine. But when I build with solution > file I get issue raised in the following link: > > http://groups.google.com/group/nhibernate-development/browse_thread/thread/5a4ebc41ec535798 > > Does anybody have any thoughts? > > Thanks > > dbl > I >
