Why is the code snippet shown in VB more than in C #?

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

For VB:

Inside the Snippet element, add the Link Element and all the required child elements that add the link to the project when the snippet.

For C #

Visual C # code scripts, so as not to do, maintain the "Links" section, so the link to System.Windows.Forms.dll must be manually added to the project

What is the main reason preventing C # from supporting links like VB?

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

But this is not even as complete as links to code snippets, because links to code snippets allow you to add multiple links at once, not one after another.

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

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

+8
c # visual-studio msdn
source share
3 answers

Karen Liu from the C # IDE team answered this in a report:

Thank you for submitting this offer. This is what we know about and tried to do as a design change Request earlier. Ultimately, based on the cost to implement this, when we were in the production cycle we made a tough decision, since links would be something that you would need to add only once, it did not do this in VS2005. This is what we are hoping to do in the future, although hearing feedback about it is valuable.

Only nine upvotes are not enough to make it popular. I would recommend you vote for it, they pay attention to it.

+13
source share

The main reason is that VB thought the script was more valuable to its customers than C #, and therefore invested in this feature. Nothing prevents C # from adding this feature. It just didn’t fit the shorthand list when evaluating it compared to other IDE fetuses.

+11
source share

Political reasons, IMHO C # is more "hardcore" and vb is "letting it do this fast and compress codemonkey".

So, the VB programmer will usually stick to the standard (visual installation installation) Visual Studio installation, while the aC # programmer will install one (or more) plugins (Resharper, Coderush, etc.), not counting additional components (Telerik, Devexpress ..), instead, a # will not work if the visual studio does not have at least one additional code support plugin.

+1
source share

Source: https://habr.com/ru/post/650253/


All Articles