<?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>What to do with a feature that only works 90% of the time?</title><link>http://blogs.msdn.com/b/jmstall/archive/2006/01/25/killing-unsafe-features.aspx</link><description>Imagine when you're designing a feature if there was an operation that was very useful 90% of the time; but the other 10% of the time it was provably and innately unsafe (either crashed, deadlocked, or gave back garbage). By "innately unsafe", I mean</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>Trivia about Managed debugging and Exit Process</title><link>http://blogs.msdn.com/b/jmstall/archive/2006/01/25/killing-unsafe-features.aspx#2516120</link><pubDate>Thu, 10 May 2007 06:52:13 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2516120</guid><dc:creator>Mike Stall's .NET Debugging Blog</dc:creator><description>&lt;p&gt;Process Shutdown is evil , as Raymond Chen recently blogged about in wonderful detail. This prompts me&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=2516120" width="1" height="1"&gt;</description></item></channel></rss>