3. The HintPath for a reference is now checked before the AssemblyFolders. VS.NET checks it this way and it can break a solution that wants to reference (using a direct assembly reference) a different version of an assembly than might have been installed in an AssemblyFolder path.
Are you sure about this ??? I haven't checked this, but according to MS this is kind of "the last resort" ...
Guaranteed. I have a project that references an assembly (v1 of the DLL) with the same name as an assembly in one of my assembly folders (v2 of the DLL). Before my change, it was incorrectly picking up v2. After the change, it correctly picks up v1.
Even if Microsoft describes it as a last resort, it's definitely not how VS.NET does it.
Matt.
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
