<?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: Massive Search &amp; Replace Among Files Checked-in to TFS</title>
	<atom:link href="http://elegantcode.com/2009/11/07/massive-search-replace-among-files-checked-in-to-tfs/feed/" rel="self" type="application/rss+xml" />
	<link>http://elegantcode.com/2009/11/07/massive-search-replace-among-files-checked-in-to-tfs/</link>
	<description></description>
	<lastBuildDate>Tue, 16 Mar 2010 18:16:58 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: David Starr</title>
		<link>http://elegantcode.com/2009/11/07/massive-search-replace-among-files-checked-in-to-tfs/comment-page-1/#comment-50204</link>
		<dc:creator>David Starr</dc:creator>
		<pubDate>Mon, 09 Nov 2009 15:25:14 +0000</pubDate>
		<guid isPermaLink="false">http://elegantcode.com/2009/11/07/massive-search-replace-among-files-checked-in-to-tfs/#comment-50204</guid>
		<description>&lt;a href=&quot;#comment-50201&quot; rel=&quot;nofollow&quot;&gt;@Jason Jarrett &lt;/a&gt; 

Ah! I totally misread that. You can see the sorry state of my PowerShell skillz.</description>
		<content:encoded><![CDATA[<p><a href="#comment-50201" rel="nofollow">@Jason Jarrett </a> </p>
<p>Ah! I totally misread that. You can see the sorry state of my PowerShell skillz.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Jarrett</title>
		<link>http://elegantcode.com/2009/11/07/massive-search-replace-among-files-checked-in-to-tfs/comment-page-1/#comment-50202</link>
		<dc:creator>Jason Jarrett</dc:creator>
		<pubDate>Mon, 09 Nov 2009 14:47:32 +0000</pubDate>
		<guid isPermaLink="false">http://elegantcode.com/2009/11/07/massive-search-replace-among-files-checked-in-to-tfs/#comment-50202</guid>
		<description>&lt;a href=&quot;#comment-50199&quot; rel=&quot;nofollow&quot;&gt;@Graham&lt;/a&gt; 
Yes - but as Singletons aren&#039;t the main topic of the post, and the context required to explain the reasoning for the search/replace is way out of scope. I&#039;ll just leave it at, yes it is an improvement.</description>
		<content:encoded><![CDATA[<p><a href="#comment-50199" rel="nofollow">@Graham</a><br />
Yes &#8211; but as Singletons aren&#8217;t the main topic of the post, and the context required to explain the reasoning for the search/replace is way out of scope. I&#8217;ll just leave it at, yes it is an improvement.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Jarrett</title>
		<link>http://elegantcode.com/2009/11/07/massive-search-replace-among-files-checked-in-to-tfs/comment-page-1/#comment-50201</link>
		<dc:creator>Jason Jarrett</dc:creator>
		<pubDate>Mon, 09 Nov 2009 14:42:36 +0000</pubDate>
		<guid isPermaLink="false">http://elegantcode.com/2009/11/07/massive-search-replace-among-files-checked-in-to-tfs/#comment-50201</guid>
		<description>&lt;a href=&quot;#comment-50189&quot; rel=&quot;nofollow&quot;&gt;@David Starr&lt;/a&gt; 

A. Not sure, what you mean by &quot;in the repo&quot;. I&#039;m still working on my local dev disk. So I&#039;m not changing live in the repo. Which is the purpose of using tfs power tools to detect what changed locally and queue it up to be checked in. This gives me the opportunity to diff each file that actually changed.

B. I&#039;m sure there are risks here, luckily I didn&#039;t bump into any.</description>
		<content:encoded><![CDATA[<p><a href="#comment-50189" rel="nofollow">@David Starr</a> </p>
<p>A. Not sure, what you mean by &#8220;in the repo&#8221;. I&#8217;m still working on my local dev disk. So I&#8217;m not changing live in the repo. Which is the purpose of using tfs power tools to detect what changed locally and queue it up to be checked in. This gives me the opportunity to diff each file that actually changed.</p>
<p>B. I&#8217;m sure there are risks here, luckily I didn&#8217;t bump into any.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Graham</title>
		<link>http://elegantcode.com/2009/11/07/massive-search-replace-among-files-checked-in-to-tfs/comment-page-1/#comment-50199</link>
		<dc:creator>Graham</dc:creator>
		<pubDate>Mon, 09 Nov 2009 13:40:17 +0000</pubDate>
		<guid isPermaLink="false">http://elegantcode.com/2009/11/07/massive-search-replace-among-files-checked-in-to-tfs/#comment-50199</guid>
		<description>Is the IoC anti-pattern (i.e. coupling to the container, rather than dependency injection) much of an improvement on using singletons?</description>
		<content:encoded><![CDATA[<p>Is the IoC anti-pattern (i.e. coupling to the container, rather than dependency injection) much of an improvement on using singletons?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Starr</title>
		<link>http://elegantcode.com/2009/11/07/massive-search-replace-among-files-checked-in-to-tfs/comment-page-1/#comment-50189</link>
		<dc:creator>David Starr</dc:creator>
		<pubDate>Mon, 09 Nov 2009 06:21:13 +0000</pubDate>
		<guid isPermaLink="false">http://elegantcode.com/2009/11/07/massive-search-replace-among-files-checked-in-to-tfs/#comment-50189</guid>
		<description>A. This is cool. Being able to work on the code in the repo is pretty slick.
B. I wonder if this is really risky, though.

Just thinking through another scenario, would it be safer to pull all the code, do the search and Replace within Visual Studio, and then ensure I get all my changes to pass tests before I commit them?</description>
		<content:encoded><![CDATA[<p>A. This is cool. Being able to work on the code in the repo is pretty slick.<br />
B. I wonder if this is really risky, though.</p>
<p>Just thinking through another scenario, would it be safer to pull all the code, do the search and Replace within Visual Studio, and then ensure I get all my changes to pass tests before I commit them?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
