I have a visual studio 2008 solution that includes an asp.net-hosted remoting 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 great. I can literally step into server calls and back out. However, there are times in which I need to focus my debugging on a standalone executable without the asp.net project.
My trouble is that, after settings the startup project(s) to other projects besides the asp.net project does not prevent the asp.net project from launching in the development server (and system tray). It doesn’t appear to be ‘debugging’ per se, but it IS running and using up resources when I don’t want it to be.
I have checked and rechecked the startup project settings. They are firmly in the ‘off’ position. Any thoughts on why this would happen and/or how to prevent it? Has anyone else experienced this?
Solution Notes: Chalk this one up to the ‘oh that’s where that is!’ phenomenon in Visual Studio. This setting isn’t on the ASP.NET project properties page (right-click on project in solution explorer and choose ‘properties’), and isn’t on the startup projects UI. Instead it is on the ‘regular’ properties page when the project is selected in the solution explorer. i.e. ensure the properties page is visible (View->Properties Window) and then click on the ASP.NET project in solution explorer. The top option is ‘Always Start when Debugging’ which, when set to false, solved the problem.
To stop the the development server from starting.