A group blog from members of the VB team
As announced today by Soma, we've just released the first CTP (Community Technology Preview) of the next version of Visual Studio. This is doubly-exciting as this is the first public release of a version of Visual Studio powered by "Roslyn" by default. At BUILD we released the "Roslyn" End User Preview which extends Visual Studio 2013 by replacing some components with their "Roslyn" equivalents but this version of Visual Studio is built from the ground up on "Roslyn" with "Roslyn".
The Visual Studio "14" CTP includes new and improved language and IDE features for Visual Basic such as multiline strings and a full-fledged refactoring experience:
(Invoke the Go to Definition command on a symbol not defined in your source project)
These are just some of the small but powerful enhancements we're building for VB developers and we're far from done. But that's no reason for you to wait. Since we've literally rebuilt the very foundations of VB it couldn't be more critical for us to get your feedback early and often on what you like, don't like, love, and what you want to see more of.
Stay tuned for more posts from the Managed Languages team highlighting new and improved language features and experiences. In the meantime…
And one more thing: Visual Studio side-by-side support is not available on this early build. DO NOT install this CTP (or feed it after midnight) on a machine with any other version of Visual Studio installed.
Anthony D. Green, Program Manager, Visual Basic and C# Languages Team
These multilined Strings is a godsend. I'm looking forwared to do some Universal Apps.
Satya Nadella still hasn't replied to the open letter about updating or open sourcing VB6.
Here is an abbreviated version of the letter....
Dear Mr. Nadella,
I have emailed you, sent you a Facebook message and posted on Facebook. As you have not replied I assume you haven't seen any of these.
I have asked you for an explanation of Mr. Paul Yuknewicz's refusal to update the VB6 programming language with the same modifications Microsoft have already done to VB6's sister language VBA.
Mr. Yuknewicz raises several straw man arguments ("Current needs ranging from distributed applications and services, to web applications and services, to devices, to new architectures and languages, required fundamental changes to the whole stack") in an attempt to explain why this is "not possible". The reality is that it is very possible, if Mr. Yuknewicz does not understand we can explain the details to him. Again, these changes are very possible - you have already done them in VBA 7.
Whilst most VB6 developers would prefer that Microsoft did these modifications and that VB6 remained a Microsoft product, if you are not willing to do this then Microsoft has a duty to safeguard the investment of VB6 developers by open sourcing VB6.
Microsoft could, of course, supply the C++ source code of VB6 to the community and let us do the modifications, but Mr. Yuknewicz again refuses, stating that is "not feasible" to open source VB6. Presumably the reason it is "not feasible" is a business decision rather than a technical one. If your concern is that the language is still current in VBA presumably you could license the VBA element to the community - certainly whatever objections you may have cannot be insurmountable.
Even Mr. Yuknewicz admits Microsoft will have to continue supporting VB6 until 'at least' 2024. In reality I'm sure we all know it is likely to be much longer.
So, Mr. Nadella, could you please explain why is it not possible for Microsoft to add the same modifications to VB6 you have already added to VBA7.1 ?
And why is it not feasible for you to open source VB6 ?
The vote for an updated VB6 on the Microsoft UserVoice site had reached the fifth highest position (out of over 8,500) and looked to be well on the way to the top position. Rather than seeing this as an indication of the popularity of VB6, it looks as though Mr. Yuknewicz has declined our call merely because of the perceived embarrassment to Microsoft of a language he cancelled back in 2002 reaching the top of a 'popularity' poll.
And why was Mr. Yuknewicz the person to make the decision ? He apparently is the Group Program Manager, Microsoft Visual Studio Cloud Tools. What relevance does that have to VB6 ? Other than being instrumental in the original decision in 2002 to abandon VB6, what involvement with VB6 does he have now ?
Mr. Nadella, please have the courtesy to reply.
Seriously, is there anyone else out there still doing development with a language that has not been updated in 14 years.