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?
Related
When I starting the project the following error appears:
The project TestProject.Android needs to be deployed before it can be started. Verify the project is selected to be deployed in the Solution Configuration Manager.
In the Configuration Manager Build and Deploy configurations enabled for Any CPU.
Note: reproduce only on Visual Studio 2019. On the previous version (2017)
all works as expected.
You can simply change the settings in your Solution as:
right-click the Solution -->then go to "Configuration Manager" -->then check "deploy" for your required platform project.
Hope!! It will work..
I have 2 project in my solution explorer that one of this related to windows and other related to web,now i want to run web project but it runs in windows form so i want to know how to change the control to run the web project?
you need to make the web project the start up project. Right click on the web project and choose the Set As StartUp Project.
I have a number of configurations setup in Visual Studio with a carefully crafted list of projects that each one should build.
When I create a new project in the solution it gets selected for building automatically in every existing build configuration.
Is there an option to stop this occurring?
In the solution configuration manager you can unselect build (and deploy) of individual projects for different build configurations.
Right click on solution, select properties, Configuration Properties.
Or Build | Configuration Manager
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.
I've switched from a Website Project to a WAP (Web Application project).
The WDP (Web Deployment Project) is used to set and potentially in the future make other web.config changes.
However I notice that the team build is building everything twice, once on behalf of the solution file and then again because of the WDP. Any idea how I can stop this from happening?
Or is there a way to replace out the web deployment project altogether?
Yes and yes.
You can stop TFS Build from building everything twice by following these steps:
Open the configuration manager (open your solution and select Configuration Manager from the top-level Build menu).
Expand the drop down list for Active solution configuration and select New.
Enter a name for your new solution configuration and select an existing configuration to copy settings from and click OK.
In the Configuration Manager, uncheck the checkboxes in the Build column for all of the projects except the deployment project and click Close.
Edit your TFSBuild.proj file's ConfigurationToBuild ItemGroup by adding your new configuration:
Foo
Any CPU
Where Foo is the name of the new configuration you just defined.
For Visual Studio 2010, the ASP.NET team has partnered with the IIS team to deliver an integrated web application packaging and deployment solution built on the [Web Deployment Tool][1]. It more or less replaces web deployment projects and you can use it with VS/TFS 2008 via its [command line interface][2]. I have a blog post covering the basic scenario here:
Building a Simple Web Site with VSTS/TFS 2008.