WHEN is Microsoft going to fix the problem with VS.NET where it cannot
build the solution because it is locking DLLs that are >64k in size?  This
has been a problem since day one and I have wasted DAYS of time over the
last 12 months battling this.  I can't even work on one of the subprojects
because everytime I make a change and compile it, it fails because the DLL
is locked and I have to exit VS.NET, delete the project's bin and obj
folders and reload VS.NET.  Another way that the problem manifests itself
is that the subproject will build fine but another subproject that
references that subproject will not build saying something like it can't
find the type of namespace in that project.

(YES, all references to the project in question are Project references, not
File references - which, according the Microsoft, should make it work fine)

Surely a hell of a lot of people out there are running into this problem...
or is no one out besides me and a few others foolish enough to try a large-
scale .NET project yet?

Sorry for the ranting and raving but I have completely lost my patience
with this.

You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced 
DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

Reply via email to