I have a few different solution configurations in my VS2010 solution. For some of those I only want to build a subset of the included projects. Is that possible?
Configuration Manager should do the trick for you.
Related
My Visual Studio 2019 solution contains several projects, some of which I don't want to be built as part of continuous integration. Specifically, I'm trying to exclude tooling and unit tests.
In Visual Studio, I have created a new solution configuration and unchecked the "Build" box for each project I don't want to be built.
In TeamCity, I have specified the name of the new solution configuration to use. However, TeamCity continues to attempt to build all projects within the solution.
[I had included screenshots of my solution configuration, TeamCity build configuration, and resulting TeamCity log but I do not have enough reputation to post images apparently.]
From everything I could find so far, unchecking "Build" from the solution configuration used by TeamCity is supposed to exclude that project from building.
I figured it out by finally noticing that the TeamCity log was showing the build configuration as "ReleaseCI|Mixed Platforms" instead of "ReleaseCI|Any CPU". On other projects, I only needed to specify the configuration. For this project, I apparently have to specify the platform as well.
IDE= Visual Studio 2017 Community
How can I setup a software project so that different cross compile targets for the project map to diff. TFS branches of a single project.
Another related query how to map debug and release versions for one compile target, taking into account previous query above, in VS hosted TFS online.
I assume you mean configuration and platform, you don’t need to do it, also it is based on the configuration and platform you selected in Visual Studio, you just need to change the configuration and platform before build the project.
Refer to these steps to configure configuration and platform for each project.
Right click solution > Configuration Manager
Choose configuration and platform for solution
Choose configuration and platform for projects
Change configuration and platform for solution in Visual Studio
Build the solution or just the project
I have seen this:
Running two projects at once in Visual Studio
But I have another problem.
My solution had many executable projects.
Maybe I can allocate them into different groups.
For each group, It has a specific one or more startup projects.
So how can I configure it with Visual Studio 2017?
(Could I making some configuration in the project properties?)
You can use the SwitchStartupProject extension to select the startup project from a dropdown and switch between multi-project startup configurations.
I have a solution with a large number of solution level build configurations. Whenever I add a project to this solution, Visual stuido changes all of my configurations to build the new project. Is there a way to stop VS from doing this, or am I stuck reconstructing all my build configurations every time I add a new project to the solution?
I don't know of any solution within visual studio but you could do it by hand rather easily. Project files are simply xml files and solution files are text-based as well (and rather simple structured).
If you know how to handle MSBuild files (i.e. project files) you can even simplify them if you have many configurations.
This is the msdn article for MSBuild:
https://msdn.microsoft.com/en-us/library/wea2sca5(v=vs.90).aspx
What is the difference between Build Solution and Batch Build in Visual Studio 2008?
The key point which seems to be missed in both the existing answers is that batch build allows you to build multiple configurations of each project (e.g. you can build debug and release configurations with a single operation).
With a normal build, you have to use the configuration manager to select just one configuration for each project.
in addition to what has been mentioned so far, batch build allows a combination of projects or configurations to be stored as a preset for easier future access.
Batch build allows you to build any project that you select, and a Solution build only builds the projects that are part of the active solution.
You can customise what projects are part of a solution build by going to menu Tools → Configuration Manager.
Another nice thing about batch build is that it lets you build a configuration different than the current one. It is handy for solutions that take a while to switch.
Building the solution is the same as batch building all projects. Both methods respect the solution's dependencies.