.NET Core 3.0

What's New in .NET Core 3.0 Features?

The following changes are coming in ASP.NET Core 3.0:

Default executable: .NET Core will now build framework dependent executable by default.

Build copies dependencies: dotnet build now copies NuGet dependencies for your application from the NuGet cache to the build output folder.

.NET Core 3.0 adds support for C# 8.0

Local dotnet tools: While .NET Core 2.1 supported global tools, .NET Core 3.0 now has local tools. Local tools are similar to global tools but are associated with a particular location on disk.

Run a local tool with the following command:
dotnet tool run <your-tool-command-name>
Source - https://blogs.msdn.microsoft.com/dotnet/2018/05/07/net-core-3-and-support-for-windows-desktop-applications/

Windows desktop: This is the biggest enhancements, now we can build Windows desktop applications using WPF and Windows Forms and It also support using modern controls and Fluent styling from the Windows UI XAML Library (WinUI).

We can create a new WPF or Windows Forms app with the following dotnet commands:
1.      dotnet new winforms
2.      dotnet new wpf

Benefits of .NET Core for Desktop:
1.      Performance improvements and other runtime updates that will delight your users.
2.      Super easy to use or test a new version of .NET Core for just one app on a machine.
3.      Enables both machine-global and application-local deployment.
4.      Support for the .NET Core CLI tools and SDK-style projects in Visual Studio.

Fast built-in JSON support, high-performance, low allocation, forward-only reader for UTF-8 encoded JSON text, read from a ReadOnlySpan<byte>

Async streams: The IAsyncEnumerable<T> type is a new asynchronous version of IEnumerable<T>

Cryptography Support has been added for AES-GCM and AES-CCM ciphers, implemented via System.Security.Cryptography.AesGcm and System.Security.Cryptography.AesCcm.

Cryptographic Key Import/Export :.NET Core 3.0 Preview 1 supports the import and export of asymmetric public and private keys from standard formats, without needing to use an X.509 certificate.

ARM64 Linux support

Tiered compilation: Tiered compilation is on by default with .NET Core 3.0. It is a feature that enables the run-time to more adaptively use the Just-In-Time (JIT) compiler to get better performance, both at startup and to maximize throughput.

Some of the following improvements are also new in .NET Core 3.0.
1.      Brotli support built in to HttpClient
2.      ThreadPool.UnsafeQueueWorkItem(IThreadPoolWorkItem)
3.      Unsafe.Unbox
4.      CancellationToken.Unregister
5.      Complex arithmetic operators
6.      Socket APIs for TCP keep alive
7.      StringBuilder.GetChunks
8.      IPEndPoint parsing
9.      RandomNumberGenerator.GetInt32

Removal of some sub-components in .NET Core 3.0 :
As part of this change, some notable sub-components will be removed from the ASP.NET Core shared framework in 3.0
1.      Json.NET (Newtonsoft.Json)
2.      Entity Framework Core (Microsoft.EntityFrameworkCore.*)
3.      Microsoft.CodeAnalysis (Roslyn)

Entity Framework Core will ship as “pure” NuGet packages in 3.0

JSON.NET or Entity Framework Core will continue to work with ASP.NET Core, but they will not be "in the box" with the shared framework.

In ASP.NET Core 3.0, we plan to remove the following assemblies from Microsoft.AspNetCore.App. These APIs will still be available as NuGet packages.
1.      Microsoft.AspNet.WebApi.Client
2.      Microsoft.AspNetCore.Authentication.Facebook
3.      Microsoft.AspNetCore.Authentication.Google
4.      Microsoft.AspNetCore.Authentication.JwtBearer
5.      Microsoft.AspNetCore.Authentication.MicrosoftAccount
6.      Microsoft.AspNetCore.Authentication.OpenIdConnect
7.      Microsoft.AspNetCore.Authentication.Twitter
8.      Microsoft.AspNetCore.Authentication.WsFederation
9.      Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore
10. Microsoft.AspNetCore.Identity.EntityFrameworkCore
11. Microsoft.AspNetCore.Identity.UI
12. Microsoft.AspNetCore.JsonPatch
13. Microsoft.AspNetCore.MiddlewareAnalysis
14. Microsoft.AspNetCore.Mvc.Razor.Extensions
15. Microsoft.AspNetCore.NodeServices
16. Microsoft.AspNetCore.Owin
17. Microsoft.AspNetCore.Razor.Design
18. Microsoft.AspNetCore.Razor.Language
19. Microsoft.AspNetCore.Server.Kestrel.Https
20. Microsoft.AspNetCore.SpaServices
21. Microsoft.AspNetCore.SpaServices.Extensions
22. Microsoft.CodeAnalysis.Razor
23. Microsoft.EntityFrameworkCore
24. Microsoft.EntityFrameworkCore.Abstractions
25. Microsoft.EntityFrameworkCore.Analyzers
26. Microsoft.EntityFrameworkCore.Design
27. Microsoft.EntityFrameworkCore.InMemory
28. Microsoft.EntityFrameworkCore.Relational
29. Microsoft.EntityFrameworkCore.SqlServer
30. Microsoft.EntityFrameworkCore.Tools
31. Microsoft.Extensions.Caching.SqlServer
32. Microsoft.Extensions.DiagnosticAdapter
33. System.Net.WebSockets.WebSocketProtocol

To upgrade your project from ASP.NET Core 2.1 to 3.0, you may need to add several <PackageReference> items for the following.

For More Questions and Answers, go to below link.

Anil Singh is an author, tech blogger, and software programmer. Book writing, tech blogging is something do extra and Anil love doing it. For more detail, kindly refer to this link..

My Tech Blog - https://www.code-sample.com/
My Books - Book 1 and Book 2

www.code-sample.com/. Powered by Blogger.