Microsoft drops

Suitable for production if you're brave, but you don't have a Windows Forms designer yet

  A Windows Forms .NET Core 3.0 application implemented simply by copying a folder

A Windows Forms .NET Core 3.0 application simply implemented copying a folder

Microsoft has released .NET Core 3.0 Preview 7 and Visual Studio 16.3 Preview 1, which work together to enable new features, including Windows desktop applications created with .NET Core and C # 8.0.

NET Core 3.0 is the first version of the Microsoft .NET open source cross-platform fork that can point to Windows Presentation Foundation (WPF) and Windows Forms, the two most commonly used frameworks for Windows desktop applications.

This does not mean that these frameworks now work cross-platform; They are still only Windows. However, it does mean that in Windows .NET Core it gains features such as COM interoperability.

Why build desktop applications in .NET Core, instead of the reliable .NET Framework, especially if it is still only for Windows? One reason is that the .NET Framework is now a kind of inherited runtime and is not compatible with C # 8.0, which is also approaching general availability.

Microsoft wants to play safe with the .NET Framework and keep it compatible, so some new language and API functions in the .NET Core require runtime changes, they won't work in the .NET Framework. The official word about this is here, where Immo Landwerth program manager explains that the new features in the .NET Standard 2.1 will not reach the .NET Framework, which remains in the .NET Standard 2.0.

Yes, there are multiple .NET incompatible standards.

This means that developers need to get away from the .NET Framework if they want to keep up with the new language features. Eventually, this will also be a problem for libraries and popular components.

Microsoft has already announced that the version of .NET Core after 3.0 will be .NET 5.0, and will lose the designation "Core", which underlines the inherited status of the .NET Framework.

There is, of course, an inconvenience. Yes, you can now create WPF and Windows Forms applications with .NET Core 3.0, but it is not exactly the same WPF or Windows Forms framework that you are used to. Rather, they are forks (open source) of those frames, with some missing APIs. Microsoft has a portability analysis tool that you can use as a guide.

.NET Core 3.0 support is indeed good, with a notable exception of the Windows Communication Foundation (WCF), which has not all been ported.

  Configuration of the .NET Portability Analyzer is a reminder of the different variants of .NET that Micrsosoft has created

The configuration of .NET Portability Analyzer is a reminder of the different variants of .NET that Microsoft has created

The Portability Analyzer is also a useful reminder of how many .NET variants exist, including dead ends such as Windows Phone and Silverlight.

Another benefit of making the change is to take advantage of possible future improvements of WPF and Windows Forms now that these frameworks are open source. They have been almost frozen for years, with Microsoft pushing developers towards their Universal Windows Platform (UWP).

. The .NET Core developers also have an option for autonomous deployment, which means that the runtime libraries are grouped by request. We verified this by creating a Windows Forms application using the .NET Core 3.0 and C # 8.0 features, publishing it in a folder using the standalone option and copying the folder to a Windows 7 PC. The application was executed immediately.

There is also an option for "framework dependent" implementation, which will use a full-system installation of .NET Core 3.0.

.NET Core 3.0 Preview 7 has a "Go Live" license, which means it is compatible with Microsoft in production. This also implies that Microsoft does not expect to make many changes before general availability other than bug fixes, although the main program administrator Richard Lander said: "Notable exceptions are: WPF, Windows Forms, Blazor and Entity Framework" – a substantial list. For production use, Microsoft is likely to think primarily of ASP.NET applications instead of these newer and less proven features.

It is necessary to have Visual Studio 16.3 Preview in order to use the latest .NET Core. Lander said in the comments to his post: "We don't believe there is any risk when using VS 16.3 Preview from the point of view of working in production applications." However, Windows Forms developers will have to manage without a form designer when working with .NET Core 3.0, unless you create a multi-purpose project that can share forms created for the .NET Framework.

One of the reasons Microsoft is eager to move to .NET Core 3.0 is better container support. The new version is compatible with containers and supports Docker memory limits and CPU limits. The details are here.

ASP.NET Core 3.0 is part of the same wave of releases as .NET Core 3.0 and Visual Studio 16.3. One of the features included is Blazor, which allows you to create web user interface components using C #. Blazor can run on the server or in the browser. When running in the browser, it uses WebAssembly. Blazor on the server side will be in ASP.NET Core 3.0, but Blazor on the client side will remain in the preview. Blazor is a route to a cross-platform GUI written in C # and running in .NET Core, using browser technology.

In general, this is an important step in the transition to .NET Core as the main version of .NET, although you can be sure that the .NET Framework only for Windows will remain for the foreseeable time. ®

Balancing consumerization and corporate control

For More Updates Check out Blog, Windows Softwares Drivers, Antivirus, Ms Office, Graphic Design Don’t Forget to Look Our Facebook Page Get Into Pc like us & follow on Twitter- @getinpc

Please Note: This content is provided and hosted by a 3rd party server. Sometimes these servers may include advertisements. does not host or upload this material and is not responsible for the content.