Windows 10: Visual Basic WinForms Apps in .NET 5 and Visual Studio 16.8

Brink · Nov 24, 2020

Visual Basic, along with its Application Framework, is supported in .NET 5 and Visual Studio 16.8! Visual Studio 16.8 includes the Windows Forms Designer, so Visual Basic is ready for you to migrate existing applications or create new applications.

While .NET Core has had Visual Basic since the first release, and WinForms since it was released in .NET Core 3.1, it did not include the Application Framework library and WinForms Designer support Visual Basic programmers expect. .NET 5 is the next version of .NET Core and we think .NET 5 is ready for you to migrate existing .NET Framework apps or create new WinForms applications.

Weâre excited about the updates for Visual Basic in .NET 5, but first a reminder that you can base your decision to migrate to .NET 5 on whether or not you want its new features and how you need to interop with .NET 5 applications. The .NET Framework will be supported as part of Windows for a very long time. New features will not be added to .NET Framework. New features, including new WinForms features, will be added only to .NET 5 and future versions.

Visual Studio 16.8 and .NET 5 include the following updates for WinForms development in .NET 5:

Designer Event Handling support: Visual Basic events are hooked up with a Handles keyword on the code behind method. This presented significant challenges to the WinForms designer and did not work correctly in .NET Core 3.1. This has been fixed.

Application Framework: The Visual Basic Application Framework provides event-based startup, meaning you donât need a Sub Main for WinForms applications. A new version of the Application Framework is available in .NET 5.

Single Instance applications: .NET 5 introduces Single Instance Applications to the .NET Core family. The new version also has updated logic that should work well in more scenarios.

Updates to Visual Studio dialogs: Updates have been made to a few dialogs to support Visual Basic features in the new project format. This work is ongoing.

Visual Basic WinForms template: We waited to add the template to Visual Studio until you could create WinForms applications with the Application Framework. This new template is the default in Visual Studio, and available via a switch on dotnet new in the .NET CLI.

Additional Visual Basic Runtime features: The last few versions of .NET Core have ported features of the Visual Basic Runtime. We believe this work is complete and that missing features canât work the same way on .NET 5.

Click to expand...

Read more: https://devblogs.microsoft.com/dotne...l-studio-16-8/

:)

NJDevils28 · Nov 24, 2020

Visual Basic WinForm - Visual Studio 2019

Hi,

If I'm not in the correct forum, please advise me of where I should be posting this.

I have written a program that required I call System.Security.Cryptography to create a File Hash. I'm using MD5. However, for me to add my program to the Microsoft Store, I cannot have any code that needs elevation. Such as the UAC that is required to
call System.Security.Cryptography.

Is there a way around this? Is it possible to create the MD5 hash without breaking any MS Store rules?

I'm coding a WinForm using Visual Studio Community 2019 in Visual Basic.

Thank you in advance,

-Ron B.

Amol S. · Nov 24, 2020

Visual Studio (.NET Framework)

Do you still have the Visual Studio Installer or Visual Studio Manager still installed?

If you have it still installed and it opens up correctly, you could try removing all additional packages that are installed, and try reinstalling them again. It could have been a corruption issue relating to package extensions that you may have installed
into Visual Studio 2017 Community Edition. If that does not work, go to apps in settings, and select Visual Studio 2017 Community Edition and select repair. If that does not work, you could try going to TechNet, and asking there for help. It could be a
bug with the current version of the .NET Framework 48 or with the recent version of Visual Studio 2017 Community Edition.

If you can not find Visual Studio Installer or Visual Studio Manager, unfortunately in this situation the only thing I can think of is if you still have the installation file that you downloaded from the Visual Studio website. If you can't find that, then
I suggest that you download Visual Studio 2019 Community Edition, since the 2017 Community edition is not given for free anymore unless you have some sort of subscription. However, I suggest that you still check with TechNet before taking this step.

Brink · Nov 24, 2020

Visual Basic support planned for .NET 5.0

We’ve heard your feedback that you want Visual Basic on .NET Core. Earlier versions of .NET Core supported Class Library and Console applications types. Starting with .NET 5 Visual Basic will support:

Class Library

Console

Windows Forms

WPF

Worker Service

ASP.NET Core Web API

We are supporting these application types to provide a good path forward for the existing VB customer who want to migrate their applications to .NET Core. This allows Visual Basic customers to take advantage of new platform features like side-by-side deployment, cross platform support, performance and new API improvements.

One of the major benefits of using Visual Basic is that the language has been stable for a very long time. The significant number of programmers using Visual Basic demonstrates that its stability and descriptive style is valued. Going forward, we do not plan to evolve Visual Basic as a language. This supports language stability and maintains compatibility between the .NET Core and .NET Framework versions of Visual Basic. Future features of .NET Core that require language changes may not be supported in Visual Basic. Due to differences in the platform, there will be some differences between Visual Basic on .NET Framework and .NET Core.

If you are happy with .NET Framework, you can be confident that it will remain supported as long as Windows is supported because it is shipped with the OS. Both Visual Basic and C# customers can continue to use .NET Framework and need to port to .NET Core only if you want features like those listed above. If your application uses technologies that aren’t supported on .NET Core, like WebForms, Workflow or WCF, you might want to stay on .NET Framework because porting will require work to move to newer technologies.

Visual Studio regularly adds new features to improve the experience for developers, including those using Visual Basic and either .NET Core or .NET Framework. An example is the recent addition of IntelliCode for Visual Basic.

Visual Basic is a great language and a productive development environment. The future of Visual Basic will include both .NET Framework and .NET Core and will focus on stability, the application types listed above, and compatibility between the .NET Core and .NET Framework versions of Visual Basic.

.NET Team
Click to expand...

Source: https://devblogs.microsoft.com/vbtea...d-for-net-5-0/

Tweet

— Twitter API (@user) View on Twitter
Click to expand...

Windows 10: Visual Basic WinForms Apps in .NET 5 and Visual Studio 16.8

Visual Basic WinForms Apps in .NET 5 and Visual Studio 16.8

Visual Basic WinForms Apps in .NET 5 and Visual Studio 16.8

Visual Basic WinForms Apps in .NET 5 and Visual Studio 16.8

Visual Basic WinForms Apps in .NET 5 and Visual Studio 16.8 - Similar Threads - Visual Basic WinForms

does visual studio 2022 support winforms for python

does visual studio 2022 support winforms for python

SoftWire for Visual Studio .Net

SoftWire for Visual Studio .Net

Visual Basic Studio

Visual Basic Studio

Visual Basic WinForm - Visual Studio 2019

Visual Studio (.NET Framework)

New Visual Studio, Visual Studio for Mac, .NET Core and Xamarin.Forms