Have Geek Brain

In VS.NET, why doesn't run debug create the entire selected project in active configuration?

Why doesn't running debug create the entire selected project in an active configuration?

Usually I have some DLLs that are linked to the main project indirectly (MEF) and when I run debug (F5) VS.NET does not create those DLLs. I first need to build (Ctrl + Shift + B) and then debug the application to debug the current versions of these DLLs.

I'm guessing VS.NET is trying to speed up the debugging process by not creating non-relational DLLs, but in my case it makes it even slower.

Can this behavior be changed?

0


a source to share


3 answers


Maybe check the project dependencies: Project | Project dependencies.



+1


a source


Is it safe to assume that these DLLs are simply referenced and not part of your solution? If so, why. So that you can implement the functionality that I think you are looking for, then you will need to add projects for the DLLs that reference your solution, and instead of referencing the DLLs directly, you should refer to the project.This will allow you to compile the DLL along with your main project and easy to debug. If this is not what you are talking about, I apologize.



+2


a source


The following setting can also affect which projects in your solution are created when you start a debug session:

Tools -> Options ... -> Projects and Solutions -> Build and Run -> Create Only Launch Projects and Run Dependencies

0


a source






More articles:


All Articles