Visual Studio 2013 Domain Specific Language Designer crash on exit. - by David Clement BC

Status : 

 


2
0
Sign in
to vote
ID 813425 Comments
Status Active Workarounds
Type Bug Repros 0
Opened 1/9/2014 2:58:08 PM
Access Restriction Public

Description

Using the Visual Studio 2013 Domain Specific Language Designer, I created a simple project and ran it without alteration.  Every time I exit the instance of Visual Studio running the DSL I get a crash as follows:

System.Runtime.InteropServices.InvalidComObjectException was unhandled
Message: An unhandled exception of type 'System.Runtime.InteropServices.InvalidComObjectException' occurred in mscorlib.dll
Additional information: COM object that has been separated from its underlying RCW cannot be used.

I have not customized or altered the base configuration of Visual Studio 2013 in any way nor altered the default simple DSL that is used to create the DSL.
Sign in to post a comment.
Posted by Michael-DragonSpark on 11/3/2014 at 1:15 PM
Is it fixed yet?
Posted by Carlos J. Quintero on 1/22/2014 at 11:05 PM
Hi,

This problem is reproducible using VS 2013 at least on Windows 8.1. Install the VS 2013 SDK an create either a DSL, a package or an add-in. Debug the project. A new VS 2013 instance is launched. Close this instance. You get:

System.Runtime.InteropServices.InvalidComObjectException was unhandled
Message: An unhandled exception of type 'System.Runtime.InteropServices.InvalidComObjectException' occurred in mscorlib.dll

This bug has been acknowledged by Ryan Molden (from the VS team) in this thread of the MSDN VSX forum: http://social.msdn.microsoft.com/Forums/vstudio/en-US/06c0c8f3-e616-4c8c-9a62-aa87a6a63edb/default-vspackage-template-in-vs2013-sdk-throws-exception-when-exiting?forum=vsx
Posted by Microsoft on 1/15/2014 at 7:28 PM
Thank you for submitting feedback on Visual Studio and the .NET Framework. At this point, it has been more than 4 days since we initially requested additional information to reproduce your issue. Since we have not heard back from you we will close the issue. If you need further assistance on this or any other pre-release product issues in the future, please feel free to contact us and we will be happy to help.
Posted by Microsoft on 1/14/2014 at 3:35 AM
Hello again. We wanted to give you a quick reminder that to efficiently investigate and reproduce your issue, we need you submit the additional information we requested.
Posted by Microsoft on 1/13/2014 at 3:30 AM
Hello again. We wanted to give you a quick reminder that to efficiently investigate and reproduce your issue, we need you submit the additional information we requested.
Posted by Microsoft on 1/9/2014 at 8:28 PM
Thanks for your feedback. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a dump file and call stack so that we can conduct further research?

Visual Studio now has an extension called Microsoft Visual Studio 2013 Feedback Tool, available on the VS gallery(<http://visualstudiogallery.msdn.microsoft.com/563d1003-f0ed-498f-8ef9-f8ee1aac39fe>).

The extension allows you to
1. upload files,
2. collect trace and dump files
3. collect steps while you're repro'ing the issue
4. SQM logs about VS extensions installed
5. System details (in DxDiag output)

We look forward to hearing from you with this information.
Posted by Microsoft on 1/9/2014 at 3:52 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)