Its honestly doubtful that you will simplify whatever you issue is by GAC-ing the NH bins; if anything that will make troubleshooting this *more* difficult as it will give you yet another location from which your app/tests can pull its dependencies. I recommend using the Fusion Log Viewer to capture the failed assembly resolution in order to determine why its not being found by the MSTest Runner where you claim it should be located.
Steve Bohlen [email protected] http://blog.unhandled-exceptions.com http://twitter.com/sbohlen On Fri, Jul 1, 2011 at 4:03 PM, Matteo Migliore <[email protected]>wrote: > I've to use MSTest with MSBuild and TFS, we are in a CI environment so all > is automated :). > > On the development machines all work, on the server each build clean the > workspace, so the build is "perfect" every time. We have the problem only on > the server. > > I checked also that the TestResults contains all NH assemblies and it is so > and I also checked that the test assembly contains the references using > Reflector. > > I also run the test in local on multiple machines in Debug and Release > mode. The C# compiler remove all references to unused assemblies (not > directly referenced by any time in the project) so I created a Fake<T> class > to pass a type for each assembly (Nhibernate, Iesi, Castle, ConfOrm etc...). > > At least I've to try to put NH in the GAC of the build server. > > Thanks!
