Visual Studio and .NET Framework Home
Auto list members causes VS 2008 B2 to crash with generic extension method
10/14/2007 7:25:55 AM
User(s) can reproduce this bug
When attempting to write code to call a method of a specialized class from a class library in a console application where the specialized class derives from a base that explicitly implements ICloneable and that base class has a generic extension method in the same class library, auto list members causes visual studio to crash.
Visual Studio Code Name "Orcas" (Beta 2)
Windows XP Professional
Operating System Language
Steps to Reproduce
Create a .NET 3.5 class library.
Delete the autogenerated Class1
Add the following class implementations to the class library:
public class Base : ICloneable
#region ICloneable Members
object ICloneable.Clone ( )
throw new NotImplementedException();
public class Inherited : Base
public static class Extensions
public static T Clone<T> ( this T instance ) where T : Base
Add a new .NET 3.5 console application project to the solution.
In the Main method of the console application, add Inherited variable and initialize it:
ClassLibrary2.Inherited i = new ClassLibrary2.Inherited();
Now, when you attempt to call a method on i, Visual Studio crashes (i.e. type "i.").
If I delete the extension method, the crash does not occur.
If I turn Auto list members off, the crash does not occur.
See attached solution.
Following is the error reporting event log information:
Bucket 470715848, bucket table 1, faulting application devenv.exe, version 9.0.20706.1, stamp 468e0278, faulting module cslangsvc.dll, version 9.0.20706.1, stamp 468e06a1, debug? 0, fault address 0x00129a79.
Visual Studio crashes
Show list of members
TAP Code (if applicable)
You can indicate your satisfaction with how Microsoft handled this issue by completing this quick
3 question survey
to post a comment.
Please enter a comment.
on 10/15/2007 at 11:46 AM
Thanks for the feedback. I'm happy to say that this issue has been fixed in recent builds. We're currently working on a patch that will fix this issue for Beta2 as well so if you'd be interested in learning more, feel free to contact me directly at email@example.com.
VIsual C#, Program Manager
on 10/14/2007 at 9:19 PM
Thanks for your feedback.
We are escalating this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Visual Studio Product Team
on 10/14/2007 at 8:23 PM
Thank you for your feedback. We are currently investigating. The investigation process normally takes 7-14 days. If this issue is urgent, please contact support directly (see http://support.microsoft.com).
If at any time your issue is closed unsatisfactorily, you may edit your issue via Connect and change the status to “Active.”
Visual Studio Product Team
to post a workaround.
Please enter a workaround.
© 2014 Microsoft