.NET Conf starts today. It’s a three-day, free, virtual and global .NET conference. All you need to do is point your web browser to channel9.msdn.com, starting at 8AM Pacific Time. We have a packed agenda with a great set of expert .NET developers.
What will you learn? Many things.
You will learn to build for web, mobile, desktop, games, services, libraries and more for a variety of platforms and devices all with .NET. We have sessions for everyone, no matter if you are just beginning or are a seasoned engineer. We’ll have presentations on .NET Core and ASP.NET Core, C#, F#, Roslyn, Visual Studio, Xamarin, and much more.
Tell me More
You can watch a teaser video that we did a few days ago, telling you what to expect from the conference.
What will you learn? Many things. BUT NOT VB.NET??????? Why are you killing VB.NET! We feel, we are left out. Pl ask bill gate to promote VB.net if u guys cannot revive the language.
We added VB and F# support in the .NET Core 2.0 release. Your VB code can now run in new places. We also released VB 15 earlier this year.
Our investment is not the same in each of the languages, based on the number of users using them. Here is a write-up on this topic: https://blogs.msdn.microsoft.com/dotnet/2017/02/01/the-net-language-strategy/.
MS is doing too little too late for VB.NET community. If you guys cannot add more features to VB.NET language then at least make it enable to build apps which are possible with C#. Nowadays what we see only “work-around” solution to build app using of VB.NET with xamarin or dot net core platform but no native integration like C#. All examples are only in C#. We have clearly understood Dot net language strategy but treating VB as secondary language over C# is not correct. No MS ebooks on VB.net + ASP.net core, Xamarin, Dotnet Code? This attitude toward Vb.net shows MS is not serious about VB.
@hitesh,
Here’s what I think you said and my responses, please let me know if I missed anything.
> Why no Visual Basic examples at .NET Conf?
To keep things simple, we usually present things in C#. Not simply because C# is the most popular .NET language but also because most VB and F# developers can also read C#. In the past when we’ve presented talks in Visual Basic or F# we’ve found that the reverse is not always true. Presenting content this way allows us to reach the broadest audience with minimal duplication. If there was some content you’re really interested in but are finding it difficult to learn or adopt because of a lack of VB-specific documentation, please let us know so we can work with subject matter experts at Microsoft and within the VB community to make that content a priority. Not all content we produce is of equal interest to every part of our huge developer base so we want to make sure that if we do focus on VB-specific content is the content that is most critical to VB customer success.
> Microsoft is not adding more features to the Visual Basic language.
This is not true. As Rich mentions the last major release of Visual Basic was VB15, released earlier this year. Visual Basic already has a *massive* surface area with many great features and we’re adding more. Since VB15 was released we’ve moved more of our design process in the open and you can participate in the design of VB16 at https://github.com/dotnet/vblang. There’s lot of discussion on directions to take the language and I encourage you (and all VB developers) to participate.
> There is no native integration of VB into Xamarin (yet)
The C# support in Xamarin pre-exists Xamarin joining the Visual Studio family and is written as such. The Visual Basic and Xamarin teams are aware of the interest of the VB community in support for using Visual Basic to create Xamarin projects and are working together to identify the most efficient way to support Visual Basic in Xamarin without sacrificing the great editing and tooling experience VB developers have grown to expect or needlessly duplicating (and likely wasting) a lot of engineering effort. When we have something to announce on that front, we will.
> There is no native integration of VB into .NET Core
This is incorrect. Visual Basic is fully integrated alongside C# and F# into the .NET CLI and you can create cross platform Visual Basic console apps and class libraries both with the CLI and Visual Studio as of Visual Studio 2017 15.3. This was announced here: https://blogs.msdn.microsoft.com/vbteam/2017/08/14/new-for-visual-basic-net-standard-class-libraries-and-the-dotnet-cli/ and you can read more documentation of VB support in .NET Core 2.0 here: https://docs.microsoft.com/en-us/dotnet/core/whats-new/index
.NET Core doesn’t include GUI technologies such as Windows Forms, WPF, or UWP, so console apps and class libraries were our goal for this first release.
> All code examples are only in C#/No eBooks in VB on new technologies.
See my first answer.
> The .NET language strategy is to make Visual Basic secondary to C#
The point is not to make Visual Basic secondary, but to support Visual Basic in a manner unique to the needs of the Visual Basic community. Which, is in a way, more first class than before. Now, to make Visual Basic the master of its own destiny we (Microsoft) can’t do it all alone. Vocal and impassioned community members such as yourself can help us is by reaching out as you’ve done today on our blogs, on Twitter, on GitHub, and UserVoice, and the Visual Studio Developer Community portal and letting us know what really matters to you and your business and helping us separate actual business needs from more speculative and visceral calls for feature parity.
As an example, when ASP.NET 5 (now ASP.NET Core) was first announced there was a lot of community outcry that immediate support for Visual Basic was unequivocally critical to the success of all Visual Basic developers and projects everywhere. However, upon engaging the community through surveys, and email, and phone interviews we found that this was not the case. First, the big wins ASP.NET are cross-platform deployment (which is important for the cloud) and cloud-scale performance (also for the cloud). When asked, most Visual Basic shops indicated that they managed their own Windows Servers in-house to host their ASP.NET projects and that they had no immediate interest in moving those projects either to the cloud or to a Linux server. Also, none of them indicated that application throughput was an issue. Further, almost every Visual Basic developer we spoke to who was using MVC was doing so in hybrid projects that combined new development targeting ASP.NET MVC with maintenance of in some cases hundreds of pages of ASP.NET Web Forms pages. ASP.NET Web Forms is not a part of ASP.NET Core nor is supporting it part of the ASP.NET Core roadmap and even ASP.NET MVC 6 has many breaks from ASP.NET MVC 5. Meaning that the vast majority of Visual Basic ASP.NET projects will *never* be able to take advantage of ASP.NET without massive rewrites. ASP.NET Core is not a replacement for ASP.NET 4 but a new offering along side it targeted at new scenarios and both will continue to evolve in the future. And this is a prime example of how “first class” treatment of Visual Basic doesn’t mean doing things in or for VB reflexively and without regard to the value of those things to the VB community. We treated it as a first-class language first by treating it as an individual language and talking to VB customers and listening to their priorities. This is why by contrast, .NET Standard support, which allows customers to reuse their investments in business logic written in Visual Basic, was our priority.
I’m happy to discuss all of these things more with you and get your thoughts and hear about your particular needs in the coming months. If you’d like to discuss please grab some time on my calendar at: https://calendly.com/adgreen/vbfeedback to chat over Skype.
Regards,
Anthony D. Green
Program Manager
Visual Basic
Twitter: @ThatVBGuy
I don’t VB any more , but what a strong response, good on ya
Why Xamarin.Forms is still not intent to support VB ? Write a custom build tool to generate *.xaml.g.vb files is too hard for the Xamarin team?
@Nukepayload2,
It’s a little more involved than that. The Xamarin and VB teams are aware of the feedback that VB + Xamarin = WIN and are investigating! When there’s an update on that front we’ll announce it likely here and/or on the VB team blog.
Regards,
-ADG
Why should we learn anything of this? Only thing who is of interesting now is mobile, and Microsoft not supporting their own system, so why use anything of Microsoft now? Before killing Windows Mobile, it was very interesting to learn about UWP, but now when Phone support is gone, then UWP seams to be gone altså. As I saw in the Edge Summit, the Microsoft Teams will come with an UWP app in the future, but if UWP is so importen for Microsoft, why did they not build one who was released in the first wave. I’m so fried to spend time learning UWP, because Microsoft have shown that they are not fried to give middle fingers to they who supporting them, as they do with their Mobile system. I also been very confuse, when I se Microsoft do demo, using Chrome and Google instead of using their Edge and Bing. Does that mean that they don’t have trust in those, and maybe going to lay down those also? Just now Microsoft does me as an Developer for the Microsoft system very anxious, because it seams that they do not have any faith in their own systems, and that to sad.
On the .NET Team, we are just finishing up a huge investment in UWP. .NET for UWP will soon support .NET Standard 2.0. That’s a growth of ~ 20k APIs. From my team’s perspective, this is the most important improvement that we can deliver. I cannot comment on what other teams are doing.
UWP is dead when win mobile gone . Let’s take a look at reality of UWP:
Desktop: win32, and now people use node, there not too many users anymore .
Mobile: dead already.
IoT: who use UWP ?
Xbox : not too mush user of UWP.
Hololens: not design for too many user to use
Hi Rich,
Got here via a link in VS2017 Developer News page. The title says “.NET Conf 2017 (Livestream Nov 19th -21st, or watch on-demand)”. That item is dated September 21st. Here your posts is dated September 19th and states that the conference starts “today”. Can you clarify is there is something coming for November or did some dates just get mixed up? Anyways, happy that I can still catch some content on demand. Thanks!
Sounds like a typo. The conference already happened. You can check out all the videos at https://channel9.msdn.com/Events/dotnetConf/2017