MSBuild: What is it, and when do I need it?

I seem to have missed Day 1 of MsBuild 101. I find myself asking "What does it do, what does it replace, and when do I need it?" since I can just hit F5 and compile my application.

Wha开发者_StackOverflow中文版t is the bigger picture I'm missing?

---

MSBuild is the build platform that enables all build activity in the Visual Studio world.

A better, more practical example would be to state that

1. The .csproj files (every C# project) are msbuild files

2. When you hit F5, you basically (oversimplifying) call msbuild.exe and passing in your .csproj file.

MSBuild empowers all the things that make hitting F5 work. From creating the "debug" or "release" folder, to dropping references into the bin\ directory, to invoking CSC ... and everything in between ... MSBuild "powers" all that.

If all you will ever need from a build is the output that F5 gives you, then you know about all you probably need to know about MSBuild.

In most commercial/practical development scenarios, however, there will come a time where there is a need to customize the build process. The most common approach is automating the build process (using either TeamBuild or some homegrown system). You may also need to

• create a "packaged" deployment
• link to another library outside of your project that is also actively being developed
• publish your build to an FTP and send an email to a customer notifying them of its availability.

The use of a unified and extensible build platform (ie MSBuild) is what makes all these these possible, while still being part of the build process ... keeping the "build" part of the development pipeline simple and contained.

---

It's useful when you want do automated builds, and have to implement a build process

The F5 Key Is Not a Build Process and links therein (e.g this) is a good read in that regard.

Also, your Visual Studio project files are msbuild files. If you want to do more advanced stuff when you build (e.g. run a javascript minifier, have more control over autogenerated version identifiers, post processing of files etc.) , you'll have to dig into msbuild.

---

msbuild is used when you want to build your project from the command line. Whenever you see a continuous integration product that will automatically build your project, it will call msbuild to perform the actual build step.

---

I think that build servers should have the option to press F5 key in a simpler way than via windows API.

---

I know this is pretty stale, but here's my take on MSBuild.

It's a scriptable build tool really similar to ANT. They both use XML for configuration, so you'll be able to figure it out fairly quickly. Both have the concept of "Targets" for instance, lots more similarities in thinking, if you know ANT the switch shouldn't be tough.

MSBuild files generated from Visual Studio is really like the generated ANT scripts you get from Eclipse that build your projects, remember your includes and define your dependencies. You can modify them directly for fun and profit.

I like MSBuild, it fixes some of the stuff I find annoying about ANT.