<?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>I have heard of the BSoD - what's a WSoD?</title><link>http://blogs.msdn.com/rprabhu/archive/2005/08/11/450332.aspx</link><description>If you have used the Windows Forms designer in Visual Studio 2005 enough, chances are you may have occasionally seen a white error screen instead of the design time form. This screen, fondly referred to as WSoD in our team, shows up when error(s) are</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: I have heard of the BSoD - what's a WSoD?</title><link>http://blogs.msdn.com/rprabhu/archive/2005/08/11/450332.aspx#450356</link><pubDate>Thu, 11 Aug 2005 16:00:10 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:450356</guid><dc:creator>AndrewSeven</dc:creator><description>I have seen the  white ;)&lt;br&gt;&lt;br&gt;Having the event wire-ups dissapear from InitializeComponent() is a very tricky problem to find and fix. Things build and run, but buttons don't do anything. Looking at the code view, the missing wire-ups are in a collapsed region.&lt;br&gt;&lt;br&gt;It might seem odd, but maybe the choice should be to comment out the code instead of deleting it (And thus uncomment code before inserting a duplicate :S which is probably brutal ).&lt;br&gt;&lt;br&gt;Losing the wireups can be hard to spot, but the problem is how to be sure that you add them all back...unless they are there commented out.&lt;br&gt;&lt;br&gt;I prefer the obvious failure that stops me rather than silent failure that could slip by  unoticed.&lt;br&gt;&lt;br&gt;</description></item><item><title>re: I have heard of the BSoD - what's a WSoD?</title><link>http://blogs.msdn.com/rprabhu/archive/2005/08/11/450332.aspx#450501</link><pubDate>Thu, 11 Aug 2005 22:03:53 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:450501</guid><dc:creator>Shawn Burke</dc:creator><description>Probably worth some definitions here for those that don't have their MS-Glossary handy.&lt;br&gt;&lt;br&gt;BSoD: Blue Screen of Death&lt;br&gt;WSoD: White Screen of Darn&lt;br&gt;&lt;br&gt;We didn't think &amp;quot;death&amp;quot; was the right metaphor since in many cases it's like any other error message.  But it's never what you want to see.  Darn!</description></item><item><title>re: I have heard of the BSoD - what's a WSoD?</title><link>http://blogs.msdn.com/rprabhu/archive/2005/08/11/450332.aspx#543725</link><pubDate>Sat, 04 Mar 2006 22:56:26 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:543725</guid><dc:creator>franco rainusso</dc:creator><description>i ate a whole bunch of chinzaminos</description></item><item><title>re: I have heard of the BSoD - what's a WSoD?</title><link>http://blogs.msdn.com/rprabhu/archive/2005/08/11/450332.aspx#575075</link><pubDate>Wed, 12 Apr 2006 20:20:47 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:575075</guid><dc:creator>Christopher</dc:creator><description>[quote]We didn't think &amp;quot;death&amp;quot; was the right metaphor since in many cases it's like any other error message. But it's never what you want to see. Darn![/quote]&lt;br&gt;&lt;br&gt;I think the &amp;quot;darn&amp;quot; here is more appropriate because there isn't a &amp;quot;death&amp;quot; occuring like what happens with the BSoD (system crash). &amp;nbsp;The WSoD is more of a annoyance than a critical problem.&lt;br&gt;</description></item><item><title>re: I have heard of the BSoD - what's a WSoD?</title><link>http://blogs.msdn.com/rprabhu/archive/2005/08/11/450332.aspx#581449</link><pubDate>Sun, 23 Apr 2006 02:15:57 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:581449</guid><dc:creator>Ivar</dc:creator><description>I get WSoD with the following message &amp;quot;Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.&amp;quot; followed by a list of exceptions (no stacj trace. I do not understand what causes it. I did find a reference to a possible VS hotfix (?) and I also found a reference to removing indexing on project folders. It did help the first time, but now the problem is back and does not disappear. How can I proceed? How can I retrieve LoaderExceptions?</description></item><item><title>re: I have heard of the BSoD - what's a WSoD?</title><link>http://blogs.msdn.com/rprabhu/archive/2005/08/11/450332.aspx#581571</link><pubDate>Sun, 23 Apr 2006 13:08:49 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:581571</guid><dc:creator>Berke Sokhan</dc:creator><description>We get the same problem frequently, but the messages were generally related with our 3rd party components' licences.licx file. It seems like VS 2005 can't load this license file appropriately or in time, because we didn't write any code at that time only drag and drop. How can it be explained other than a bug?</description></item><item><title>Berke Sokhan &amp;raquo; White Screen of Darn - WSoD</title><link>http://blogs.msdn.com/rprabhu/archive/2005/08/11/450332.aspx#581576</link><pubDate>Sun, 23 Apr 2006 13:39:38 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:581576</guid><dc:creator>Berke Sokhan » White Screen of Darn - WSoD</dc:creator><description>PingBack from &lt;a rel="nofollow" target="_new" href="http://berkesokhan.wordpress.com/2006/04/23/white-screen-of-darn-wsod/"&gt;http://berkesokhan.wordpress.com/2006/04/23/white-screen-of-darn-wsod/&lt;/a&gt;</description></item><item><title>re: I have heard of the BSoD - what's a WSoD?</title><link>http://blogs.msdn.com/rprabhu/archive/2005/08/11/450332.aspx#582382</link><pubDate>Mon, 24 Apr 2006 22:34:11 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:582382</guid><dc:creator>rprabhu</dc:creator><description>One way of getting more information when you see a WSoD (and the information provided there isn't sufficient) is to attach a debugger (maybe another instance of VS 2005) to Visual Studio (devenv.exe), run through the problem scenario and see what exceptions get thrown.&lt;br&gt;&lt;br&gt;If you suspect you found a bug in VS 2005 or have any suggestion/comment, please log it through &lt;a rel="nofollow" target="_new" href="http://lab.msdn.microsoft.com/productfeedback/"&gt;http://lab.msdn.microsoft.com/productfeedback/&lt;/a&gt;. This is the ideal way to submit feedback, since both you and the product team can track it through resolution.</description></item><item><title>re: I have heard of the BSoD - what's a WSoD?</title><link>http://blogs.msdn.com/rprabhu/archive/2005/08/11/450332.aspx#600643</link><pubDate>Thu, 18 May 2006 08:18:26 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:600643</guid><dc:creator>Thinh</dc:creator><description>No, I have been heard of the BSoD alot but WSoD is never.&lt;br&gt;&lt;br&gt;Sometimes when I install alot of software for my Palm, I have been saw a WSoD similar when windows error but WSoD not provide any reason.</description></item><item><title>WSOD - White Screen of Death in Winforms Designer</title><link>http://blogs.msdn.com/rprabhu/archive/2005/08/11/450332.aspx#1484195</link><pubDate>Wed, 17 Jan 2007 19:42:05 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1484195</guid><dc:creator>David Truxall</dc:creator><description>&lt;p&gt;I've seen it many times in the past, now it has a name&lt;/p&gt;
</description></item></channel></rss>