<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Running MSBuild from Visual Studio</title>
	<atom:link href="http://brennan.offwhite.net/blog/2007/05/31/running-msbuild-from-visual-studio/feed/" rel="self" type="application/rss+xml" />
	<link>http://brennan.offwhite.net/blog/2007/05/31/running-msbuild-from-visual-studio/</link>
	<description>My Experiences with Software Development</description>
	<pubDate>Thu, 20 Nov 2008 10:38:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Brennan&#8217;s Blog &#187; Blog Archive &#187; Web Deployment Projects in Visual Studio 2008</title>
		<link>http://brennan.offwhite.net/blog/2007/05/31/running-msbuild-from-visual-studio/#comment-25482</link>
		<dc:creator>Brennan&#8217;s Blog &#187; Blog Archive &#187; Web Deployment Projects in Visual Studio 2008</dc:creator>
		<pubDate>Fri, 30 Nov 2007 06:13:12 +0000</pubDate>
		<guid isPermaLink="false">http://brennan.offwhite.net/blog/2007/05/31/running-msbuild-from-visual-studio/#comment-25482</guid>
		<description>[...] Below is my main build.proj script which assumes the website is in a folder named Website and the Web Deployment project is in a folder called Website_deploy. It creates a zip file with three folders: Assemblies, ThirdParty and Website. The Assemblies folder holds the output files from the class library while the ThirdParty folder holds the pre-built assemblies referenced by the class library. Finally the Website folder holds the output generated by the Website Deployment project.  To learn more about working with MSBuild, you can read 7 Steps to MSBuild and to learn how to make better use of Web Deployment Projects you can read Post Build Deployments with MSBuild. Finally, to learn how to easily to run the MSBuild script in your root Solution folder you can read Running MSBuild from Visual Studio. [...]</description>
		<content:encoded><![CDATA[<p>[...] Below is my main build.proj script which assumes the website is in a folder named Website and the Web Deployment project is in a folder called Website_deploy. It creates a zip file with three folders: Assemblies, ThirdParty and Website. The Assemblies folder holds the output files from the class library while the ThirdParty folder holds the pre-built assemblies referenced by the class library. Finally the Website folder holds the output generated by the Website Deployment project.  To learn more about working with MSBuild, you can read 7 Steps to MSBuild and to learn how to make better use of Web Deployment Projects you can read Post Build Deployments with MSBuild. Finally, to learn how to easily to run the MSBuild script in your root Solution folder you can read Running MSBuild from Visual Studio. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
