Skip to main content
UploadLanguage (EN)Support
BusinessMobileSocial MediaMarketingTechnologyArt & PhotosCareerDesignEducationPresentations & Public SpeakingGovernment & NonprofitHealthcareInternetLawLeadership & ManagementAutomotiveEngineeringSoftwareRecruiting & HRRetailSalesServicesScienceSmall Business & EntrepreneurshipFoodEnvironmentEconomy & FinanceData & AnalyticsInvestor RelationsSportsSpiritualNews & PoliticsTravelSelf ImprovementReal EstateEntertainment & HumorHealth & MedicineDevices & HardwareLifestyle
Bertrand Le Roy, profile picture
Uploaded byBertrand Le Roy
PPTX, PDF12,243 views

.Net Core

.NET Core is a modular, cross-platform implementation of .NET designed for modern software development, differing significantly from .NET Framework. The document outlines migration strategies, highlights compatibility issues, and provides resources for developers to port existing applications. It emphasizes that not all projects should migrate, particularly those relying on Windows-specific frameworks.

Engineering◦
Downloaded 505 times
.NET Core How to migrate and write new code for .NET Core
Bertrand Le Roy ▪ Senior Program Manager on .NET Core ▪ One of the founders of Orchard ▪ http://weblogs.asp.net/bleroy ▪ https://blogs.msdn.microsoft.com/dotnet/tag/week-in-net/ ▪ https://www.youtube.com/channel/UCvtT19MZW8dq5Wwfu6B0oxw
Objectives ▪ What’s .NET Core and when to use it (or not) ▪ How to create a new library, ASP.NET, or console application ▪ How to port existing code
Innovation Any platformOpenness .NET Core ASP.NET 5
.NET Core ≠ .NET Framework
.NET Framework 4.6 ▪ .NET implementation for any scenario on Windows with comprehensive library support
.NET Core ▪ Modular and smaller implementation of .NET ▪ Cross-platform ▪ App-level isolation ▪ Built in the open ▪ Optimized for specific workloads ▪ Built for the next ten years of software development
Next gen JIT (RyuJIT) SIMD Runtime Components Compilers Languages innovation .NET Compiler Platform .NET Core 5 Libraries .NET Framework 4.6 Libraries NuGet packages .NET Framework 4.6 .NET Core What’s common, and what’s not?
What’s not supported? ▪ WPF ▪ Winforms ▪ WebForms ▪ Binary serialization… ▪ Anything Windows-specific: registry, ACLs, perf counters, etc.
Significant change: Reflection foo.GetType() → foo.GetType().GetTypeInfo()
API Portability resources ▪ Portability analyzer VS extension ▪ https://github.com/Microsoft/dotnet-apiport/releases ▪ http://dotnetstatus.azurewebsites.net/ ▪ https://packagesearch.azurewebsites.net/ ▪ http://forums.dotnetfoundation.org/ ▪ https://gitter.im/dotnet/corefx ▪ https://dotnet.github.io/porting *
Managing expectations ▪ This is very much a new platform with a known flavor ▪ There is a cost to migration ▪ There are things to learn ▪ Not all projects can or should migrate
Should I migrate my project? Cannot: ▪ WPF, WinForms, unless UWP ▪ ASP.NET WebForms Should (absolutely): ▪ General purpose libraries Should (maybe): ▪ ASP.NET MVC ▪ Micro-services ▪ Console apps ▪ Rewrite ▪ Talent expertise on Linux
DEMO Porting FluentPath
Dependencies ▪ Most fundamental libraries first: test frameworks, tooling, data access, JSON, logging, IoC, etc. ▪ Go to the source, ask the author ▪ Offer to help, or fork ▪ Switch to another Core-compatible library ▪ DIY
Testing ▪ xUnit was first, now NUnit, MsTest ▪ Secondary test libraries (mocking, functional testing, etc.) in progress
Debugging ▪ On Windows: Visual Studio ▪ Everywhere: VS Code
Tooling Your choice of tool, on your choice platform ▪ Visual Studio on Windows ▪ Visual Studio Code on Mac, Linux, or Windows ▪ vi or emacs with OmniSharp ▪ etc.
.NET CLI replaces DNX, DNVM, DNU ▪ dotnet new ▪ dotnet restore ▪ dotnet run ▪ dotnet build ▪ dotnet build –native ▪ dotnet dosomethingcool
DEMO Creating a new application
Q&A