Crashing VS.NET

I’ve replicated this crash quite easily. If I install the current (1.0.737) VS.NET IDE plugin and try to examine the Properties for the loaded Project then VS.NET will crash.

Plugin

KodersAddinVS2005-1.0.737.msi

System

Microsoft XP Pro SP2 running in VM under MS Virtual Server 2005 RC2.

IDE

Microsoft Visual Studio 2005 Team Edition for Software Developers SP1

Full IDE Info

Microsoft Visual Studio 2005 Version 8.0.50727.762 (SP.050727-7600) Microsoft .NET Framework Version 2.0.50727

Installed Edition: Enterprise

Microsoft Visual C# 2005 77642-113-3000004-41109 Microsoft Visual C# 2005

Microsoft Visual Studio Tools for Office 77642-113-3000004-41109 Microsoft Visual Studio Tools for the Microsoft Office System

Microsoft Visual Web Developer 2005 77642-113-3000004-41109 Microsoft Visual Web Developer 2005

Microsoft Web Application Projects 2005 77642-113-3000004-41109 Microsoft Web Application Projects 2005 Version 8.0.50727.762

Visual Studio 2005 Team Edition for Developers 77642-113-3000004-41109 Microsoft Visual Studio 2005 Team Edition for Software Developers

Visual Studio 2005 Team Explorer 77642-113-3000004-41109 Microsoft Visual Studio 2005 Team Explorer Version 8.0.50727.147

Microsoft Visual Studio 2005 Team Edition for Software Developers – ENU Service Pack 1 (KB926601) This service pack is for Microsoft Visual Studio 2005 Team Edition for Software Developers – ENU. If you later install a more recent service pack, this service pack will be uninstalled automatically. For more information, visit http://support.microsoft.com/kb/926601

ReSharper 3.0 C# Edition build 3.0.468.6 on 2007-06-21T10:34:16 ReSharper add-in for Microsoft Visual Studio. For more information about ReSharper, see the ReSharper website at http://www.jetbrains.com/resharper. Copyright © 2003â??2007 JetBrains, Inc

SQL Server Analysis Services Microsoft SQL Server Analysis Services Designer Version 9.00.3042.00

SQL Server Integration Services Microsoft SQL Server Integration Services Designer Version 9.00.3042.00

SQL Server Reporting Services Microsoft SQL Server Reporting Services Designers Version 9.00.3042.00

GhostDoc for Visual Studio 2005 For more information about GhostDoc, see the GhostDoc website at http://www.roland-weigelt.de/ghostdoc Copyright © 2003-2007 Roland Weigelt.

KodeShareAddin for Visual Studio 2005 KodeShareAddin for Visual Studio 2005

TestDriven.NET 2.7.2111 Beta Personal For more information, see the TestDriven.NET website at http://www.testdriven.net/. Development by Jamie Cansdale <jamie@mutantdesign.co.uk>. Copyright© 2002-2006 Mutant Design.

Hi Richard,

I was able to reproduce your bug report where VS2005 crashes while attempting to view the property page of a project with the Koders Panel View visible:-(. I have an engineer looking into it, but in the meantime, it is still usable as long as you don’t keep the Koders Search Panel view up while attempting to see the property page of a project. I realize that this is not desirable and I will post here as soon as I can update the plugin.

Thanks for your post,

Dianna DeCristo

IDE Plugin Manager

Hi Richard,

We’ve got a new version of the VS 2005 Plugin ready that should solve this issue. You can download it here: http://www.koders.com/info.aspx?c=tools#IDEs

Please let us know how it goes and thanks again for letting us know.

Mike

If I install the current (1.0.762) VS.NET IDE plugin and try to open a .sql file VS.NET crashes.

I don’t see the error as being the plugin’s problems with the file I’m opening but with the fact a crash in the plugin can take down VS.NET. I’ve not written a plugin for VS.NET but should an exception in the plugin not be handled by the plugin?

Hi Richard,

Just to be clear, you installed the VS.NET 1.0.762 version of the plugin and then any attempt to open a .sql file caused VS.NET to crash? I assume uninstalling the plugin, then fixed your problem?
In my opinion, our plugin should handle exceptions appropriately and VS.NET should never crash. I have filed a bug to review our plugins exception handling.

Hey Richard,

I have tried all sorts of combinations of opening and creating SQL scripts (ending in .sql) and cannot reproduce this situation. Any additional information about this crash would be very useful.