visual studio .net debugging: We have a large solution with a large (unmanaged) C++ code base. We started adding .NET projects in C++ and C# recently. If we add a C# project, when we try to debug (e.g. by pushing F5,) the IDE insists on touching every project to see if it is up-to-date

If something has changed, the pop-up that says that not all projects are up-to-date will show, and after clicking "No" VS still tries to build everything. If nothing has changed, it just goes right into building before starting the debugger

If we remove the C# project, everything goes back to normal

This is frustrating since we have about 100 projects that have to get checked everytime we start/restart the debugger. As a temporary solution we have removed the C# projects and put them in another solution, but then we have to add references to the dll's they reference, instead of the projects they reference

Is this a known bug? Is there a work around

Chris,

This is something that we're aware of. For Visual C# projects, the IDE
checks whether a project is up to date regardless of whether it has been
modified since the last build. For the case when you click "No" on the build
dialog, even though it looks like the IDE is rebuilding the Visual C#
projects, it's actually only performing a check. The projects are not built.

The only workaround that I can suggest is rather than removing the projects
from the solution, create a new configuration where you specify to not build
those projects. Using the "Configuration Manager", create a new
configuration called "Debug without Build" (or some other name). In this new
configuration, uncheck the "Build" column for those projects that you don't
want to build. Then you can enable/disable building of those projects by
simply changing your configuratoin from "Debug" to "Debug without Build" and
vice versa.

HabibH.

[quoted text, click to view]
started adding .NET projects in C++ and C# recently. If we add a C#
project, when we try to debug (e.g. by pushing F5,) the IDE insists on
touching every project to see if it is up-to-date.
[quoted text, click to view]
up-to-date will show, and after clicking "No" VS still tries to build
everything. If nothing has changed, it just goes right into building before
starting the debugger.
[quoted text, click to view]
checked everytime we start/restart the debugger. As a temporary solution we
have removed the C# projects and put them in another solution, but then we
have to add references to the dll's they reference, instead of the projects
they reference.
[quoted text, click to view]

On Tue, 27 Jan 2004 18:11:05 -0800, "Chris Johnson"
[quoted text, click to view]

Yes. No. Wait for Whidbey whose "MSBuild" system is hopefully
somewhat less broken than that of Visual Studio 2002/2003.
--

Hi:
I suggest you may use the the tool from framework SDK.
such as CORDBG
Best Wishes
Wei Ci Zhou
[quoted text, click to view]
started adding .NET projects in C++ and C# recently. If we add a C#
project, when we try to debug (e.g. by pushing F5,) the IDE insists on
touching every project to see if it is up-to-date.
[quoted text, click to view]
up-to-date will show, and after clicking "No" VS still tries to build
everything. If nothing has changed, it just goes right into building before
starting the debugger.
[quoted text, click to view]
checked everytime we start/restart the debugger. As a temporary solution we
have removed the C# projects and put them in another solution, but then we
have to add references to the dll's they reference, instead of the projects
they reference.
[quoted text, click to view]

Thanks Habib..

It's not exactly what we wanted to hear, but thanks for the workaround - we'll see if it will work for our environment

None that I'm aware of.

HabibH.

[quoted text, click to view]