The other problem that I've had is with common output directories. My advice, don't use them. When I had the output of all of my projects going to a single directory and Copy Local set to false, I had a complete nightmare rebuilding the solution. I'd have to remove all references and then build from the base re-adding references as projects built. I ditched that and now have the projects build to the default bin\<config> and have Copy Local set to true -- haven't had a reference problem since I made the change. I'm just kicking myself for not doing it earlier...I probably cost myself a week of development time just working around this shortcoming in Visual Studio.
Seang -----Original Message----- From: James Berry [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 16, 2002 1:53 PM To: [EMAIL PROTECTED] Subject: Re: [DOTNET] NIGHTMARE BUG!! Visual Studio fails to build debug, but release works fine.. Hi Sean, I've had the odd funny in the past too, which is why I've tried everything I have to make it work (see below). In this case, I can move all the code to a new machine, without any dll's and it STILL doesn't work. I've tried just about every permutation of everything. Frustrated of Canterbury -----Original Message----- From: Sean Greer (SBI-Chico) [mailto:[EMAIL PROTECTED]] Sent: Tue 16/04/2002 21:31 To: [EMAIL PROTECTED] Cc: Subject: Re: [DOTNET] NIGHTMARE BUG!! Visual Studio fails to build debug, but release works fine.. I've had my share of build problems Visual Studio .NET 1-oh-my-God! as well. My last resort has always been to close Visual Studio and delete the bin and obj directories for all projects. Once this is done, I have been able to build regardless of the previous error (missing reference, locked file, etc.) Good luck, Seang -----Original Message----- From: James Berry [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 16, 2002 1:15 PM To: [EMAIL PROTECTED] Subject: [DOTNET] NIGHTMARE BUG!! Visual Studio fails to build debug, but release works fine.. I am developing a .net project. The solution has 14 projects, of varying size. The compiled IL is a total of 640k so far. So it's getting big, but you wouldn't expect there to be any problems. Today VS.NET has started refusing to build my project in debug mode. A simple 'using Adastra.CMS.Business' statement gives the standard reference problem message: "Main.cs(8): The type or namespace name 'CMS' does not exist in the class or namespace 'Adastra' (are you missing an assembly reference?)" However, I have got the correct project in my references. Deleting the reference and re-adding it has no effect. Inspecting the compiled dll with ildasm indicates that yes, the namespace is in there. Would you believe building a release mode version works perfectly??? I have tried full rebuilds, partial rebuilds, del *.dll /s, del *.pdb /s and a rebuild. I've tried restarting devenv. I've tried rebooting. I've deleted the solution and recreated it. I've deleted the project that contains the adastra.cms.business namespace. I've done a full repair/reinstall of vs.net; I've copied the project to another machine and tried building it on there (same again). I've tried pulling my hair out. I've tried shouting. But nothing seems to work. I don't understand -- seeing as a release build works fine! This is frustrating as hell. I've been trying to solve this for 7 hours straight now, and you can guess how I feel about visual studio.net right about now. Anyone got any ideas? Please??? ;-) You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. bjzi爀 z kax34Dڭb=맲 ry 34DȮ mh"^7zZ)1 b 聶 m.2^=hƥ& You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
