tag:blogger.com,1999:blog-10748614.post113214843855462876..comments2024-02-28T12:34:09.691-05:00Comments on FrazzledDad: The Joys of Crashing SoftwareJim Holmeshttp://www.blogger.com/profile/05869146736565695900noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-10748614.post-1132254403684999582005-11-17T14:06:00.000-05:002005-11-17T14:06:00.000-05:00Since it doesn't look like trackbacks are enabled,...Since it doesn't look like trackbacks are enabled, I want to close this thread by linking to Jim's next couple of posts where he discovers that it is an Add-in issue and gets VS 2005 working.<BR/><BR/>http://frazzleddad.blogspot.com/2005/11/visual-studio-crashes-update.html<BR/><BR/>and<BR/><BR/>http://frazzleddad.blogspot.com/2005/11/vs-2005-crashes-fixed.htmlAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-10748614.post-1132173024820894232005-11-16T15:30:00.000-05:002005-11-16T15:30:00.000-05:00Hey there Sara. You certainly don't have to intro...Hey there Sara. You certainly don't have to introduce yourself here -- I've been a fan of your blog for some time!<BR/><BR/>Thanks for the tips on filing a report. I've been fooling around with my configuration today and it looks like one of the various add-ins I've got may be the source of the problem. I wanted to get that info ironed out before proceeding further.<BR/><BR/>Your comment's such good advice that I'll point to it from a separate blog post. Thanks!Jim Holmeshttps://www.blogger.com/profile/05869146736565695900noreply@blogger.comtag:blogger.com,1999:blog-10748614.post-1132171142174902272005-11-16T14:59:00.000-05:002005-11-16T14:59:00.000-05:00Hi Jim,I'm a tester on the VS Core team. Having V...Hi Jim,<BR/><BR/>I'm a tester on the VS Core team. Having VS crash on you upon every shutdown is totally not acceptable. Please file a bug report at Product Feedback Center located at<BR/>http://lab.msdn.microsoft.com/productfeedback<BR/><BR/>Also, when you file the bug report, please send us the Crash ID from the Watson dialog (the dialog where you can send the crash feedback to Microsoft - please hit Send Feedback to send us the stack trace). You can find this Crash Id from the following steps:<BR/>1. From Start - Run dialog, run "eventvwr.msc"<BR/>2. Open the "Application Log" node.<BR/>3. Look for the newest event with Source="Microsoft Development Environment" and Event="1--1"<BR/>4. Open that event and you'll see "Bucket" followed by the crash ID number we're looking for<BR/><BR/>Also, please open a second bug report for the aspx file along with the Crash ID.<BR/><BR/>As for a workaround, unfortunately, i'm thinking that some Beta 2 components didn't get completely uninstalled. The Visual Studio Setup Forums has a good summary of all tips and tricks located at<BR/>http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=134489&SiteID=1<BR/><BR/>Let me know if there's anything I can do to help.<BR/><BR/>thanks!<BR/>-saraAnonymousnoreply@blogger.com