<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Running MSBuild 4.0 and MSBuild 3.5 on Continuous Integration	</title>
	<atom:link href="https://www.scmgalaxy.com/tutorials/running-msbuild-40-and-msbuild-35-on-continuous-integration/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.scmgalaxy.com/tutorials/running-msbuild-40-and-msbuild-35-on-continuous-integration/</link>
	<description>A Platform for Software Engineers</description>
	<lastBuildDate>Mon, 22 Dec 2025 12:01:09 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1</generator>
	<item>
		<title>
		By: Blake		</title>
		<link>https://www.scmgalaxy.com/tutorials/running-msbuild-40-and-msbuild-35-on-continuous-integration/#comment-873</link>

		<dc:creator><![CDATA[Blake]]></dc:creator>
		<pubDate>Mon, 22 Dec 2025 12:01:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.scmgalaxy.com/tutorials/2010/03/09/running-msbuild-40-and-msbuild-35-on-continuous-integration/#comment-873</guid>

					<description><![CDATA[Running both MSBuild 3.5 and MSBuild 4.0 in a continuous integration (CI) environment is crucial for teams maintaining legacy .NET applications alongside newer projects. This article does a solid job explaining how to configure your CI server to correctly identify and invoke the appropriate MSBuild version based on project requirements, which helps prevent build failures due to mismatched toolsets. Understanding how to set the environment paths and build definitions ensures repeatable, reliable builds — an essential practice in DevOps and CI/CD workflows. Thanks for shedding light on these configuration tips that can save developers time and reduce integration issues.]]></description>
			<content:encoded><![CDATA[<p>Running both MSBuild 3.5 and MSBuild 4.0 in a continuous integration (CI) environment is crucial for teams maintaining legacy .NET applications alongside newer projects. This article does a solid job explaining how to configure your CI server to correctly identify and invoke the appropriate MSBuild version based on project requirements, which helps prevent build failures due to mismatched toolsets. Understanding how to set the environment paths and build definitions ensures repeatable, reliable builds — an essential practice in DevOps and CI/CD workflows. Thanks for shedding light on these configuration tips that can save developers time and reduce integration issues.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
