Re: [nant-dev] Solution task fixes + speedups
- Original Message - From: "Matthew Mastracci" <[EMAIL PROTECTED]> To: "Gert Driesen" <[EMAIL PROTECTED]> Cc: "Nant-Developers (E-mail)" <[EMAIL PROTECTED]> Sent: Tuesday, March 16, 2004 11:05 PM Subject: Re: [nant-dev] Solution task fixes + speedups > Gert Driesen wrote: > > >>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. But you actually have two different "assembly folders" : you have the assembly folder that is referenced in your project file using the "AssemblyFolderKey" attribute of the element, eg. and you have the rest of the AssemblyFolder registry keys. Perhaps VS.NET first checks the AssemblyFolderKey, then the HintPath and then the rest of the assembly folders. But I'm just guessing here. > > Even if Microsoft describes it as a last resort, it's definitely not how > VS.NET does it. I'll verify it tomorrow, and report it to MS if necessary Gert --- 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
Re: [nant-dev] Solution task fixes + speedups
Gert Driesen wrote: 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
Re: [nant-dev] Solution task fixes + speedups
- Original Message - From: "Matthew Mastracci" <[EMAIL PROTECTED]> To: "Nant-Developers (E-mail)" <[EMAIL PROTECTED]> Sent: Tuesday, March 16, 2004 10:20 PM Subject: [nant-dev] Solution task fixes + speedups > I've spent a bit more time speeding up the solution task and fixing > differences from VS.NET. Here's a short summary of what to expect with > the latest CVS: > > 1. We only create one AppDomain per solution build and per project > build. We were creating dozens of AppDomains per project build before. I know, I was planning on fixing this later ... > > 2. GAC checks (IsAssemblyInGac) are now cached per solution build. > This cuts 25% of the build time off alone. Fine, I wasn't concentracing on performance for now > > 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" ... Gert --- 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
[nant-dev] Solution task fixes + speedups
I've spent a bit more time speeding up the solution task and fixing differences from VS.NET. Here's a short summary of what to expect with the latest CVS: 1. We only create one AppDomain per solution build and per project build. We were creating dozens of AppDomains per project build before. 2. GAC checks (IsAssemblyInGac) are now cached per solution build. This cuts 25% of the build time off alone. 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. 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
