StackOverflowException in Visual Studio 2012 internal code - by Simon Mourier (SoftFluent)

Status : 


Sign in
to vote
ID 790303 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 6/17/2013 3:23:42 AM
Access Restriction Public



I'm writing a package that can open an .SQL file programmatically from the IDE for the user. The .SQL file correspond to a hierarchy node that resides in my package's hierarchy. For that, I use the standard IVsUIShellOpenDocument.OpenStandardEditor method with Guid.Empty as the logical view.

It used to work fine with Visual Studio 2008 and 2010. But now with Visual Studio 2012 (Version is 11.0.60315.01 Update 2), either it doesn't work, the screen may be blank, or completely black, or it Visual Studio just crashes, also when I use the new "preview" feature of Visual Studio 2012.

When it crashes, it's because of a .NET StackOverflowException in Visual Studio 2012 internal code.

It seems like a bug to me. Right now, I use OpenSpecificEditor with VSConstants.GUID_TextEditorFactory as the editor and VSConstants.LOGVIEWID_Code as the logical view for a workaround, but I'd like to use the standard SQL Server editor.

Note when I use the LOGVIEWID_UserChooseView logical view, it also fails if I select the default "Microsoft SQL Server Data Tools, Editor Selector".

Sign in to post a comment.
Posted by Deon [MSFT] on 4/29/2014 at 12:30 PM
Thank you for reporting this issue. This issue has been fixed in Visual Studio 2013. You can install a trial version of Visual Studio 2013 with the fix from:
Posted by Simon Mourier (SoftFluent) on 8/10/2013 at 11:25 PM
Great. Thanks a lot!
Posted by Patrick [MSFT] on 8/10/2013 at 3:55 PM
Found it. This will be fixed in the next version of VS and next versions of SSDT.
Posted by Patrick [MSFT] on 8/10/2013 at 2:44 PM
By the way, I tried the free license and it didn't work.
Posted by Patrick [MSFT] on 8/10/2013 at 2:34 PM
Hello Simon - I'm trying to repro this in VS 2011 but I don't have a license. Do you have one I could use for the repro purposes? My email is patrick dot sirr thanks!

Posted by Microsoft on 6/17/2013 at 11:09 PM
Thanks for your feedback.

We are rerouting 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.
Posted by Microsoft on 6/17/2013 at 3:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(