{"id":132347,"date":"2023-03-09T19:15:00","date_gmt":"2023-03-09T19:15:00","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/dotnet\/?p=44695"},"modified":"2023-03-09T19:15:00","modified_gmt":"2023-03-09T19:15:00","slug":"whats-new-for-the-winforms-visual-basic-application-framework","status":"publish","type":"post","link":"https:\/\/sickgaming.net\/blog\/2023\/03\/09\/whats-new-for-the-winforms-visual-basic-application-framework\/","title":{"rendered":"What\u2019s new for the WinForms Visual Basic Application Framework"},"content":{"rendered":"
\n
\n
\n
<\/div>\n

Klaus Loeffelmann<\/p>\n<\/div>\n<\/div>\n

\n
\n
<\/div>\n

Melissa Trevino<\/p>\n<\/div>\n<\/div>\n<\/div>\n

\n

March 9th, 2023<\/i>3<\/a><\/span> 4<\/span><\/a><\/span><\/span><\/span><\/p>\n<\/p><\/div>\n

<\/p>\n

.NET from version .NET Core 3.1 up to .NET 7 has plenty of advantages over .NET
\nFramework: it provides performance improvements in almost every area, and those
\nimprovements were an ongoing effort over each .NET version. The
\nlatest improvements in .NET
\n6<\/a> and
\n.NET
\n7<\/a> are
\nreally worth checking out.<\/p>\n

Migrating your Windows Forms (WinForms) Visual Basic Apps to .NET 6\/7+ also
\nallows to adopt modern technologies which are not (or are no longer) supported in .NET
\nFramework. EFCore is one example<\/a>: it is
\na modern Entity Framework data access technology that enables .NET developers to
\nwork with database backends using .NET objects. Although it is not natively
\nsupported for VB by Microsoft, it is designed in a way that it is easy for the
\ncommunity to build up on it and provide code generation support for additional
\nlanguages like Visual Basic<\/a>. In
\nthat context there are also changes and improvements in the new WinForms
\nOut-of-Process Designer for .NET, especially around Object Data
\nSources<\/a>.
\nFor the WinForms .NET runtime, there are a series of improvements in different
\nareas which have been introduced with the latest releases of .NET:<\/p>\n

The new Visual Basic Application Framework Experience<\/h2>\n

In contrast to the project property Application Framework Designer experience in
\nearlier versions of Visual Studio and for .NET Framework, you will noticed that
\nthe project properties UI in Visual Studio has changed. It\u2019s style is now in
\nparity with the project properties experience for other .NET project types: we
\nhave invested into modernizing the experience for developers, focusing on
\nenhancing productivity and a modern look and feel.<\/p>\n

\"Screenshot<\/p>\n

We\u2019ve added theming and search to the new experience. If this is your first time
\nyou\u2019re working with the new project properties experience in Visual Studio, it\u2019s
\na good idea to read up on the the introductory
\nblog<\/a>.<\/p>\n

In contrast to C# projects, Visual Basic Application Framework projects use a
\nspecial file for storing the Application Framework project settings: the
\nApplication.myapp<\/em> file. We\u2019ll talk more about the technical details of how
\nthis file connects the project settings to the VB project specific code
\ngeneration of the My<\/code> namespace later, but one thing to keep in mind is how the
\nUI translates each property\u2019s value to this file:<\/p>\n