{"id":22982,"date":"2019-05-06T15:22:54","date_gmt":"2019-05-06T22:22:54","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/dotnet\/?p=22982"},"modified":"2019-05-08T15:39:05","modified_gmt":"2019-05-08T22:39:05","slug":"net-core-is-the-future-of-net","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/net-core-is-the-future-of-net\/","title":{"rendered":".NET Core\u00a0is the Future of .NET\u00a0"},"content":{"rendered":"

We introduced .NET Core 1.0 on November 2014<\/a>. The goal with .NET Core was<\/span>\u00a0to take the learning from our experience building, shipping and servicing .NET Framework\u00a0<\/span>over<\/span>\u00a0the previous 12 years and build a better product. Some example<\/span>s<\/span>\u00a0of these improvements are\u00a0<\/span>side-<\/span>by-<\/span>side\u00a0<\/span>installations\u00a0<\/span>(you can install a new version and not worry about breaking existing apps), self-contained applications (applications can embed\u00a0<\/span>.NET, so .NET does not need to be on the computer), not\u00a0<\/span>being\u00a0<\/span>a component of the Windows operating system (<\/span>.NET\u00a0<\/span>ship<\/span>s<\/span>\u00a0new releases\u00a0<\/span>independent of the OS<\/span>\u00a0schedule) and many more. On top of this<\/span>,<\/span>\u00a0we made .NET Core open source and cross platform.<\/span>\u00a0<\/span><\/p>\n

.NET Core 1<\/span>.0<\/span><\/a>\u00a0was primarily focused on\u00a0<\/span>high performance web and microservices<\/span>.<\/span>\u00a0<\/span>.NET Core 2<\/span>.<\/span>0<\/span><\/a>\u00a0<\/span>added<\/span>\u00a0<\/span>20K\u00a0<\/span>more\u00a0<\/span>API<\/span>s and\u00a0<\/span>components\u00a0<\/span>like Razor Pages and\u00a0<\/span>SignalR<\/span>,<\/span>\u00a0making it easier to port web applications to .NET Core. And now .NET Core 3<\/span>.<\/span>0<\/span>\u00a0embraces the desktop\u00a0<\/span>by\u00a0<\/span>adding WinForms, WPF and Entity Framework 6\u00a0<\/span>making it\u00a0<\/span>possible\u00a0<\/span>to port desktop applications<\/span>\u00a0to .NET Core.\u00a0<\/span>\u00a0<\/span><\/p>\n

After .NET Core 3<\/span>.0<\/span>\u00a0we will not port any more\u00a0<\/span>features\u00a0<\/span>from .NET Framework. If you are a Web Form<\/span>s<\/span>\u00a0developer and<\/span>\u00a0want to build a new application on .NET Core<\/span>,<\/span>\u00a0we would recommend\u00a0<\/span>Blazor<\/span>\u00a0which provides the closes<\/span>t<\/span>\u00a0programming model. If you are a\u00a0<\/span>re<\/span>moting or WCF Server developer and want to build a new application on .NET Core<\/span>,<\/span>\u00a0we would recommend either\u00a0<\/span>ASP.NET\u00a0<\/span>Core<\/span>\u00a0<\/span>Web\u00a0<\/span>API<\/span>s<\/span>\u00a0or\u00a0<\/span>gRPC<\/span><\/a>, which provides cross platform and cross programming language\u00a0<\/span>contract based<\/span>\u00a0RPC<\/span>s). If you are a Windows Workflow\u00a0<\/span>developer<\/span>\u00a0there is an open source port of Workflow to .NET Core<\/a><\/span>.\u00a0<\/span>\u00a0<\/span><\/p>\n

With the<\/span>\u00a0<\/span>.NET Core 3.0\u00a0<\/span>release\u00a0<\/span>in September 2019 we think that all\u00a0<\/span>*<\/span>new<\/span>*<\/span>\u00a0.NET applications should be based on .NET Core. The primary\u00a0<\/span>a<\/span>pplication types<\/span>\u00a0<\/span>from .NET Framework are supported,\u00a0<\/span>and where we did not port something over there is a recommended modern replacement. All future investment in .NET will be in .NET Core. This includes:\u00a0<\/span>Runtime,<\/span>\u00a0<\/span>JIT<\/span>, AOT,<\/span>\u00a0<\/span>GC,\u00a0<\/span>BCL (Base Class Library),\u00a0<\/span>C#, VB<\/span>.NET<\/span>, F#, ASP.NET,\u00a0<\/span>Entity Framework<\/span>,\u00a0<\/span>ML.NET,\u00a0<\/span>WinForms, WPF<\/span>\u00a0and Xamarin.<\/span>\u00a0<\/span><\/p>\n

.NET Framework 4.8<\/a> will be the last major version of .NET Framework.<\/span>\u00a0<\/span>If you have existing .NET Framework applications that you are\u00a0<\/span>maintaining,<\/span>\u00a0<\/span>there is\u00a0<\/span>no\u00a0<\/span>need<\/span>\u00a0<\/span>to move these applications to .NET Core.<\/span>\u00a0<\/span>We will continue to\u00a0<\/span>both\u00a0<\/span>service<\/span>\u00a0and\u00a0<\/span>support .NET<\/span>\u00a0Framework<\/span>,\u00a0<\/span>which includes bug<\/span>–<\/span>, reliability<\/span>–<\/span>\u00a0and security fixes<\/span>. It will continue to ship with Windows\u00a0<\/span>(much of Windows depends on .NET\u00a0<\/span>Framework) and we will continue\u00a0<\/span>to improve the tooling support for\u00a0<\/span>.NET<\/span>\u00a0in Visual Studio\u00a0<\/span>(Visual Studio is written on .NET Framework).<\/span>\u00a0<\/span><\/p>\n

Summary<\/span>\u00a0<\/span><\/h2>\n

N<\/span>ew applications should be built o<\/span>n<\/span>\u00a0.NET Cor<\/span>e. .NET Core is where future investments in .NET will happen. Existing application<\/span>s<\/span>\u00a0<\/span>are safe to remain on .NET Framework which\u00a0<\/span>will be supported<\/span>. Existing\u00a0<\/span>applications that want to take advantage of the new features\u00a0<\/span>in .NET<\/span>\u00a0<\/span>should consider moving to .NET\u00a0<\/span>Core.\u00a0<\/span>As we plan into the future, we will be bringing in even more capabilities to the platform. You can read about our plans here<\/a><\/span>.<\/span>\u00a0<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

We introduced .NET Core 1.0 on November 2014. The goal with .NET Core was\u00a0to take the learning from our experience building, shipping and servicing .NET Framework\u00a0over\u00a0the previous 12 years and build a better product. Some examples\u00a0of these improvements are\u00a0side-by-side\u00a0installations\u00a0(you can install a new version and not worry about breaking existing apps), self-contained applications (applications can […]<\/p>\n","protected":false},"author":810,"featured_media":58792,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[196,195],"tags":[],"class_list":["post-22982","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dotnet-core","category-dotnet-framework"],"acf":[],"blog_post_summary":"

We introduced .NET Core 1.0 on November 2014. The goal with .NET Core was\u00a0to take the learning from our experience building, shipping and servicing .NET Framework\u00a0over\u00a0the previous 12 years and build a better product. Some examples\u00a0of these improvements are\u00a0side-by-side\u00a0installations\u00a0(you can install a new version and not worry about breaking existing apps), self-contained applications (applications can […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/22982","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/users\/810"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/comments?post=22982"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/22982\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media\/58792"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media?parent=22982"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/categories?post=22982"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/tags?post=22982"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}