Hi guys... I've been updating tonight the NAntContrib code to use the new NUnit2 tests, and quite quickly ran into a gotcha with the new assemblyname attibute: It is exactly that, an assembly name, and cannot take an assembly _file_ name.
In fact, the build files for nant itself pass in an assembly file name instead of just an assembly name, which is wrong, and happens to work just because of sheer luck. The reason for this problem is that, deep inside, the nunit2 task ends up calling the Load() method of NUnit's TestSuiteBuilder code, which has, imho, a horrible problem: It indeed takes an assembly name instead of an assembly file name... a terrible design mistake in my opinion, though. Of course, the problem is that TestSuiteBuilder::Load() calls AppDomain::Load() inside, instead of doing the more sensible thing, which would be an Assembly::LoadFrom(). Of course, without this, the nunit2 assemblyname attribute is useless unless the DLL containing the test classes is also located _in the same directory as nant's binaries_. Then again, this is just my opinion. I don't know anything about NUnit's internals, nor do I know what they pretended to do, but right now, this doesn't look good and puts a bit of a showstopper in nant :( -- Tomas Restrepo [EMAIL PROTECTED] ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
