<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://danmoseley.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Dan Moseley</title>
 <link>http://danmoseley.sys-con.com/</link>
 <description>Latest News from Dan Moseley</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Wed, 02 Dec 2009 11:49:59 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>MSBuild - What It Does and What You Can Expect in the Future</title>
 <link>http://danmoseley.sys-con.com/node/461416</link>
 <description>In Visual Studio 2003 and earlier, the build process for Visual Basic and C# projects was hard-coded, and built into Visual Studio itself. The only build scripting tool that Microsoft offered was nmake, and a companion tool called build.exe that provided some support for concurrent builds. Visual Studio users whose build systems were based on makefiles had to maintain project files in parallel. For Visual Studio 2005, we thought it would be great if it was possible to completely customize the build process, and to build Visual Studio projects on machines that didn&#039;t even have Visual Studio installed, exactly the same as they built inside Visual Studio. We also wanted to be able to plug in reuseable build loggers and build steps.&lt;p&gt;&lt;a href=&quot;http://danmoseley.sys-con.com/node/461416&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sat, 17 Nov 2007 12:00:00 EST</pubDate>
 <guid isPermaLink="true">http://danmoseley.sys-con.com/node/461416</guid>
 <comments>http://danmoseley.sys-con.com/node/461416#feedback</comments>
</item>
</channel>
</rss>
