This site uses cookies for analytics, personalized content and ads. By continuing to browse this site, you agree to this use. Learn More
The official source of product insight from the Visual Studio Engineering Team
October 27, 2015Oct 27, 201510/27/15Hello everyone! Every month we share some top stories from the previous month, and here’s our round-up for September.
Open-source, cross-platform MSBuild: Continuing the open-source, cross-platform .NET story that is already well underway with .NET Core and the .NET Compiler Platform (“Roslyn”),
July 24, 2013Jul 24, 201307/24/13We made a number of exciting changes to MSBuild for Visual Studio 2013, including rethinking the fundamental relationship between MSBuild, Visual Studio, and the .NET Framework. MSBuild has shipped as a component of the .NET framework since it was first introduced in 2005 with .NET 2.0,
July 8, 2010Jul 8, 201007/8/10In my last two posts (here and here) I showed how to enable the unsupported MSBuild debugger to debug a build started on the command line with MSBuild.exe. In this final post, I’ll mention some other variations.
Note that this blog is rather narrow,
July 8, 2010Jul 8, 201007/8/10In my previous post, I showed how to enable the hidden Visual Studio debugger for MSBuild script, and demonstrated it by stepping through the evaluation of a C# project. In this post, I’ll keep debugging into the actual build of that project.
July 6, 2010Jul 6, 201007/6/10Back when we started 4.0 development, I polled readers of the MSBuild blog to find out what features were most important to them. Debugging was #1 which was very surprising to us. Thinking about it more, it makes sense. In our team we’ve become so proficient ourselves at reading the XML and making sense of logs that it’s easy to forget how difficult it is – especially for someone new.
June 1, 2010Jun 1, 201006/1/10Introduction
In MSBuild 4 we introduced several performance improvements, particular for large interdependent builds. By and large they are automatic and you receive their benefit without making any changes to the way your build process in authored. However, there are still some cases where we are unable to make the best decision.
May 11, 2010May 11, 201005/11/10Assembly references are an integral part of build process. When the assembly references passed to the compiler are correct everything works but when they are not projects stop building. When this happens It can be frustrating to try and figure out why a reference was resolved from one location rather than another thereby causing the problem.
May 7, 2010May 7, 201005/7/10UPDATE: Most issues around MSBuild support for cross-bitness and 64-bit builds are fixed in .NET 4.5. As always, feedback is welcome! Please leave your comments in this blog post and report any bugs on Microsoft Connect.
During the Visual Studio 2010 development cycle a push to make the build experience better on Cross compilation scenarios as well on making sure a build using 32-bit MSBuild was identical (in outputs) to a build using 64-bit MSBuild.
May 5, 2010May 5, 201005/5/10Some more information about this 4.0 feature. (I’ve also updated the first post with this, so everything’s in one place for your reference.)
Built-in MSBuild functions
The full list of built-in [MSBuild] functions, like the one above, are in the MSDN topic here.
April 26, 2010Apr 26, 201004/26/10The VC++ build system is of course MSBuild based in VS 2010. This automatically gives you a great deal more flexibility to customize your build than you had with .vcproj project files in prior releases. We went out of our way to ensure that the .targets files that drive the build of a .vcxproj file in VS 2010 leverage as much MSBuild flexibility as possible.
