<?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: Speeding up Visual Studio 2005</title>
	<atom:link href="http://www.thekua.com/atwork/2007/05/speeding-up-visual-studio-2005/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thekua.com/atwork/2007/05/speeding-up-visual-studio-2005/</link>
	<description>thekua&#039;s reflections on work related topics</description>
	<lastBuildDate>Mon, 15 Mar 2010 07:45:06 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: wethecom</title>
		<link>http://www.thekua.com/atwork/2007/05/speeding-up-visual-studio-2005/comment-page-1/#comment-75008</link>
		<dc:creator>wethecom</dc:creator>
		<pubDate>Sun, 08 Nov 2009 09:47:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.thekua.com/atwork/?p=29#comment-75008</guid>
		<description>one trick i just learned
it speeds up the gui
if leave the focus of VS to goto any other application or what not
such as say Firefox to do some research..after a while VS goes into a hibernating mode or something and it takes a long time to get it responding again
what i learned is if you plan to leave focus of VS highlight some text
in the code window...and when you return focus to visual studio it is still ready to go ..without waiting for it catch back up with itself
...this is in 2009 version..it works great for me so far but its not perfect
let me know if it helps out ...and works for you</description>
		<content:encoded><![CDATA[<p>one trick i just learned<br />
it speeds up the gui<br />
if leave the focus of VS to goto any other application or what not<br />
such as say Firefox to do some research..after a while VS goes into a hibernating mode or something and it takes a long time to get it responding again<br />
what i learned is if you plan to leave focus of VS highlight some text<br />
in the code window&#8230;and when you return focus to visual studio it is still ready to go ..without waiting for it catch back up with itself<br />
&#8230;this is in 2009 version..it works great for me so far but its not perfect<br />
let me know if it helps out &#8230;and works for you</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: thekua.com@work &#187; A more usable Visual Studio 2009</title>
		<link>http://www.thekua.com/atwork/2007/05/speeding-up-visual-studio-2005/comment-page-1/#comment-63632</link>
		<dc:creator>thekua.com@work &#187; A more usable Visual Studio 2009</dc:creator>
		<pubDate>Fri, 29 May 2009 12:37:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.thekua.com/atwork/?p=29#comment-63632</guid>
		<description>[...] of the tips I wrote a long time ago for speeding up Visual Studio 2005 still apply. I&#8217;ve found that the preferred replacement for Cool Commands is the Power [...]</description>
		<content:encoded><![CDATA[<p>[...] of the tips I wrote a long time ago for speeding up Visual Studio 2005 still apply. I&#8217;ve found that the preferred replacement for Cool Commands is the Power [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Abishek.R.Srikaanth</title>
		<link>http://www.thekua.com/atwork/2007/05/speeding-up-visual-studio-2005/comment-page-1/#comment-5061</link>
		<dc:creator>Abishek.R.Srikaanth</dc:creator>
		<pubDate>Fri, 11 Jan 2008 12:15:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.thekua.com/atwork/?p=29#comment-5061</guid>
		<description>Remove .REFRESH FILES to speed build time of VS 2005</description>
		<content:encoded><![CDATA[<p>Remove .REFRESH FILES to speed build time of VS 2005</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug Porter</title>
		<link>http://www.thekua.com/atwork/2007/05/speeding-up-visual-studio-2005/comment-page-1/#comment-3184</link>
		<dc:creator>Doug Porter</dc:creator>
		<pubDate>Wed, 21 Nov 2007 22:06:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.thekua.com/atwork/?p=29#comment-3184</guid>
		<description>I was having many of the same problems listed here, for me turning off Navigation bar also helped.  

One problem I was having that I haven&#039;t seen mentioned is that while debugging in C++ if I did Step Over or Step Into it would take 3+ seconds to move a single line.   I finally fixed it by clearing all my breakpoints and now it runs like it used to.</description>
		<content:encoded><![CDATA[<p>I was having many of the same problems listed here, for me turning off Navigation bar also helped.  </p>
<p>One problem I was having that I haven&#8217;t seen mentioned is that while debugging in C++ if I did Step Over or Step Into it would take 3+ seconds to move a single line.   I finally fixed it by clearing all my breakpoints and now it runs like it used to.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Georges Vivier</title>
		<link>http://www.thekua.com/atwork/2007/05/speeding-up-visual-studio-2005/comment-page-1/#comment-2832</link>
		<dc:creator>Georges Vivier</dc:creator>
		<pubDate>Wed, 14 Nov 2007 21:17:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.thekua.com/atwork/?p=29#comment-2832</guid>
		<description>Hi there!

First , I&#039;d like to thank everyone for taking the time to post their findings. They helped alot.

Now it&#039;s my turn.

So I&#039;d like to share a solution I figured out to some ridiculously long builds I consistently experienced with VB.NET projects prepared for COM compatibility (VBA, VBS)

Unchecking the &quot;Register for COM interop&quot; property for this kind of project, reduced build times from several minutes to a few seconds !!!

I only need to recheck the property for the final build before actual deployment for testing or production.

I&#039;m running an isolated VS2K5 Team System SP1 on WXP Pro SP2 virtual machine (VMWARE)

Cheers!!!</description>
		<content:encoded><![CDATA[<p>Hi there!</p>
<p>First , I&#8217;d like to thank everyone for taking the time to post their findings. They helped alot.</p>
<p>Now it&#8217;s my turn.</p>
<p>So I&#8217;d like to share a solution I figured out to some ridiculously long builds I consistently experienced with VB.NET projects prepared for COM compatibility (VBA, VBS)</p>
<p>Unchecking the &#8220;Register for COM interop&#8221; property for this kind of project, reduced build times from several minutes to a few seconds !!!</p>
<p>I only need to recheck the property for the final build before actual deployment for testing or production.</p>
<p>I&#8217;m running an isolated VS2K5 Team System SP1 on WXP Pro SP2 virtual machine (VMWARE)</p>
<p>Cheers!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Knowtu &#187; The Pig On My Desktop</title>
		<link>http://www.thekua.com/atwork/2007/05/speeding-up-visual-studio-2005/comment-page-1/#comment-2567</link>
		<dc:creator>Knowtu &#187; The Pig On My Desktop</dc:creator>
		<pubDate>Mon, 29 Oct 2007 23:49:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.thekua.com/atwork/?p=29#comment-2567</guid>
		<description>[...] 2 gig ram laptop running XP with a primary 7200 rpm drive. I followed some of the steps in this useful visual studio speed up guide but my main gripes are the building and startup which this won&#8217;t [...]</description>
		<content:encoded><![CDATA[<p>[...] 2 gig ram laptop running XP with a primary 7200 rpm drive. I followed some of the steps in this useful visual studio speed up guide but my main gripes are the building and startup which this won&#8217;t [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will Buttitta</title>
		<link>http://www.thekua.com/atwork/2007/05/speeding-up-visual-studio-2005/comment-page-1/#comment-1763</link>
		<dc:creator>Will Buttitta</dc:creator>
		<pubDate>Wed, 05 Sep 2007 14:59:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.thekua.com/atwork/?p=29#comment-1763</guid>
		<description>I also was frustrated by a delay while typing (especially in code comments).  For me unchecking the &quot;Navigation Bar&quot; in &quot;Tools::Options::Text Editor::C#::General&quot; fixed the problem.</description>
		<content:encoded><![CDATA[<p>I also was frustrated by a delay while typing (especially in code comments).  For me unchecking the &#8220;Navigation Bar&#8221; in &#8220;Tools::Options::Text Editor::C#::General&#8221; fixed the problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sansay</title>
		<link>http://www.thekua.com/atwork/2007/05/speeding-up-visual-studio-2005/comment-page-1/#comment-1343</link>
		<dc:creator>sansay</dc:creator>
		<pubDate>Thu, 09 Aug 2007 16:12:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.thekua.com/atwork/?p=29#comment-1343</guid>
		<description>Yes, I do remember VS6 speed. In fact I can compare it every day, and yes it&#039;s so much faster. Too bad about VS2005 unable to use multiple core processors, as my work machine has an 8 cores CPU.

I tried many of the suggestions listed above, but it doesn&#039;t prevent  slow response every time I type something. The cursor disappear for a couple of seconds. It&#039;s really irritating.
Anybody know what&#039;s causing this?</description>
		<content:encoded><![CDATA[<p>Yes, I do remember VS6 speed. In fact I can compare it every day, and yes it&#8217;s so much faster. Too bad about VS2005 unable to use multiple core processors, as my work machine has an 8 cores CPU.</p>
<p>I tried many of the suggestions listed above, but it doesn&#8217;t prevent  slow response every time I type something. The cursor disappear for a couple of seconds. It&#8217;s really irritating.<br />
Anybody know what&#8217;s causing this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hoary Germ</title>
		<link>http://www.thekua.com/atwork/2007/05/speeding-up-visual-studio-2005/comment-page-1/#comment-773</link>
		<dc:creator>Hoary Germ</dc:creator>
		<pubDate>Tue, 31 Jul 2007 03:44:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.thekua.com/atwork/?p=29#comment-773</guid>
		<description>A lot of Visual Studio 2005&#039;s slowdown, as discovered with by procexp, is due to SourceSafe integration.  Right-clicking anywhere in Visual Studio causes all the .vcproj/.csproj files to be read from disk.  Running the debugger causes _all_ files to be read from disk.  All kind of stuff like this has me looking for a better alternative.  Using vi with msbuild is too slow because msbuild cannot utilize multiple cores (at least not until Orcas comes out).  Does anyone remember how damn fast Visual Studio 6 was?</description>
		<content:encoded><![CDATA[<p>A lot of Visual Studio 2005&#8217;s slowdown, as discovered with by procexp, is due to SourceSafe integration.  Right-clicking anywhere in Visual Studio causes all the .vcproj/.csproj files to be read from disk.  Running the debugger causes _all_ files to be read from disk.  All kind of stuff like this has me looking for a better alternative.  Using vi with msbuild is too slow because msbuild cannot utilize multiple cores (at least not until Orcas comes out).  Does anyone remember how damn fast Visual Studio 6 was?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Speeding Up VS.NET 2005 &#171; Smart Thinker</title>
		<link>http://www.thekua.com/atwork/2007/05/speeding-up-visual-studio-2005/comment-page-1/#comment-745</link>
		<dc:creator>Speeding Up VS.NET 2005 &#171; Smart Thinker</dc:creator>
		<pubDate>Tue, 24 Jul 2007 19:26:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.thekua.com/atwork/?p=29#comment-745</guid>
		<description>[...] Speeding Up VS.NET&#160;2005  Hi, A very interesting and useful content I found on the internet that describes how can we improve the reponse time of Visual Studio.Net 2005 while development. It is a much needed as there has been a problem with VS.NET 2005 eating loads of resources unwantedly. See Details [...]</description>
		<content:encoded><![CDATA[<p>[...] Speeding Up VS.NET&nbsp;2005  Hi, A very interesting and useful content I found on the internet that describes how can we improve the reponse time of Visual Studio.Net 2005 while development. It is a much needed as there has been a problem with VS.NET 2005 eating loads of resources unwantedly. See Details [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
