Why code snippet in VB is more featured than in C#?

Question

As I read http://msdn.microsoft.com/en-us/library/ms165394.aspx:

For VB:

Inside the Snippet element, add the References element and all of the required child elements that add a reference to the project when the snippet is inserted.

For C#

Visual C# code snippets to do not support the References section, so a reference to System.Windows.Forms.dll must be added to the project manually

What fundamental reason prevents C# to support References like VB ?

Update: I saw this posted http://visualstudiogallery.msdn.microsoft.com/en-us/dc06b54c-b6c4-4cf5-8203-a09c6979e881

But it isn't even as full-featured as Code Snippet References as Code Snippet References will allow you to add multiple references at once not just one by one.

C# is supposedly more "professional" than VB.NET, one would expect C# to be more featured not more limited or does "professional" means you have to do it the hard way as said "MANUALLY" :p

When will the C# team catch up with VB.NET team ?

Answer 1

Karen Liu of the C# IDE team responded to this in a feedback report:

Thanks for submitting this suggestion. This is something we are aware of and had tried to do as a Design Change Request before. Ultimately, based on cost to implement this where we were in the product cycle, we made the tough decision that since references would be something you would need to add only once, this did not make it into VS2005. This is something we are looking to do in the future though and hearing feedback on this is valuable.

Only nine upvotes, not enough to make it a popular request. I'd recommend you vote it up, they do pay attention to that.

Answer 2

The fundamental reason is that VB thought the scenario had more value for their customers than C# did and hence invested in the feature. There is nothing preventing C# from adding the feature. It simply didn't meet the cut list when they evaluated it against other IDE fetaures.

Answer 3

politician reasons, IMHO C# is more "hardcore", while vb is more "let's do it quick and contract a codemonkey to do it.

So, a VB programmer usually will stick with a standard (vanilla install) visual studio installation, while a c# programmer will install one (or more) plugins (Resharper,Coderush,etc.) , not counting extra components (Telerik, Devexpress..), instead a c# will not work unless visual studio have at least one extra code assistance plugins.