<?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>How to Stop on First Chance Exceptions - Visual Studio .NET 2003</title><link>http://blogs.msdn.com/davidklinems/archive/2005/07/18/440150.aspx</link><description>Last week, I talked about what first chance exceptions are and mentioned that you could configure the Visual Studio debugger to allow you to debug them. Using Visual Studio .NET 2003, you can configure how the debugger handles first chance exceptions</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>How to Stop on First Chance Exceptions - Visual Studio 2005</title><link>http://blogs.msdn.com/davidklinems/archive/2005/07/18/440150.aspx#440633</link><pubDate>Wed, 20 Jul 2005 02:04:23 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:440633</guid><dc:creator>David Kline</dc:creator><description>Yesterday, I talked about how to enable stopping in the debugger on first chance exceptions when using...</description></item><item><title>re: How to Stop on First Chance Exceptions - Visual Studio .NET 2003</title><link>http://blogs.msdn.com/davidklinems/archive/2005/07/18/440150.aspx#440973</link><pubDate>Wed, 20 Jul 2005 19:44:40 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:440973</guid><dc:creator>Phillip</dc:creator><description>I typically change all the exceptions to stop in the debugger when thrown. Then I selectively go through and pick which ones to let the machine handle. Plus I end up adding several Win32 exceptions that COM and MSXML throw.&lt;br&gt;&lt;br&gt;Then after a few days VS 2003 will loose all my changes and I have to start all over. (Once I notice).&lt;br&gt;&lt;br&gt;So my comment/request is, is there a way to set these options via a macro or script or addin? Or some way to export-import these settings?&lt;br&gt;&lt;br&gt;And I really wish MS had set the default to break into the debugger on them. Too many are just ignored by programmers because it does not throw up a big message box.</description></item><item><title>re: How to Stop on First Chance Exceptions - Visual Studio .NET 2003</title><link>http://blogs.msdn.com/davidklinems/archive/2005/07/18/440150.aspx#441114</link><pubDate>Thu, 21 Jul 2005 00:14:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:441114</guid><dc:creator>DavidKlineMS</dc:creator><description>Phillip,  The changes you make to the debugger's exception handling is on a per project basis.  When you save the project, these changes should also be saved.  If this same behavior occurs in Visual Studio 2005 beta 2, please report it via the Product Feeback Center (&lt;a rel="nofollow" target="_new" href="http://lab.msdn.microsoft.com/productfeedback"&gt;http://lab.msdn.microsoft.com/productfeedback&lt;/a&gt;).&lt;br&gt;&lt;br&gt;Thanks!&lt;br&gt;--DK</description></item><item><title>The Mobile Minute 106</title><link>http://blogs.msdn.com/davidklinems/archive/2005/07/18/440150.aspx#441892</link><pubDate>Fri, 22 Jul 2005 21:00:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:441892</guid><dc:creator>Nino.Mobile</dc:creator><description>Since last night (Thursday), my smartphone has, literally, been my conduit to the world; I had to drive...</description></item><item><title>re: How to Stop on First Chance Exceptions - Visual Studio .NET 2003</title><link>http://blogs.msdn.com/davidklinems/archive/2005/07/18/440150.aspx#442065</link><pubDate>Sat, 23 Jul 2005 02:29:29 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:442065</guid><dc:creator>fish</dc:creator><description>&amp;lt;P&amp;gt;hi i have first-chance exception in my program in both debug and release module. the wield thing is this exception only happen in my machine, if i copy the whole project to other machines, and recompile, there is no such problem!!!!(drive me craze) can u tell me some possibilities about such situation? thanks [Edit: email address removed]&amp;lt;/P&amp;gt;</description></item><item><title>re: How to Stop on First Chance Exceptions - Visual Studio .NET 2003</title><link>http://blogs.msdn.com/davidklinems/archive/2005/07/18/440150.aspx#442075</link><pubDate>Sat, 23 Jul 2005 02:45:17 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:442075</guid><dc:creator>DavidKlineMS</dc:creator><description>Fish, first chance exceptions do not necessarilly indicate a problem in the application.  If you configure Visual Studio to stop when the exception is thrown, you may be able to determine why it is occuring on your specific system.&lt;br&gt;-- DK</description></item><item><title>Configuring How the Visual Studio Debugger Handles Custom Exceptions</title><link>http://blogs.msdn.com/davidklinems/archive/2005/07/18/440150.aspx#445200</link><pubDate>Sat, 30 Jul 2005 03:04:01 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:445200</guid><dc:creator>David Kline</dc:creator><description>A few days ago, I posted on how to configure the debugger to stop on first chance exceptions in Visual...</description></item><item><title>First chance exception | keyongtech</title><link>http://blogs.msdn.com/davidklinems/archive/2005/07/18/440150.aspx#9362169</link><pubDate>Thu, 22 Jan 2009 06:36:53 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9362169</guid><dc:creator>First chance exception | keyongtech</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.keyongtech.com/716230-first-chance-exception"&gt;http://www.keyongtech.com/716230-first-chance-exception&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>