Adding C# class to SSDT project breaks Solution Explorer file expand and Code Map features for all projects in solution - by PashaPash

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 774868 Comments
Status Closed Workarounds
Type Bug Repros 3
Opened 12/20/2012 6:51:23 AM
Access Restriction Public


When class (or any C# file) added to SSDT project, solution explorer stops expanding files to class level. SL still shows expand ">" symbols for all files, but shows nothing in that file when clicked.
All projects in solution, not only SSDT project, are affected. Code Maps are broken for all projects too.

I tried to attach a debugger to VS, and got en exception when broken expand icon is clicked:
ArgumentNullException: "Value cannot be null.\r\nParameter name: key"
>	mscorlib.dll!System.Collections.Generic.Dictionary<System.Uri,Microsoft.RestrictedUsage.CSharp.Compiler.IDE.IDECompiler>.Insert(System.Uri key, Microsoft.RestrictedUsage.CSharp.Compiler.IDE.IDECompiler value, bool add) + 0x2c2 bytes	
 	Microsoft.VisualStudio.Progression.LanguageService.CSharp.dll!Microsoft.VisualStudio.Progression.LanguageService.CSharp.CSLanSvcProvider.GetIDECompilers.AnonymousMethod__6(object objContext) + 0x25a bytes	
 	Microsoft.VisualStudio.Progression.Common.dll!Microsoft.VisualStudio.Progression.UIThread.RunTask(Microsoft.VisualStudio.Progression.UIThread.TaskData taskData) + 0x46 bytes	
 	Microsoft.VisualStudio.Progression.Common.dll!Microsoft.VisualStudio.Progression.UIThread.PumpTasks() + 0xac bytes	
 	Microsoft.VisualStudio.Progression.Common.dll!Microsoft.VisualStudio.Progression.UIThread.OnTick(object sender, System.EventArgs e) + 0x15 bytes	
 	WindowsBase.dll!System.Windows.Threading.DispatcherTimer.FireTick(object unused) + 0x2f bytes	

unloading SSDT project helps, but next time it's loaded Solution Explorer breaks again.
Sign in to post a comment.
Posted by James [MSFT] on 2/14/2013 at 2:16 PM
Thanks for the feedback. We have fixed this issue for the next release of the Visual Studio 2012 Update.
Posted by poochyellowbus182 on 2/10/2013 at 9:48 PM
It is late thank you good night.
Posted by Macy [MSFT] on 12/20/2012 at 11:16 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 Macy [MSFT] on 12/20/2012 at 7: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(
Posted by PashaPash on 12/20/2012 at 6:54 AM
I attached a sample project to reproduce the issue.