none
What is The future of VB.NET 2014+

    General discussion

  • I see that Microsoft choose java script and HTML5 for windows 8 and they focusing on C# More than VB.NET , and from reading around the net Microsoft trying to cancel VB.NET and make programmers choose C# as the main language for .NET
    Sunday, September 08, 2013 12:35 AM

All replies

  • Microsoft has one team working on C#.Net and another team working on VB.Net. The VB.Net team has always lagged the C#.Net team because C# was derived from C++ an objected oriented language and VB6 was not object oriented.  This was really an issue with VS2002 and VS2003. With each release of VS since the VB.Net team has been getting closer.  Today, there are only slight differences in the two languages. Both languages compile to the same IL code. .Net introduced the managed heap and garbage collector, something C++ and VB6 did not use. JAVA uses a similar scheme (managed heap and garbage collector). VB.Net will never be removed from VS.  Now a better alternative for VS will someday arrive.  I have been programming for 47 years in many different languages and each new language was an improvement over the previous language. 

    The difference between genius and stupidity is that genius has its limits.

    Sunday, September 08, 2013 2:15 AM
  • Hi mishar82,

    Maybe this issue can be sent to http://visualstudio.uservoice.com/forums/121579-visual-studio (submit an idea).


    If you think one reply solves your problem, please mark it as An Answer, if you think someone's reply helps you, please mark it as a Proposed Answer

    Help by clicking:
    Click here to donate your rice to the poor
    Click to Donate
    Click to feed Dogs & Cats


    Found any spamming-senders? Please report at: Spam Report

    Sunday, September 08, 2013 2:20 AM
  • MS is not going to retire VB.NET. You do know there are other application types other than things that run at the lipstick UI.  Right? There are other Windows O/S(s) that are not Windows 8 like Win XP, Vista and Win 7 that are heavy in use. Win 2k, Win 2k3 servers etc, etc that are still heavily being used that are running VB.NET applications.

    Application types such as Windows Service, Console Application, legacy Web service, WCF services, classlib (DLL) all done with VB.NET that have nothing to do with the UI,  and companies are using all of the technologies and are running those solutions on machines. And they will continue to run VB.NET on machines.

    Why would MS invest anything in JavaScript? It was the fallout with MS and Sun Micro Systems over Java that lead to the development platform of .NET.

    Also, businesses are going to be at the Windows 8 desktop doing the same things like they can do now at the Win 7 or Vista desktop to conduct day-2-day or business-2-business activities on a desktop powered by VB and or C#.NET applications. The State of NY's most high profile applications, as an example, are running on VB.NET, which is a heavy MS client. And there are many others around the US and the world that are using VB.NET that are heavy MS clients.

    You show any official MS documentation where it states the MS is going to terminate or retire VB.NET. All you see if you do look is a lot of blabber mouth lip-service about VB.NET being retired. It's not going to happen.

    Sunday, September 08, 2013 2:40 AM
  • VB and C# are developed by one team which is under control of Anders Hejlsberg. In that team are persons biased to VB and to C# like Anders Hejlsberg, but non of them would say any of the two is better. 



    Success
    Cor

    Sunday, September 08, 2013 7:28 AM
  • javascript is not Java.  And it very quickly become the lingua Franca of client side webprogramming. 
    Monday, March 10, 2014 6:16 PM
  • There was just a successful change.org petition to bring back VB6.  To make a 64-bit version.  Seems in 2014 there is still a large demographic that prefer VB6 over .Net or Java.  The change.org signers are from as most a diverse country set as can be imagined.

    I wonder if the new management at MS will act on this or ignore as they have done in the past.

    Sunday, March 16, 2014 3:00 PM
  • There was just a successful change.org petition to bring back VB6.  To make a 64-bit version.  Seems in 2014 there is still a large demographic that prefer VB6 over .Net or Java.  The change.org signers are from as most a diverse country set as can be imagined.

    I wonder if the new management at MS will act on this or ignore as they have done in the past.

    Successful?, then there would be a million voters, I see 6 reactions, a kindergarten petition gets more.. 

    Be aware that the old management of Microsoft did not ignore all the petitions. VB8 (2005) got a lot from old vintage VB6 behaviour (The My Namespace with its bad memory mapping) which is disliked by the users of the real Visual Basic of that time (VB7).


    Success
    Cor


    Sunday, March 16, 2014 3:12 PM
  • I see that Microsoft choose java script and HTML5 for windows 8 and they focusing on C# More than VB.NET , and from reading around the net Microsoft trying to cancel VB.NET and make programmers choose C# as the main language for .NET

    Java Script and HTML5 are client side technologies used for rendering content in a platform independent manner and/or for taking advantage of the latest browser capabilities.

    But guess what kind of project(s) you create to serve that client side data?  That's right, it is your VB or C# project that is generating the clientside JS or HTML5 code.

    Of course at this point in time the majority of what you see written on the web focuses on Windows Store Apps for the various Windows 8 platforms.  There is very little talk about "classic" desktop and web applications right now.  But the reason for this is not that Microsoft is transitioning away from .Net in favor of JS or HTML5... the reason is that Microsoft already owns the PC Desktop market-space and has for a long time.  The problem is that they have only a small fraction of the modern "App market-space", which is currently dominated by Apple, with Google being the ones hot on their heals.  It should come as no surprise that the loudest talk will center around "Apps" until either MS gains a dominate market-share, or the fad wears off (whichever comes first).

    You cannot speak of the future of C# and that of VB as two separate cases; there is only the future of .Net which equally includes both languages. If you want to keep up with the development of .Net languages, then this is the blog to follow: http://blogs.msdn.com/b/dotnet/

    Here's a post from last summer that should put your mind at ease and allow you to trust what Cor has already told you:

    http://blogs.msdn.com/b/vbteam/archive/2013/07/17/no-new-vb-and-c-language-features-in-vs-2013.aspx


    Reed Kimble - "When you do things right, people won't be sure you've done anything at all"

    Sunday, March 16, 2014 5:15 PM