I have a solution file Blah.sln in Visual Studio that contains say 10 projects. On a commit only 1-2 projects would be changed so doing an incremental build on the solution file would only build those projects.
What I would like to do though, whenever I do an incremental build in Visual Studio, I would like to know which projects were built and which projects were not touched. Does Visual Studio has any feature support for this?
Any help would be much appreciated. Thanks.
Related
I am using Visual Studio 2017 and I have a solution consisting of several projects mainly in C++. Now I want to add an existing C++ project which using CMake for building to my solution in visual studio and build it along with other projects in solution. Is it possible to do that? FYI, I can build the cmake project separately in Visual Studio.
I'm new to .net and want to use a build tool for my project. I'm reading about MSBUILD and other options but recently came to know that Visual studio projects are MS Build scripts.
So, that makes me think, should I really use MSBUILD for Visual studio projects ?
Visual Studio uses MSBuild under the hood and the project system is based on it.
There are a few other tools that help with .NET builds, like Cake, but for the most important part, they also call MSBuild (but help you to script it for complex scenarios).
There really isn't an alternative to MSBuild since all tools (VS, JetBrains Rider, OmniSharp (/VSCode)) require it to understand C#/VB.NET projects.
should I really use MSBUILD for Visual studio projects ?
Obviously, we can also use devenv.exe, csc.exe or other compilers for Visual Studio projects except MSBuild. But just as Martin`s answer, all tools (VS, JetBrains Rider, OmniSharp (/VSCode)) require it to understand C#/VB.NET projects. And Visual Studio hosts MSBuild to load and build managed projects. Because MSBuild is responsible for the project, almost any project in the MSBuild format can be successfully used in Visual Studio.
With MSBuild, you could build projects on a build server for .NET apps without Visual Studio.
Besides, MSBuild will give you significant flexibility in choosing what technologies you use to implement continuous integration. And custom MSBuild tasks will give you even more flexibility in implementing custom builds.
What more, If Visual Studio Team System is in your future, applications built using MSBuild will be much easier to move into that environment than those built via alternative means.
Though, we can build Visual Studio project by using other ways, it is absolutely a good idea to use MSBuild for Visual Studio projects.
Hope this can help you.
I'm using Visual Studio 2015 Enterprise Edition. I followed this tutorial
https://www.youtube.com/watch?v=IgvbhyDh8r0
Like Visual Studio creates a .sln file when any new project is saved and then on building it executes it to build the project, in the case of this VTK tutorial, it uses CMake to create the build file .sln for Visual studio to execute. Is there any way I can automate/replace the process of CMake using Visual Studio only?
PS- Just ignore if I have any misunderstanding of the concepts as I'm totally new to this and was not able to find proper documentation on it.
After you've generated a .sln file once, you don't need to run CMake manually again. It hooks itself into ZERO_CHECK project, so it would regenerate the solution every time you change CMakeLists.txt.
But you can't do with VS only, as you have to generate .sln for the first time.
Is there any way that I can use the latest IDE (VS2015) to work with my old solution project but i don't wish to upgrade my project?
Unfortunately, you cannot do this. The format of project and solution files was changed in VS 2010, so the furthest back you could possibly go with VS 2015 would be to VS 2010.* And that wouldn't help you any for cross-compatibility, since VS 2008 can't open VS 2010 project files.
You have no real choice but to allow the IDE to convert your solution and project files to the latest version. However, this will not delete your old VS 2008 project/solution files. They will still be in the solution directory, and will still work for opening the solution in VS 2008. The new project/solution files will open the solution in VS 2015.
This was a very common strategy employed by open-source projects before recent versions of Visual Studio implemented cross-compatibility. They would just have multiple versions of project and solution files for each supported version of Visual Studio.
The only disadvantage with this is that changes you make to one version of a project or solution file don't propagate to the others automatically. But this isn't really that big of a deal, since once a project is reasonably mature, the project and solution files don't change very often.
* In fact, VS 2015 interoperates smoothly with project/solution files from VS 2013, VS 2012, and VS 2010 SP1. It can create and modify project files for any of these versions. See MSDN: Porting, Migrating, and Upgrading Visual Studio Projects (for Visual Studio 2015)
I have a visual studio solution with a a vs2010 project
Everytime I open it I got this warning.
Visual Studio needs to make non-functional changes to this project in
order to enable the project to open in this version and Visual Studio
2010 SP1 without impacting project behavior.
ANd it generates some xml log files
I need to definitely convert it to vs 2012
How can I do that without breaking anything else?
I was able to solve it by opening the .csproj file and changing this
<FileUpgradeFlags>0</FileUpgradeFlags>
for this
<FileUpgradeFlags></FileUpgradeFlags>