5 Replies - 2786 Views - Last Post: 09 February 2017 - 10:14 AM

#1 maceysoftware  Icon User is offline

  • D.I.C Lover
  • member icon

Reputation: 348
  • View blog
  • Posts: 1,493
  • Joined: 07-September 13

The .NET Language Strategy

Posted 09 February 2017 - 02:01 AM

Not sure if anyone else has read this or not.

However I will just post the links here encase people want to read.

https://blogs.msdn.m...guage-strategy/
https://blogs.msdn.m...guage-strategy/

If I am reading this right it seems they will now not be adding all the feature they add to C# into VB.Net.

Even though I do most of my programming in work in VB.Net, I am glad I have already moved across to C# on personal projects at home. I doubt there is anything to worry about for a few years until they actually get out of sync, it will be when features I actually want to use comes out, but are only applicable to C#.

Is This A Good Question/Topic? 1
  • +

Replies To: The .NET Language Strategy

#2 modi123_1  Icon User is online

  • Suitor #2
  • member icon



Reputation: 13484
  • View blog
  • Posts: 53,825
  • Joined: 12-June 08

Re: The .NET Language Strategy

Posted 09 February 2017 - 08:05 AM

Yup.. caught that a day or so ago. Meh - I flip between the two and am somewhat shocked when I find people who work in one, but can't work in the other. :D
Was This Post Helpful? 1
  • +
  • -

#3 maceysoftware  Icon User is offline

  • D.I.C Lover
  • member icon

Reputation: 348
  • View blog
  • Posts: 1,493
  • Joined: 07-September 13

Re: The .NET Language Strategy

Posted 09 February 2017 - 08:21 AM

I often make the same remark to people I work with.

Quote

What so your telling me you know VB.Net but you honestly can't read C#?


One reply I got was, no there are too many semi colons and curly brackets...
Was This Post Helpful? 0
  • +
  • -

#4 andrewsw  Icon User is offline

  • the case is sol-ved
  • member icon

Reputation: 6375
  • View blog
  • Posts: 25,756
  • Joined: 12-December 12

Re: The .NET Language Strategy

Posted 09 February 2017 - 08:26 AM

Knowing how to at least read C# is imperative for a VB.NET programmer, especially with more modern frameworks like ASP.NET MVC. There is very little information out there for ASP.NET MVC + VB.NET. This trend will only continue.
Was This Post Helpful? 0
  • +
  • -

#5 maceysoftware  Icon User is offline

  • D.I.C Lover
  • member icon

Reputation: 348
  • View blog
  • Posts: 1,493
  • Joined: 07-September 13

Re: The .NET Language Strategy

Posted 09 February 2017 - 09:29 AM

I am in agreement, I have opted not to go down the website route, in terms of personal development, however I can and have debugged myself around websites and you are correct a lot of information in terms of MVC is in C#.
Was This Post Helpful? 0
  • +
  • -

#6 andrewsw  Icon User is offline

  • the case is sol-ved
  • member icon

Reputation: 6375
  • View blog
  • Posts: 25,756
  • Joined: 12-December 12

Re: The .NET Language Strategy

Posted 09 February 2017 - 10:14 AM

The same applies with WPF et al. WinForms is the area where info for VB.NET is on a par with C#.

Even with WinForms there are often occasions when a good article or tutorial is about C# and should be utilised. (We shouldn't have to qualify a reference as "uses C#".)
Was This Post Helpful? 0
  • +
  • -

Page 1 of 1