I have multiple projects running and one project sometimes stops and needs to be restarted. Is there a way to restart only one project without stopping the other projects? i.e., clicking the Restart button in Visual Studio that restarts all of the projects, but I only want to restart one.
Independently from startup settings, each project can be started "manually" via: right click on the project > Debug > Start New Instance
Related
I'm trying to create a pre build event similar to one described in this post
Build another project by prebuild event without adding reference
This is the command line I'm using in the Pre-build command line of the build events tab in Visual Studio 2015.
"$(DevEnvDir)devenv.exe"
$(SolutionDir)MyFolder\SubFolder\MyProject.csproj /Rebuild "Debug|Any
CPU"
However when I hit Build on the project that contains the pre-build event, it begins launching multiple instances of Visual Studio. I am watching the output directory for bin/Debug and it is conintually cleaning and rebulding the project, each time a new instance of Visual Studio is launched. None of the instances close. They remain running.
EDIT: I noticed even after cancelling the build in the IDE and exiting the IDE, the processes are still running and the debug folder is still being cleaned and updated with new dll's each time.
This is what my task manager looks like during the process
I'm working at a colleagues PC. When I right click on a .Net Gadgeteer 4.2 project in our solution and select "Set as StartUp Project" I expect Visual Studio to set the build configurations so that the new start-up project is deployed to the device on start, as it does on my PC. But instead I need to open the configuration manager and manually deselect the previous start-up project and select the new one. Why? How can I swap (back) to using Visual Studio to manage deployment without the additional step in the configuration manager?
========== EDIT ==========
#john-saunders comment below makes me think I've misworded my question.
I have a solution containing multiple projects, many of which are .Net Gadgeteer projects.
On most of my machines if I right click on Project A in the Solution Explorer and select Set as StartUp Project then when I debug the solution (i.e. hit F5) Project A and any of its required dependencies are built and deployed to the Gadgeteer device and the debugger gets attached. If I then right click on Project B in the Solution Explorer and select Set as StartUp Project then when I debug the solution Project B and any of its required dependencies are built and deployed to the Gadgeteer device.
But on one machine this is not happening. Instead when I right click on Project B in the Solution Explorer and select Set as StartUp Project when I debug the solution Project A is deployed to the Gadgeteer device. To ensure that Project B is instead deployed I have to manually edit the configuration.
Why? How do I get this one machine to behave like the others?
I wonder if I can run multiple instances (right now two instances) of my application in debug mode by doing a simple click or set a key for that...
Not many people seem to know this, but this is perfectly possible, though I admit it's not very obvious.
Here's what you do:
suppose your current project is A, and it's output is c:\bin\my.exe
add an empty project to the solution for A, call it 'Dummy'
under Dummy's Project Properties->Debugging set the Command to point c:\bin\my.exe
under Solution Properties->Configuration Manager, uncheck all builds of the Dummy project so VS won't try to build it (building an empty project fails)
under Solution Properties->Startup Project, select Multiple Startup Projects and set the Action for both A and Dummy to Start
now hit F5 and your exe will be launched twice, each under a seperate debugging instance. (as you will be able to see in the Debug->View->Processes window)
You can use "Multiple Startup Projects" feature, but avoid creating dummy projects by hand: just add your debuggee executable into the solution directly:
Solution > Add existing project > Path to .exe
If you neeed several instances, Visual Studio won't allow you to add the same executable twice, but adding a symlink to it with another name works as expected.
MSDN: How to: Debug an Executable Not Part of a Visual Studio Solution
Is Visual Studio 2013 this is even easier!
Project-> Properties -> Debug -> check "Start external program" and click the ... button, navigate to your .exe of the other program.
Then Make sure in your Solution -> Properties -> MultipleStartup Projects that it's checked.
You can run two instances of your application from where it is built; example: d:\test\bin\debug\app.exe and attach both instances to the Visual Studio 2010 debugger.
I created a solution in Visual C# 2010 Express that contains two projects: one is the client, the other is the server. I would like to debug both at the same time, but I can only seem to run one of the projects during debugging.
Is there a way to run both at once?
Go to Solution properties → Common Properties → Startup Project and select Multiple startup projects.
Max has the best solution for when you always want to start both projects, but you can also right click a project and choose menu Debug → Start New Instance.
This is an option when you only occasionally need to start the second project or when you need to delay the start of the second project (maybe the server needs to get up and running before the client tries to connect, or something).
I've have a project which has 11 mini-project...
I choose 2 of my project to start when project is browsing...
My first project is web other one is desttop project...
While i choose start without debugging is work fine: 2 of my projects start well...
But when i choose to debug mode my desktop project is not starting, thus i can't debug my project...Just my web project is starting and thats's all, it is not working as same as in the without debuging mode...
Summary: 2 project is not working properly as same as in the debug mode and in the without debug mode...
Anytime during debugging your can right click a project in the solution explorer and start it for debugging. That way you can start as many projects as you wish.