This document discusses .NET Core and ASP.NET Core. It summarizes that .NET Core is a cross-platform implementation of .NET that is optimized for performance and size. It also discusses that ASP.NET Core is a redesigned, cross-platform framework for building modern web apps built on top of .NET Core. The document provides details on the modular nature and benefits of both .NET Core and ASP.NET Core, such as being open-source and having long term support from Microsoft.

2. Vũ Đức Tuyến
C#.NET Software Developer - Independent
@kanvuduc
2009
SILVERLIGHT
2014
XAMARIN
2016
ASP.NET CORE
2011
ASP.NET MVC

3. 






4. .NET Core is a subset of .NET framework but a cross-platform implementation of the
.NET Platform.
 A port of .NET from scratch
 Redesigned in very small modules
 Platform agnostic
 OSS
 LTS and FTS by MS
 Better optimized performance
 Optimizable app/lib size
 Cross-platform dev/dep
 Free
 Warranty to last

5. YES AND NO
.NET Portability Analyzer

6.  VS 2015 Update 3
 .NET Core Tools
 Windows Only

7. .NET Core SDK Visual Studio Code Yeoman

9.  Cannot use of existing .NET libraries
 Cannot use .NET Core libraries in .NET lib/app
 Cannot use .NET Core libraries in Mono lib/app
 Only support console app and ASP.NET Core web app for now

10. ASP.NET Core is a new open-source and cross-platform framework for building modern
cloud based internet connected applications
 Built on top of .NET Core
 Rewritten of ASP.NET from scratch
 Redesigned in very small modules
 OSS
 LTS and FTS by MS
 Cross-platform dev/dep
 Better optimized performance
 Optimizable app size
 Free
 Warranty to last

11. Compilers and runtime components
(.NET compiler platform: Roslyn, C#, VB, F#, RyuJIT, SIMD)
ASP.NET
4.6
ASP.NET Core
.NET Framework 4.6
Full-featured and integrated
.NET libraries and runtime for Windows
.NET Core
Modular and optimized
.NET libraries and runtimes
CoreCLR .NET Native
UWPWPF, WCF, …

12.  Unified MVC and Web API
 Built-in DI
 Configurations defined in JSON
 Middleware instead of HttpModule
 Friendly Razor with TagHelper
 ViewComponent instead of child action
 Self hosted
 Side-by-side deployment

15.  SingalR
 3rd DI
 Websockets
 View precompilation
 Response caching middleware
 URL Rewriting middleware

16. 1. Does your project strongly depend on 3rd party libraries?
2. Do you want raw performance?
3. Do you want to deploy on any sever regardless of OS?
4. Do you want to use Docker for your development and production?
5. Are you willing to port your existing libraries to .NET Core?

17. •
•

18. THANK YOU!