<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>digitalMoto.net &#187; Visual Studio 2008</title>
	<atom:link href="http://digitalMoto.net/blog/tag/visual-studio-2008/feed/" rel="self" type="application/rss+xml" />
	<link>http://digitalMoto.net/blog</link>
	<description>Off-idle banter on motorcycling, software development and life in the Pacific Northwest.</description>
	<lastBuildDate>Wed, 08 Feb 2012 22:29:58 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Testing execution timeout in Visual Studio 2008 Team System</title>
		<link>http://digitalMoto.net/blog/2009/12/09/testing-execution-timeout-in-visual-studio-2008-team-system/</link>
		<comments>http://digitalMoto.net/blog/2009/12/09/testing-execution-timeout-in-visual-studio-2008-team-system/#comments</comments>
		<pubDate>Wed, 09 Dec 2009 19:30:41 +0000</pubDate>
		<dc:creator>digital</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[Debugging]]></category>
		<category><![CDATA[Testing]]></category>
		<category><![CDATA[Visual Studio 2008]]></category>

		<guid isPermaLink="false">http://digitalMoto.net/blog/?p=1034</guid>
		<description><![CDATA[With Visual Studio Team System, the LocalTestRun.testrunconfig file controls execution parameters for running tests. The default timeout on individual tests is 30 minutes. Ouch! Solution: Double click on the &#8216;Solution Items\LocalTestRun.testrunconfig&#8217; file. Select &#8216;Test Timeouts&#8217; Set the individual test time to your preference or set a total time abort if you prefer.]]></description>
		<wfw:commentRss>http://digitalMoto.net/blog/2009/12/09/testing-execution-timeout-in-visual-studio-2008-team-system/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fixed: API restriction w/ Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll</title>
		<link>http://digitalMoto.net/blog/2009/11/11/fixed-api-restriction-w-microsoftvisualstudioqualitytoolsunittestframeworkdll/</link>
		<comments>http://digitalMoto.net/blog/2009/11/11/fixed-api-restriction-w-microsoftvisualstudioqualitytoolsunittestframeworkdll/#comments</comments>
		<pubDate>Wed, 11 Nov 2009 18:36:42 +0000</pubDate>
		<dc:creator>digital</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[Debugging]]></category>
		<category><![CDATA[Visual Studio 2008]]></category>
		<category><![CDATA[Win7]]></category>

		<guid isPermaLink="false">http://digitalMoto.net/blog/?p=978</guid>
		<description><![CDATA[I wrote about this a couple days ago. I have now confirmed my fix. ENV: Win7 Ent x64, VS 2008 SP1 Problem: API restriction: The assembly &#8216;file:///c:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PublicAssemblies\Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll&#8217; has already loaded from a different location. It cannot be loaded from a new location within the same appdomain. Solution: Make sure you [...]]]></description>
		<wfw:commentRss>http://digitalMoto.net/blog/2009/11/11/fixed-api-restriction-w-microsoftvisualstudioqualitytoolsunittestframeworkdll/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Problems with Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll</title>
		<link>http://digitalMoto.net/blog/2009/11/09/problems-with-microsoftvisualstudioqualitytoolsunittestframeworkdll/</link>
		<comments>http://digitalMoto.net/blog/2009/11/09/problems-with-microsoftvisualstudioqualitytoolsunittestframeworkdll/#comments</comments>
		<pubDate>Mon, 09 Nov 2009 22:12:07 +0000</pubDate>
		<dc:creator>digital</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[Unit Testing]]></category>
		<category><![CDATA[Visual Studio 2008]]></category>

		<guid isPermaLink="false">http://digitalMoto.net/blog/?p=969</guid>
		<description><![CDATA[I have been having problems with the internal testing library in Visual Studio. I get an API error. &#8220;The assembly has already been loaded and cannot be loaded into the appDomain.&#8221; Really? &#60;sarcastic response&#62; Everyone on the team has had intermittent issues for a couple months. One solution seemed to be to clean the solution, [...]]]></description>
		<wfw:commentRss>http://digitalMoto.net/blog/2009/11/09/problems-with-microsoftvisualstudioqualitytoolsunittestframeworkdll/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The components for the 64-bit debugger are not registered&#8230;</title>
		<link>http://digitalMoto.net/blog/2009/09/02/the-components-for-the-64-bit-debugger-are-not-registered/</link>
		<comments>http://digitalMoto.net/blog/2009/09/02/the-components-for-the-64-bit-debugger-are-not-registered/#comments</comments>
		<pubDate>Thu, 03 Sep 2009 05:49:26 +0000</pubDate>
		<dc:creator>digital</dc:creator>
				<category><![CDATA[Undefined]]></category>
		<category><![CDATA[Debugging]]></category>
		<category><![CDATA[Visual Studio 2008]]></category>
		<category><![CDATA[x64]]></category>

		<guid isPermaLink="false">http://digitalMoto.net/blog/?p=717</guid>
		<description><![CDATA[So I was getting this error: Error while trying to run project: Unable to start debugging. The components for the 64-bit debugger are not registered. Please repair your Visual Studio 2008 Remote Debugger installation via &#8216;Add or Remove Programs&#8217; in Control Panel. A little surfing and I found a solution. Install the debugger! The 64-bit [...]]]></description>
		<wfw:commentRss>http://digitalMoto.net/blog/2009/09/02/the-components-for-the-64-bit-debugger-are-not-registered/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>An error occurred while signing: SignTool.exe not found.</title>
		<link>http://digitalMoto.net/blog/2009/08/25/an-error-occurred-while-signing-signtoolexe-not-found/</link>
		<comments>http://digitalMoto.net/blog/2009/08/25/an-error-occurred-while-signing-signtoolexe-not-found/#comments</comments>
		<pubDate>Tue, 25 Aug 2009 07:12:11 +0000</pubDate>
		<dc:creator>digital</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[ClickOnce Deployment]]></category>
		<category><![CDATA[SDK]]></category>
		<category><![CDATA[Visual Studio 2008]]></category>
		<category><![CDATA[Win7]]></category>

		<guid isPermaLink="false">http://digitalMoto.net/blog/?p=696</guid>
		<description><![CDATA[This error popped up tonight when I tried to publish an app via ClickOnce deployment. This was the first time I had tried to publish since building up my latest machine. I had assumed the signing tool would have installed when I installed VS2008 but I was wrong. After seaching around for a solution, I [...]]]></description>
		<wfw:commentRss>http://digitalMoto.net/blog/2009/08/25/an-error-occurred-while-signing-signtoolexe-not-found/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

