A group blog from members of the VB team
Yesterday we published a copy of a fun “Roslyn”-powered retro editor for Visual Basic called QuickVB in honor of the 50th birthday of BASIC. We thought this was a neat application to showcase our love of BASIC but since then we’ve realized that it’s also a great example of how to put the power of the .NET Compiler Platform (“Roslyn”) APIs to use.
In the spirit of openness we’ve decided to open source QuickVB as a sample project on CodePlex so that others may tinker with it and learn from it.
Alex Turner, Ian Halliday, Anthony D. Green on behalf of the Managed Languages (VB, C#, F#) team
I'm getting flashbacks! QuickBASIC 4.5 was my favorite DOS programming environment and I remember the wars between QuickBASIC and TurboBasic that used to rage in the ads of programming magazines.
You'll do this, but you won't even answer a call to either update VB6 or make it open source.
Is it that difficult to find someone in Microsoft who has the authority to say 'Yes' or 'No' ?
There are millions of lines of VB6 source code still in use, in business and in government. Microsoft just aren't addressing this.
Satya Nadella said at Build 2014 "It's crazy to abandon what you built and crazy to not let what you build work on other platforms"
And yet Microsoft's advice is still 'migrate your VB6 code to VB.Net'. DON'T YOU LISTEN TO WHAT SATYA SAYS ?
VB6 is now the 6th most popular programming language according to the April 2014 Tiobe index - well ahead of VB.Net.
And the call for an updated VB6 on the Visual Studio UserVoice site is the fifth most popular (out of over 8,000).
GIVE US AN ANSWER !
Sten2005 is right about Visual Basic 6.0 !
I'm with Sten2005 and other 800+ comments at uservoice.
We want to hear you...
PS. Thank you very much for QuickVB
VB6 is now Microsoft's top language
Visual Basic 6 has just risen to fifth most popular programming language in the May 2014 Tiobe index.
While C# has dropped to sixth. VB.Net is 11th.
Now is the time for a new release of VB6:
VB6 - Microsoft's favorite programming language
I'm with Sten2005 too.
I think it would be awesome if Microsoft would release Visual Basic 6 to the Open Source community (Codeplex). It is a long time, for example, that I would like to develop a plug-in for Visual Studio that can fully reproduce the VB6 IDE (code/form editor, compiler, debugger) .... but it's very hard (perhaps impossible) to achieve this result with just a reverse-engeneering approach (... by the way, I'm trying anyway).
Im with Sten2005,
Why can't you release a new update to vb6. You updated VBA in office.
You are leaving millions of lines of code written over 15 years un-useable. Our codebase evolved through many years and now we are just supposed to throw it away?
Funny to see the comments about the love of VB6 ,, I was actually in the Visual Fred camp when VB.Net came out as I was at that time a VB6 addict ( I still like it but I do not use it anymore ) ,, I Rode the wave of change and thus moved my business to VB.Net and boy am I addicted to VB.Net I really love that language since the early beta`s and thus have experience with it since 2001 ( MSDN Previews ) ..
What really made my blood boil was the recent release of VS 2013 Update 2 dear "Alex Turner, Ian Halliday, Anthony D. Green on behalf of the Managed Languages (VB, C#, F#) team" could you please explain to us VB ( Basic Language Developers ) why you broke your promise of Co evolution between C# and VB.Net ?
Why do we not have a Universal Apps template in Visual studio why do you leave us VB Developers behind ? why do you feed the stigma that VB.Net is a 2nd class .Net citizen instead of the First class that it is ( by words of Steve B. ) .
So you would have better spend your precious time creating and releasing these Universal App templates !
By the way ... to the VB6 posters below the power advantage of VB6 is that it is closed source , at my previous employer we sticked with release apps ( desktop apps that were shipped on CD ) with VB6 because if native compiled it was not possible to decompile it , while anny interpreted language like .Net and Java is unsafe in certain business scenario`s as anyone with minimal knowledge can decompile the assembly to the source and thus see Database passwords etc etc and thus can steal valuable business data .
We’re currently in the process of building Universal app support for both languages for the next release of Visual Studio based on the .NET Compiler Platform (“Roslyn”).
-The Visual Basic and C# Languages Team
No reply to any of the comments about the VB6 programming language.
Even though VB6 is now Microsoft's most popular programming language in the May 2014 Tiobe index.
7,000 votes in the UserVoice forum and still no reply from Microsoft.
@Anthony D. Green [MSFT]
It is noticeable that you reply to a point about C# and VB.Net, but (along with almost everyone else in Microsoft) you ignore any comments about VB6.
The call for an updated VB6 programming language on the Microsoft Visual Studio UserVoice site is now the fifth highest (with over 7,200 votes) but no reply there either.
Is it Microsoft policy to ignore all comments about VB6 ?
Is it also Microsoft policy to ignore what Satya Nadella said at Build 2014 "It's crazy to abandon what you built and crazy to not let what you build work on other platforms" ?
Also in honor of Basic's 50th birthday Paul Yuknewicz, Microsoft Group Program Manager has declined the request to bring back an updated VB6 programming language.
His weak justification seems to be an attempt to "also stand behind our decision starting in 2002 to meet the current demands of our developers and the industry with .NET. ".
Paul Yuknewicz has the unenviable distinction of now twice cancelling VB6. Yet it still won't go away.
I read all of you demanding to revive VB6... how comes that you do not understand that Vb6 can't be 'updated' to VB.NET??? there are too many breaking changes for this to be reasonable usefull procedure...
VB.NET is just a C# that looks like VB... so, VB.NET lives with C# and .NET for those that would like to have a BAIC language for them... and VB6 can not be .NET-ted... period... and microsoft development in last 10+ years was almost exclusively in the .NET area... so, what could be done for VB6? nothing, I am afraid :( you can't be .NET *AND* VB6... VB.NET is VB and .NET...
@VB6 can't be updated
No one is asking for VB6 to be updated to .Net. That is exactly what we DON'T want.
What we do want are the same (small) changes that have been added to VBA to be also added to the VB6 programming language.
If Microsoft can add the changes to VBA (in Office 2013) they can be added to VB6 too.
Satya Nadella still hasn't replied to the open letter requesting an updated or open sourced VB6 programming language.
Satya Nadella said at Build 2014 "It's crazy to abandon what you built and crazy to not let what you build work on other platforms" but seems happy to abandon VB6.