<?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: VS.Net 2005 unable to start debugging</title>
	<atom:link href="http://jfw.id.au/2006/02/28/vsnet-2005-unable-to-start-debugging/feed/" rel="self" type="application/rss+xml" />
	<link>http://jfw.id.au/2006/02/28/vsnet-2005-unable-to-start-debugging/</link>
	<description>the mutterings of a part time nutcase.</description>
	<pubDate>Sun, 20 May 2012 08:24:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Me.</title>
		<link>http://jfw.id.au/2006/02/28/vsnet-2005-unable-to-start-debugging/comment-page-1/#comment-102</link>
		<dc:creator>Me.</dc:creator>
		<pubDate>Tue, 21 Mar 2006 22:23:28 +0000</pubDate>
		<guid isPermaLink="false">http://jfw.id.au/2006/02/28/vsnet-2005-unable-to-start-debugging/#comment-102</guid>
		<description>Yeah I found the fact that 2003 install works fine (in the correct sequence of course) and the 2005 doesn't most annoying.  I would have assumed that the 2003 install had issues and they could have rectified them in 2005.  Oh well... Live and learn.

I wasn't aware that I was running the Terminal Services service, but a quick check shows that it is 
&lt;blockquote&gt;
The underpinning of Remote Desktop (including RD for Administrators), Fast User Switching, Remote Assistance, and Terminal Server
&lt;/blockquote&gt;

I find it interesting that VS2005 requires terminal services... but it works now, and that is the main thing.</description>
		<content:encoded><![CDATA[<p>Yeah I found the fact that 2003 install works fine (in the correct sequence of course) and the 2005 doesn&#8217;t most annoying.  I would have assumed that the 2003 install had issues and they could have rectified them in 2005.  Oh well&#8230; Live and learn.</p>
<p>I wasn&#8217;t aware that I was running the Terminal Services service, but a quick check shows that it is </p>
<blockquote><p>
The underpinning of Remote Desktop (including RD for Administrators), Fast User Switching, Remote Assistance, and Terminal Server
</p></blockquote>
<p>I find it interesting that VS2005 requires terminal services&#8230; but it works now, and that is the main thing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dylan</title>
		<link>http://jfw.id.au/2006/02/28/vsnet-2005-unable-to-start-debugging/comment-page-1/#comment-101</link>
		<dc:creator>Dylan</dc:creator>
		<pubDate>Tue, 21 Mar 2006 22:07:01 +0000</pubDate>
		<guid isPermaLink="false">http://jfw.id.au/2006/02/28/vsnet-2005-unable-to-start-debugging/#comment-101</guid>
		<description>I recently installed vb.net 2005 express edition on my home box to get a bit of a feel about it, and I had a similar error when trying to run a project.

While I can't remember the exact wording, the error was that it failed to start the debugger. The problem? (after much googling) My terminal services service was not running - I must have disabled it in a frenzy of game-performance-related disablement of system function. (or better security, perhaps?)

Anyway, after restarting the service everything worked fine, but it took a bit of googling to find the issue and from memory the 2003 install worked fine without it. 

So it's entirely possible to be working away with 2003 and upgrade to 2005 only to have it fail to work without explaination..... awesome!!</description>
		<content:encoded><![CDATA[<p>I recently installed vb.net 2005 express edition on my home box to get a bit of a feel about it, and I had a similar error when trying to run a project.</p>
<p>While I can&#8217;t remember the exact wording, the error was that it failed to start the debugger. The problem? (after much googling) My terminal services service was not running - I must have disabled it in a frenzy of game-performance-related disablement of system function. (or better security, perhaps?)</p>
<p>Anyway, after restarting the service everything worked fine, but it took a bit of googling to find the issue and from memory the 2003 install worked fine without it. </p>
<p>So it&#8217;s entirely possible to be working away with 2003 and upgrade to 2005 only to have it fail to work without explaination&#8230;.. awesome!!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

