I can definitely say this is not fixed in 7.1. If you hit state 1 or state 2, you will get your assemblies locked once they are over 64k. This is a non-trivial problem to fix, and it did not make it into 7.1.
I can't make promises for the next version but I can say we are painfully aware of how much headache this is causing to you, and we get it that the listed work-around is far less than optimal for most of you. For now and 7.1 unless you have CopyLocal=True and do not build to a common output directory you will encounter this problem. Thanks for the continuous input, and sorry to bring bad news, Alex Kipman ([EMAIL PROTECTED]) Program Manager Visual Studio Core Team This posting is provided "AS IS" with no warranties, and confers no rights. � -----Original Message----- From: Chris Kinsman [mailto:ckinsman@;VERGENTSOFTWARE.COM] Sent: Friday, November 08, 2002 7:21 AM To: [EMAIL PROTECTED] On Wed, 6 Nov 2002 20:26:27 -0800, Alex Kipman <[EMAIL PROTECTED]> wrote: >I want to outline the exact states that will cause this problem to occur. >I will also outline how to fix it once that happens. > >State 1 where this problem occurs: >* ProjectA references projectB and projectA has CopyLocal=False on the >reference to projectB >* Assemblies being generated/referenced are >= 64 kbytes > >State 2 where this problem occurs: >* Projects within a solution build to a common output directory. >* Assemblies being generated/referenced are >= 64 kbytes > We hit both of these criteria. We hit state 2 since we do nightly builds and then distribute binaries to developer workstations of approximately 190 assemblies at this point. This allows a developer to sync up with the nightly build and just build one or two assemblies they are working on into this directory and then test. We hit state 1 since we have found the windows forms designer has issues with visual inheritance when CopyLocal=true from what we can tell. With a common build directory set the only way we can edit our forms which are inherited from a different assembly is to set CopyLocal=false on all assemblies and then it appears to use the build directory for loading all references which works. Drives us nuts however the whole shut down, delete, etc. Can anyone definitively say this is fixed in 1.1? Thanks, Chris You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
