Сергей Корж ".net core - новый старт старой платформы"
TRANSCRIPT
.NET Coreновый старт старой платформы
Сергей КоржKorzh.com
[email protected]://korzh.comhttp://facebook.com/sergiy.korzh@korzhs
Agenda
2
1 .NET CoreCurrent state of .NET Framework, .NET Core benefits, .NET Standard library
ASP.NET CoreASP.NET today, ASP.NET Core benefits, Minimal ASP.NET Core project, Middleware pipeline, DI, Configuration, Logging
3 Tips/Tricks & TakeawaysBuilding your own middleware, Using DI to change default services, 2 Identity pipelines
4 Roadmap & conclusions
.NET Framework today
Cons:• Not cross-platform
• Tied to system
• DLL Hell
• Too long updates cycle
Pros:• Mature (since 2001)
• Large installation base
• Strong community
.NET Core Command Line Interface (CLI)
$ dotnet new
$ dotnet restore
$ dotnet build
$ dotnet run
$ dotnet publish
$ dotnet /path/to/assembly
.NET Standard
WINDOWS APPLICATIONS
CROSS-PLATFORMSERVICES
MOBILE APPLICATIONS
.NET FRAMEWORK .NET CORE XAMARIN
ASP.NET Problems
Monolithic (System.Web)
Platform dependent (Windows only)
Long development cycle
Proprietary
Duplication of concepts(controllers, actions in MVC and WebAPI)
ASP.NET Core
Totally modular
Cloud ready
Open source
Faster development cycle
Choose your own editor and tool
Cross platform
Fast!
ASP.NET Core benchmarks
Request / second (millions) based on preliminary internal tests. Official tests will be available at TechEmpower website
ASP.NET Core: important parts
Middleware pipeline
Logging
Identity
Dependency Injection
Configuration
Project.json (to be deprecated)
MVC & WebAPI combined
NPM, Bower, Gulp
.NET Core Roadmap
Version 1.1 (Q4 2016 / Q1 2017)• C# 7 support• F# support• .NET Standard 2.0 (?)• Support for .csproj / MSBuild project system• URL rewriting middleware• Few improvement for Azure
Version 1.0.1 – released
Version 1.2 (Q1 2017 / Q2 2017)• WebSockets• SignalR• Razor Pages (view without MVC controllers)
Conclusions (is .NET Core / ASP.NET Core a right choice?)
• Desktop applications (WinForms, WPF)• Mobile applications• Platform-tied (Windows)• WebForms applications
No (or just impossible to use)
• Small/middle-size MVC web-apps (ASP.NET Core over .NET Framework 4.x)• New web-applications• Cross-platform is a requirement
Yes (or at least worth to try)
NB: Consider targeting your shared code libraries as .NET Standard
Thank you!
http://korzh.com
http://facebook.com/sergiy.korzh