This is an extremely interesting question – especially from a .NET Developer’s perspective. A couple of .NET features would eventually have to be migrated into a completely new technology set.
For example, if you are an ASP.NET Web Forms Developer, you would have to, first of all, understand the ASP.NET MVC development approach, and then learn and understand the fundamentals of .NET Core development. And finally, learn the ASP.NET Razor Page model (which replaces the ASP.NET Web Forms approach). I know that a lot of people would say that you need not learn ASP.NET MVC, but the reason I am recommending it is to help ensure that one learns the base concepts and the relationship between Model, ViewModel, and Controller, which is fundamental to understand the concept of InputModel, DomainModel, and DataModel in a typical enterprise-grade ASP.NET application.

Another example of a technology migration is what’s happening to WCF! This is the biggest surprise; from the kind of responses, I have seen so far. WCF is being replaced by the gRPC approach introduced in .NET CORE 3.0. I have seen a lot of projects which were earlier utilizing XML Web Services, migrated to WCF just because it was new in the stack. And then, we got ASP.NET Web API – which kind of brought about the adoption of a whole lot of rich client-side web development technology stacks and highly evolved the adoption of the Micro-Services architecture development. But now, by creating more refined segregation between the WCF Development approach – now reinvented as gRPC and continuing to offer WEB API, the .NET Foundation Team has actually helped developers understand and use the right technology for the correct approach. gRPC cannot be hosted in a web-stack. So, web developers would have to adopt WEB API, and the rest of the distributed computing stack of WCF would now be served by the gRPC approach.

Or the complete lack of WF in the .NET 5 Framework. .NET Core 3 does not have it. And I haven’t come across anything in this direction. The current recommendation is to adopt an external open-source unofficial port of the Workflow Foundation libraries.

And then, there is always the standard features and enhancements we get from a Major Upgrade. Don’t forget to check out the following URLs for further reading on the .NET 5 Roadmap:
• .NET Platform Overview and Roadmap
Microsoft Build 2019 Developer Conference May 6-8 Seattle, WA
• Introducing .NET 5
Introducing .NET 5 | .NET Blog

Innovation stacks not coming to .NET 5

Dot net 5 Development Company in USA and UK

ASP.NET Web Forms

ASP.NET WebForms won’t come to .NET 5 and Microsoft is right now prescribing to move to Blazor which was an exploratory undertaking that got elevated to official as of late. The other elective decisions are Angular, React, and Vue SPA structures in the event that you are great at JavaScript.

On the off chance that you are presently utilizing MVC as a full-stack web application, you can keep on utilizing a similar stack by utilizing Core MVC or the new Razor Pages presented in .net center 2.0 which may look like web structures to rapidly construct web structure applications without perspectives and controllers. Notwithstanding, in the event that you are creating present-day web applications for big business, it’s smarter to consider a solitary page application, for example, Blazor, Angular or React rather than a conventional web application for giving rich customer side usefulness.

WCF (Windows Communication Foundation)

The declaration of “WCF is going to miss the .NET 5 train” astonished many including me. There has been a great deal of exchange on GitHub to bring back WCF into the .NET center, however, Microsoft chose not to bring it on the grounds that their underlying estimation porting WCF into.NET Core would take three years. (source: DotNetRocks Podcast)

Microsoft is prescribing to utilize gRPC as an elective which is a cutting edge open-source superior RPC system that can keep running in any condition. In any case, not at all like WCF, gRPC can’t be facilitated in IIS starting today due to HTTP/2 execution of Http. Sys doesn’t bolster HTTP reaction trailing headers which gRPC depends on.

WWF (Windows Workflow Foundation)

Work process Foundation isn’t getting ported into .NET Core. Each venture application will have some work process or BPM devices coordinated with it. On the off chance that you utilized WWF in your application, Microsoft is prescribing to take a gander at the informal fork of WF runtime for porting into .NET Core.

Innovation stacks that are coming to .NET 5

Winforms, WPF, and UWP

Microsoft is bringing Windows Desktop Packs (Winforms, WPF, and UWP) to help work area applications that just deals with windows. I wouldn’t anticipate that anybody should utilize WinForms for any new advancement anyway this will port heritage Winforms applications into .NET 5. This doesn’t imply that .Net center design is evolving. It will at present be a cross-stage structure yet when you are including work area packs, it focuses to work just on windows. Be that as it may, porting existing windows work area application into .Net center will give the extra advantage of Core Runtime and API execution enhancements and sending adaptability.

What’s Replaced

EF Core – Entity Framework Core is supplanting EF 6 in .Net Core Framework. Core – is supplanted by Core. Check the relocation direct for porting application into center

ASP.NET Core MVC – ASP.NET Core MVC brought together ASP.NET MVC and Web API. Check the relocation direct for porting MVC application into center MVC.

MSIX – Microsoft new bundling apparatus which replaces the old MSI bundle installer for work area applications.

vJsonDocument – New Json Document library from System.Text.Json.JsonDocument API to supplant It is 2-3x times quicker than old

A couple of other significant things to feature

The most recent variant of C# 8.0 presented a ton of new dialect highlights including Async Stream, Ranges, Nullable Reference Types, and Pattern Matching, and so forth.. Be that as it may, they will be accessible just on .NET Core 3.0 or more which means it isn’t coming to Legacy .NET Framework, or .NET Core 2.2, 2.1, 1.0. It plainly demonstrates that “.NET Framework is dead and .NET Core is what’s to come”.

On the off chance that you are wanting to port .NET Framework applications into .NET Core, you should break down your APIs utilized in your task to see whether it is good or not. .NET Portability Analyzer is an apparatus that breaks down and decides how adaptable your application is crosswise over .NET stages.


As a .NET designer, I am glad to see the eventual fate of .NET and the course it goes into. I never again need to learn JavaScript for the SPA system on the grounds that Blazor will do that. I never again need to learn Python for AI on the grounds that ML.NET will do that. I never again need to learn Android/Swift in light of the fact that Xamarin will do that. On the off chance that you know C#, presently, you can build up an application that can run anyplace from IoT to Cloud. In any case, this change is going to influence a ton of big business clients who have the item/structure dependent on WCF and WebForms.

Click to rate this post!
[Total: 1 Average: 5]