I have a solution for Visual Studio 2008 that includes an asp.net remote link project in C #. The solution also contains other C # projects and C ++ projects.
When debugging the interaction between my C # client and the asp.net server, the debugging is excellent. I can literally switch to server calls and retreat. However, there are times when I need to focus my debugging on a standalone executable without an asp.net project .
My problem is that after setting up the project, launching projects other than the asp.net project does not prevent the asp.net project from starting on the development server (and in the system tray). Apparently, it is not “debugging” per se, but it works and uses resources when I don't want it.
I checked and double-checked the settings of the launch project. They are firmly in the off position. Any thoughts on why this will happen and / or how to prevent it? Has anyone else experienced this?
Decision notes: Chalk it to "oh where it is!" in Visual Studio. This parameter is not located on the ASP.NET project properties page (right-click on the project in the solution explorer and select "properties") and is not in the launch project interface. Instead, it is on the “regular” properties page when the project is selected in the solution explorer. that is, make sure that the properties page is visible (View-> Properties Window), and then click on the ASP.NET project in Solution Explorer. The top option is "Always run when debugging", which when set to false, solved the problem.
el2iot2
source share