upgrading your asp.net 4.0+ skills to asp.net core...asp.net core •kestrel is the cross-platform...

4/12/2019

Kevin Griffin

Upgrading Your ASP.NET 4.0+ Skills to ASP.NET Core

Welcome

▪ Microsoft MVP

▪ Host of the 2 Frugal Dudes Podcast

▪ Founder of RevolutionConf

kevin@swiftkick.in

twitter.com/1kevgriff

kevgriffin.com

swiftkick.in

Kevin Griffin

Owner, Swift Kick

4/12/2019

Let’s Keep in Touch!

▪ I’m always working on new stuff around ASP.NET – and I’d love to keep you up to date.

▪ Free webinars, blog posts, courses, etc

▪ Sign up + free gift!

https://go.swiftkick.in/codestock2019

(all lowercase)

A Couple Assumptions

▪ You are heavily invested in ASP.NET Classic.

▪ .NET 3.5 or higher

▪ You’ve realized the future is .NET Core

▪ With the upcoming release of .NET Core 3.0, Microsoft is recommending all greenfield development is done on Core

▪ .NET Framework will be supported long term – but not compatible with new features

4/12/2019

Goodbye IIS, Hello Kestrel

Goodbye IIS, Hello Kestrel!

ASP.NET 4.5

• ASP.NET applications were bootstrapped by an IIS handler.

• IIS was responsible for processing incoming request, and handing them off to ASP.NET

• Stuck on Windows!

ASP.NET Core

• Kestrel is the cross-platform web server built for ASP.NET Core applications.

• Processes requests directly

• Runs on Linux, Windows, Mac – or any platform that supports the .NET Standard.

4/12/2019

Bootstrapping an ASP.NET Core Application

CreateDefaultBuilder(…)

▪ The method does a lot of work

▪ Sets working directories

▪ Loads configuration

▪ Environment variables

▪ Appsettings.json

▪ Command line

▪ Configure logging

▪ Configure Kestrel (web server)

▪ Configure IIS integration

4/12/2019

Demo: dotnet new web

Dependency Injection

4/12/2019

ASP.NET 4.5

• Relied on external libraries to provide Dependency Injection and Inversion of Control (IOC) containers.

• Other dependencies had to be configured to use your DI solutions.

ASP.NET Core

• Baked in at the framework level, no external libraries required!

• Supported out-of-the-box by all ASP.NET Core features. Ex: SignalR, Identity, etc.

• CI works outside of ASP.NET Core application.

4/12/2019

▪ AddSingleton()

▪ Creates one instance for the lifetime of the application.

▪ AddTransient()

▪ Create one instance per instantiation.

▪ Example: You might want to use IUserRepository in multiple classes in ONE request. Each class gets its own unique instance of FakeUserRepository.

▪ AddScoped()

▪ Creates one instance per Request.

▪ Example: You might want to use IUserRepository in multiple classes in ONE request. Each class gets the same instance for the request.

Routing and Pipelines

4/12/2019

MVC Routing Options

▪ Attribute-based Routing

▪ Default preference

▪ Use the [Route] attribute to decorate Actions with the request path the Action should handle.

▪ Use shortcuts such as [HttpGet], [HttpPost], etc to save on attributes!

MVC Routing Options

▪ Route prefixes can still be defined on the Controller

4/12/2019

MVC Routing Options

▪ If you’re used to “convention-based” routing, that is still possible by manually configuring the UseMvc() method.

▪ PERSONAL OPINION: Please don’t do this.

▪ If you’d like to use WebApi-style controllers and actions (verb-based), that’s doable too!

MVC vs WebAPI

4/12/2019

MVC vs WebApi

▪ In ASP.NET Core, there is no separation between Controller and ApiController.

▪ A controller is a controller.

▪ Documentation still defined MVC and WebAPI separately – but they both derive from Controller.

Action Return Types

▪ IActionResult

▪ Abstracted response.

▪ Several built in types:

▪ View()

▪ Ok()

▪ BadRequest()

▪ Forbid();

▪ Unauthorized();

▪ StatusCode();

▪ And more!

4/12/2019

Action Return Types

▪ Specific Type

▪ Like WebAPI, the controller will automatically convert the response into the appropriate format (JSON) and return it.

Action Return Types

▪ ActionResult<T>

▪ Best of both worlds!

▪ Return a specific type OR an ActionResultmessage

4/12/2019

MVC vs WebAPI

Other Goodies

Static files and wwwroot

▪ In IIS, wwwroot is the default location for your web application.

▪ In ASP.NET Core, wwwroot is the “public” folder for you application.

4/12/2019

Integration with SPA CLIs

▪ A growing number of developers are using CLIs for Vue, React, and Angular for front-end and ASP.NET for backend.

▪ This makes development difficult with ASP.NET – since it wants to be everything to everyone.

▪ You can add a proxy into the pipeline to help with debugging locally!

Razor Pages

▪ In ASP.NET 4.0+, working with Razor meant working with “MVC”

▪ Any pages built in Razor needed a corresponding Controller and Action.

▪ Razor Pages are single pages that provide the “good” parts of Razor without the ceremony of “MVC”.

4/12/2019

Other Topics I Probably Don’t Have Time For

▪ Performance, performance, performance

▪ Custom Middleware

▪ Background/Hosted Services

▪ Health Checks

▪ Logger enhancements

Thanks for attending!

▪ Microsoft MVP

▪ Host of the 2 Frugal Dudes Podcast

▪ Founder of RevolutionConf

kevin@swiftkick.in

twitter.com/1kevgriff

kevgriffin.com

swiftkick.in

Kevin Griffin

Owner, Swift Kick

upgrading your asp.net 4.0+ skills to asp.net core...asp.net core •kestrel is the cross-platform...

Documents

asp.net core mvc student workbook · chapter 1 introduction...

meetup asp.net core

asp.net mvc core

asp.net core troublemaker oder...

moving asp.net mvc to asp.net core

asp.net core security

01 - [asp.net core] plénière

asp.net core -...

asp.net core vs. asp.net 4

asp.net core 1.0 documentation - read the docs · asp.net...

개발자 & it전문가용 소프트웨어 소핑몰 asp.net...

04 - [asp.net core] entity framework core

seri belajar asp.net: asp.net core mvc & mysql

build an asp.net core and ef core hands on lab · running...

asp.net core 1.0 documentation - read the docs ·...

asp.net core razor pages? · 2018-03-02 · asp.net core...

asp.net core 101

asp.net core demos

asp.net coreradar.zhaw.ch/~rege/dnet_fs20/dnet2_10.pdf ·...

découverte .net core et asp.net core