<?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>Remarks: Edit and Continue in ASP.NET</title><link>http://blogs.msdn.com/b/bgold/archive/2004/04/19/115954.aspx</link><description>Jonathan Goodyear writes a fairly balanced and technically accurate overview of the Edit and Continue story in ASP.NET , even if the title is somewhat negative J . Since I was quoted, I wanted to make sure to paint the entire picture, without word limit</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>My real peek at VB 2005!</title><link>http://blogs.msdn.com/b/bgold/archive/2004/04/19/115954.aspx#675030</link><pubDate>Sat, 22 Jul 2006 21:48:20 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:675030</guid><dc:creator>Living .NET... </dc:creator><description>My start with VS 2005 has rather been a bit sluggish. I didn&amp;amp;amp;#8217;t really work much with the Community...&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=675030" width="1" height="1"&gt;</description></item><item><title>re: Remarks: Edit and Continue in ASP.NET</title><link>http://blogs.msdn.com/b/bgold/archive/2004/04/19/115954.aspx#466010</link><pubDate>Wed, 14 Sep 2005 15:47:08 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:466010</guid><dc:creator>Tim Bushell</dc:creator><description>Astounding. What an appalling decision, Microsoft. Do you have any idea how much time and productivity is lost by trying to debug web applications without e&amp;amp;c???? I estimate at least 40% slower without it. &lt;br&gt;&lt;br&gt;I have been absolutely hanging out for this, and to hear that everyone bar us 'plebs' in asp.net development will get it is devastating.&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=466010" width="1" height="1"&gt;</description></item><item><title>re: ASP.NET 2005 Won't Have Edit and Continue</title><link>http://blogs.msdn.com/b/bgold/archive/2004/04/19/115954.aspx#224322</link><pubDate>Thu, 02 Sep 2004 02:11:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:224322</guid><dc:creator>Clint Caraway</dc:creator><description>&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=224322" width="1" height="1"&gt;</description></item><item><title>My real peek at VB 2005!</title><link>http://blogs.msdn.com/b/bgold/archive/2004/04/19/115954.aspx#191024</link><pubDate>Thu, 22 Jul 2004 14:33:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:191024</guid><dc:creator>An agglomeration of my thoughts</dc:creator><description>&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=191024" width="1" height="1"&gt;</description></item><item><title>My real peek at VB 2005!</title><link>http://blogs.msdn.com/b/bgold/archive/2004/04/19/115954.aspx#191016</link><pubDate>Thu, 22 Jul 2004 14:14:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:191016</guid><dc:creator>An agglomeration of my thoughts</dc:creator><description>&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=191016" width="1" height="1"&gt;</description></item><item><title>re: Remarks: Edit and Continue in ASP.NET</title><link>http://blogs.msdn.com/b/bgold/archive/2004/04/19/115954.aspx#129541</link><pubDate>Tue, 11 May 2004 07:37:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:129541</guid><dc:creator>dan owens</dc:creator><description>wow - I totally agree with chris willis above - E&amp;amp;C is by far #1 on my list -  even moreso that getting remote debugging to work. The problem is magnified with the time it takes .net to stop and restart then renavigate back to the code.  &lt;br&gt;&lt;br&gt;On the otherhand, I do have more time to get thru my email while waiting for my app to recycle...&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=129541" width="1" height="1"&gt;</description></item><item><title>re: Remarks: Edit and Continue in ASP.NET</title><link>http://blogs.msdn.com/b/bgold/archive/2004/04/19/115954.aspx#126188</link><pubDate>Wed, 05 May 2004 06:20:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:126188</guid><dc:creator>ghjghghghjg</dc:creator><description>jhjkhjhjhjkhjkl&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=126188" width="1" height="1"&gt;</description></item><item><title>This Sucks!</title><link>http://blogs.msdn.com/b/bgold/archive/2004/04/19/115954.aspx#117665</link><pubDate>Wed, 21 Apr 2004 21:54:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:117665</guid><dc:creator>chris willis</dc:creator><description>I have been impatiently counting the days until my beloved E&amp;amp;C (with VS2005) would return my debugging productivity back to me.  Not supported in ASP.NET?!?  ASP.NET is where you need it the most -- we don’t do win forms anymore!  I now have to wait at least 60 seconds for ANY little change in code to recompile and get back to where I was, and this is a major annoyance and productivity killer. With VB6 COM objects behind ASP I had to wait ZERO seconds to fix something and move along.  Now my days are filled with watching the output window while VS2003 does all that stuff it does just to fix one frikkin line of code.  I thought the problem would finally be solved, BUT NOT FOR ASP.NET?!?  E&amp;amp;C is what made classic VB so great.  Please, please, please Microsoft, put E&amp;amp;C in ASP.NET!&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=117665" width="1" height="1"&gt;</description></item><item><title>re: Remarks: Edit and Continue in ASP.NET</title><link>http://blogs.msdn.com/b/bgold/archive/2004/04/19/115954.aspx#117494</link><pubDate>Wed, 21 Apr 2004 17:47:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:117494</guid><dc:creator>Jeff Kirwan</dc:creator><description>Personally, I don't miss E&amp;amp;C. Never really used it, don't intend to start. It's really a philosophical decision more than anything. Debugging should be a process, not a &amp;quot;quick fix&amp;quot;. By using E&amp;amp;C, you are vulnerable to making snap decisions which could affect the rest of your application in ways you did not take the time to consider. In my mind, it's much better to take a step back, analyze the source of the error, and implement a fix after considering all of the consequences.&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=117494" width="1" height="1"&gt;</description></item><item><title>re: Remarks: Edit and Continue in ASP.NET</title><link>http://blogs.msdn.com/b/bgold/archive/2004/04/19/115954.aspx#116475</link><pubDate>Tue, 20 Apr 2004 06:56:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:116475</guid><dc:creator>Sean Chase</dc:creator><description>Better than nothing. :)&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=116475" width="1" height="1"&gt;</description></item></channel></rss>