Robert McLaws: Windows Edition : MSBuildhttp://windows-now.com/blogs/robert/archive/tags/MSBuild/default.aspxTags: MSBuildenCommunityServer 2008 SP2 (Build: 31104.93)MSBuild and Longhornhttp://windows-now.com/blogs/robert/archive/2003/10/27/831.aspxMon, 27 Oct 2003 17:44:00 GMT20f58a17-7e15-440c-89b3-dfe02fe74bcd:831rmclaws2k0http://windows-now.com/blogs/robert/rsscomments.aspx?PostID=831http://windows-now.com/blogs/robert/archive/2003/10/27/831.aspx#comments<P>I'm sitting in a session introducing MSBuild, the new compilation engine for Whidbey/Longhorn. I'm going to talk a little bit about how it works, because it has a serious effect on software development for Longhorn.</P>
<P>In VS.NET 2002/2003, compiling an application is a &#8220;black box&#8221; event. Visual Studio does a whole ton of stuff behind the scenes, that you never even know about when you hit F5. What this also means is that, 99% of the time, you need to have VS.NET (or similar) installed to compile the application. This is an extreme hinderance to developers who cannot afford an IDE to build apps with. That all changes with MSBuild.</P>
<P>Microsoft has separated the build engine from VS.NET, and that engine will be installed by default in Longhorn. Project files are now formatted as follows:</P>
<P><PROJECT><BR>&nbsp;&nbsp;&nbsp; <ITEM Include="&#8220;*.cs&#8220;" Type="&#8220;csc&#8220;"><BR></PROJECT></P>
<P>That is the basic project file. You can add tasks</P>
<P>All of the examples in the keynote speeches were done using test editors (notepad and emacs) and MSBuild. Jim Allchin even wrote some of his own code in a text editor. </P><div style="clear:both;"></div><img src="http://windows-now.com/aggbug.aspx?PostID=831" width="1" height="1">MSBuild