I can try patching my local copy of NAnt and running it through our build torture test - 90+ projects with all sorts of inter-project and 3rd-party references. :) I may not have time to do this until next week, however.
Matt.
Ivan Tarasov wrote:
Hello Matthew,
I've fixed the current implementation of Reference.cs in VSNet-tasks project. Now it creates new AppDomain in which it tries to resolve all assemblies which are referenced from the given assembly, which are located in the same directory. Recently, all assemblies in that directory were copied.
I've tested it on our project (I was patching nightly build sources from 03.12.03) and it worked pretty well. Hope this part of code will be suitable for putting it before the 0.8.4 release (we are waiting impatiently for this release).
Patch is attached (it was "diff -C 3").
MM> (re-cc'ing the list)
MM> AppDomains allow you load/unload assemblies at will. The .NET runtime MM> tends to exhibit some odd/unpredictable behaviour as you load assemblies MM> with the same name, especially if they don't have strong names. You can MM> end up with types no longer resolving as expected. By loading MM> assemblies in the separate AppDomain, you side-step all of these issues.
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
