Visual Studio file locking during debugging

Question

I have a VS solution containing several projects. When debugging a specific project, all source files are blocked by VS. I would like to unblock sources on which the debut has no dependence. Is there a way to do this in a single solution?

UPDATE:

I am using Win XP SP3 32bit. Visual Studio 2010, C #. Modify and Continue are enabled. The solution contains 6 projects (the number is actually not important), 5 of them depend on the data access level project that uses the Entity Framework. None of these 5 are interdependent. These are WinForms and console applications. I would like to be able to run one of the projects and make changes to others, without stopping the first. The problem is that starting and stopping a project takes a considerable amount of time.

Answer 1

The function "Edit and continue" does not allow you to edit files if the debugger did not stop the program. A simple solution is Debug + Break All, you should be able to edit files, your changes will be immediately effective if your changes do not violate the restrictions imposed by E + C. This is the most efficient workflow.

The hard approach is to disable Edit and Continue. Tools + Options, Debugger, Modify and continue, uncheck the Enable box.

Answer 2

I do not think there is a way to avoid this. Although debugging, Visual Studio locks all files to prevent them from being modified, including in other projects.
You can try to open the project that interests you with another instance of Visual Studio to make changes to your files or open files synchronously with another editor.

Answer 3

This doesn't quite answer the OP question as such, but for those who stumbled upon this page in the same (very frustrated) boat as me, this might help.

Solution: start without debugging .

It drove me crazy that Visual Studio did not allow me to edit files while the application was running. My typical workflow:

• Make some changes.
• Launch the app to see the effects of these changes.
• Based on the results, make more changes, etc. etc.

The problem is that Visual Studio is stopping me from step 3. It requires you to start the STOP application before you can even make any changes (including to the XAML file or adding the file to the project), which also means that you cannot return to the application to double check something while you actually program it (which I am working on, br).

Thank goodness I finally found that if I run without debugging, this does not impose this ridiculous restriction. This is still a pain in the butt, if you really need to debug something you need to restart the application in debug mode, but it is sure that you need to kill the application before it even allows you to edit the file.