Note that there are some explanatory texts on larger screens.

plurals
  1. POVisual Studio 2008 crashes when debugging
    text
    copied!<p>I have a solution filled entirely with .NET 3.5 projects (so the 2.0 CLR) - today after rebuilding my project (and having made only minor changes to the codebase) I rebuilt it and hit Debug.</p> <p>Immediately VS crashed to the desktop. The Application Event Log had this entry:</p> <blockquote> <p>.NET Runtime version 2.0.50727.3625 - Fatal Execution Engine Error (7A05AE08) (80131506)</p> </blockquote> <p>I relaunched VS and tried again, hitting Debug straight away (without a rebuild)</p> <blockquote> <p>.NET Runtime version 2.0.50727.3625 - Fatal Execution Engine Error (000006427F827D6F) (0)</p> </blockquote> <p>I cleaned the solution, rebuilt it, and I still get this problem.</p> <p>I haven't rebooted just yet, but I'll give that a try in a few minutes.</p> <p>My computer has been switched off the past week, but I don't think that has anything to do with it.</p> <p>I've tried searching the web for these error codes, there was only one relevant result[1] which suggested running this utility[2], however when I ran the utility it told me that all of my .NET Framework installations were correctly configured with no corruption detected.</p> <p>[1] <a href="http://social.msdn.microsoft.com/Forums/en/vssetup/thread/938126ed-c98d-4c9c-94d4-aedd22a27822" rel="nofollow">http://social.msdn.microsoft.com/Forums/en/vssetup/thread/938126ed-c98d-4c9c-94d4-aedd22a27822</a></p> <p>[2] <a href="http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx" rel="nofollow">http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx</a></p> <p>Unfortunately it's a weekend, and Microsoft's VS support team are only available Monday to Friday.</p> <p>UPDATE:</p> <p>I rebooted, but I still get the same problem. My system has every Windows Update installed too.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload