The basic principle behind Visual Studio Project Builder is that it allows you to:
•Manage many projects together in one collection, even if those projects have the same name (something you can't do with a Visual Studio Solution).
•Allow you to easily, build, rebuild or clean these projects.
•Allow you to automatically repeat build a failing build so that it may succeed on the second attempt (something that does happen with Visual Studio).
•Allow you to apply filters so that you can ignore various warnings and errors that are not important.
•Provide visual, at a glance, build progress, even from across the room.
•Allow you to be notified when a build completes. These is very useful when dealing with long running builds - you can use your time more effectively - do marketing, read a book, go for a walk, without worrying "has it finished yet?".
All of these things make building software faster, easier, less error prone and less stressful.
The main tasks involved in using Visual Project Builder are to:
•Create a collection of projects.
•Build, rebuild and clean projects.
•Filter any unwanted solutions, projects and project configurations.
•Filter any warnings or errors that are not relevant
•Examine build log files
•Manage the results of the builds.
That's what we'll cover in the following topics.