<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>VS 2003 can not debug .NET 2.0 apps.</title><link>http://blogs.msdn.com/jmstall/archive/2005/11/30/everett-cant-debug-Whidbey.aspx</link><description>Somebody asked here on the forums if you can use VS 2003 to debug .NET 2.0 (whidbey) apps. Unfortunately, the answer is no. VS 2003 can not debug .NET 2.0 apps. It is a restriction in the underlying .NET debugging services (see below) You can still use</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: VS 2003 can not debug .NET 2.0 apps.</title><link>http://blogs.msdn.com/jmstall/archive/2005/11/30/everett-cant-debug-Whidbey.aspx#499505</link><pubDate>Fri, 02 Dec 2005 22:59:04 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:499505</guid><dc:creator>Andrei Ignat</dc:creator><description>I have not expected that VS2003 can debug 2005 programs... but yes, I expect the viceversa.&lt;br&gt;I am used with this from Word - each version of word can open &amp;quot;younger&amp;quot; created docs  - but not oldest.&lt;br&gt;And for a reason ... usually you can not know very well the future - but it easier to know the past</description></item><item><title>re: VS 2003 can not debug .NET 2.0 apps.</title><link>http://blogs.msdn.com/jmstall/archive/2005/11/30/everett-cant-debug-Whidbey.aspx#529052</link><pubDate>Fri, 10 Feb 2006 04:20:44 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:529052</guid><dc:creator>Matt</dc:creator><description>My old Java IDEs work with my newer JAVA SDKs. I would expect the Visual Studio 2003 to be able to compile .Net 2.0 code and the Object process should be able to parse 2.0's classes using the System.Reflection class.</description></item><item><title>re: VS 2003 can not debug .NET 2.0 apps.</title><link>http://blogs.msdn.com/jmstall/archive/2005/11/30/everett-cant-debug-Whidbey.aspx#529265</link><pubDate>Fri, 10 Feb 2006 10:21:40 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:529265</guid><dc:creator>jmstall</dc:creator><description>Matt - that's a noble goal, and it would be nice if VS worked that way. &lt;br&gt;Regarding Reflection: there are some inate limitations to your proposal. How would you express a V2.0 Generic type through V1.1's reflection? (which does not know about generics).&lt;br&gt;Solutions usually fall into 2 camps:&lt;br&gt;1) &amp;quot;type erasure&amp;quot;: Basically, all V2 types would look like V1 types. This means you couldn't instantiate a generic type across libraries.&lt;br&gt;2) shoehorn v2 to look like v1 as much as possible. Hwoever, even if the API signatures stay the same, there will almost always be some broken semantics / invariant. If you push a tool in the right way, the tool will hit that and explode. For example, a non-generics-aware V1 tool may get confused when it sees the same method compiled two different ways.&lt;br&gt;</description></item><item><title>Caveats about managed JIT-debugging </title><link>http://blogs.msdn.com/jmstall/archive/2005/11/30/everett-cant-debug-Whidbey.aspx#676757</link><pubDate>Mon, 24 Jul 2006 18:15:57 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:676757</guid><dc:creator>Mike Stall's .NET Debugging Blog</dc:creator><description>I received some questions in the mailbag about what Debugger.Launch actually does. Debugger.Launch the...</description></item><item><title>Debugger and Versioning</title><link>http://blogs.msdn.com/jmstall/archive/2005/11/30/everett-cant-debug-Whidbey.aspx#2215366</link><pubDate>Sat, 21 Apr 2007 05:32:29 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2215366</guid><dc:creator>Mike Stall's .NET Debugging Blog</dc:creator><description>&lt;p&gt;&amp;quot;Which versions of a managed debugger (eg, Visual Studio) can debug which versions of the CLR? And How?&amp;quot;&lt;/p&gt;
</description></item><item><title>Debugger and Versioning link fest</title><link>http://blogs.msdn.com/jmstall/archive/2005/11/30/everett-cant-debug-Whidbey.aspx#3704707</link><pubDate>Thu, 05 Jul 2007 15:20:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3704707</guid><dc:creator>Noticias externas</dc:creator><description>&lt;p&gt;I&amp;amp;#39;ve had enough &amp;amp;quot;Debugger + Versioning&amp;amp;quot; posts to go back and create a versioning category&lt;/p&gt;
</description></item></channel></rss>