Skip to main content

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.
By Anil Singh | Rating of this article (*****)

Popular posts from this blog

nullinjectorerror no provider for httpclient angular 17

In Angular 17 where the standalone true option is set by default, the app.config.ts file is generated in src/app/ and provideHttpClient(). We can be added to the list of providers in app.config.ts Step 1:   To provide HttpClient in a standalone app we could do this in the app.config.ts file, app.config.ts: import { ApplicationConfig } from '@angular/core'; import { provideRouter } from '@angular/router'; import { routes } from './app.routes'; import { provideClientHydration } from '@angular/platform-browser'; //This (provideHttpClient) will help us to resolve the issue  import {provideHttpClient} from '@angular/common/http'; export const appConfig: ApplicationConfig = {   providers: [ provideRouter(routes),  provideClientHydration(), provideHttpClient ()      ] }; The appConfig const is used in the main.ts file, see the code, main.ts : import { bootstrapApplication } from '@angular/platform-browser'; import { appConfig } from ...

How To convert JSON Object to String?

To convert JSON Object to String - To convert JSON Object to String in JavaScript using “JSON.stringify()”. Example – let myObject =[ 'A' , 'B' , 'C' , 'D' ] JSON . stringify ( myObject ); ü   Stayed Informed –   Object Oriented JavaScript Interview Questions I hope you are enjoying with this post! Please share with you friends!! Thank you!!!

List of Countries, Nationalities and their Code In Excel File

Download JSON file for this List - Click on JSON file    Countries List, Nationalities and Code Excel ID Country Country Code Nationality Person 1 UNITED KINGDOM GB British a Briton 2 ARGENTINA AR Argentinian an Argentinian 3 AUSTRALIA AU Australian an Australian 4 BAHAMAS BS Bahamian a Bahamian 5 BELGIUM BE Belgian a Belgian 6 BRAZIL BR Brazilian a Brazilian 7 CANADA CA Canadian a Canadian 8 CHINA CN Chinese a Chinese 9 COLOMBIA CO Colombian a Colombian 10 CUBA CU Cuban a Cuban 11 DOMINICAN REPUBLIC DO Dominican a Dominican 12 ECUADOR EC Ecuadorean an Ecuadorean 13 EL SALVA...

Encryption and Decryption Data/Password in Angular

You can use crypto.js to encrypt data. We have used 'crypto-js'.   Follow the below steps, Steps 1 –  Install CryptoJS using below NPM commands in your project directory npm install crypto-js --save npm install @types/crypto-js –save After installing both above commands it looks like  – NPM Command  1 ->   npm install crypto-js --save NPM Command  2 ->   npm install @types/crypto-js --save Steps 2  - Add the script path in “ angular.json ” file. "scripts" : [                "../node_modules/crypto-js/crypto-js.js"               ] Steps 3 –  Create a service class “ EncrDecrService ” for  encrypts and decrypts get/set methods . Import “ CryptoJS ” in the service for using  encrypt and decrypt get/set methods . import  {  Injectable  }  from ...

Angular Testing Questions and Answers | 9, 8, 7, 6

What Is Testing? The testing is a tools and techniques for a unit and integration testing Angular applications . Why Test? Tests are the best ways to prevent software bugs and defects. How to Setup Test in Angular Project? Angular CLI install everything you need to test an Angular application. This CLI command takes care of Jasmine and karma configuration for you. Run this CLI command- ng test The test file extension must be “.spec.ts” so that tooling can identify the test file. You can also unit test your app using other testing libraries and test runners. Types of Test – The all great developer knows his/her testing tools use. Understanding your tools for testing is essential before diving into writing tests. The Testing depends on your project requirements and the project cost. The types of Testing looks like - 1.       Unit Test 2.       Integration Test 3.       En...