- File new Razor Pages project
- Open
Program.cs
and talk aboutWebHost.CreateDefaultBuilder
- Show configuration & logging
WebHostBuilder
APIs - Open
Startup.cs
- Show
IConfiguration
is now injected 'cos it's in DI - Show that all the configuration logger setup is gone 'cos it's defaulted by
WebHOst.CreateDefaultBuilder
- Add authentication for Twitter & Google
- Show that all the APIs are now available by default because of the new
Microsoft.AspNetCore.All
meta-package - Open the CSPROJ and show how simple it is with just the single package
- Talk about the new runtime store that ensures all the packages aren't deployed with the application
- Publish the application and note the output size, then compare it to the publisht output size of a previously prepared & published 1.1 application
- Go the publish output of the 1.1 application prepared earlier whice includes startup time measuring code and run the app, noting the total time printed
- Go back to the 2.0 application and add the code in
Program
to measure the time to start the app, complete a request to the home page and shutdown again - Publish the application again and run it and note the reduced startup time compared to the 1.1 application
- Go back to
Startup.cs
and add the code to configure Cookie & Twitter auth inConfigureServices
- Add the authentication middleware and explain how it's different to 1.1
- Add the configuration secrets for Twitter and Google to User Secrets
- Add a logout endpoint using route-to-middleware
- Add a Razor Page "Login.cshtml" and add buttons for the authentication schemes
- Demo logging in/out
- Create and register an
IHostedService
that logs the number of requests received in the last N secondns - Create an no-op
IHostingStartup
and debug through it to demonstrate its discovery and execution - Transition to Visual Studio
- Explain that
IHostingStartup
facilitates the in VS and Azure Application Insights and diagnostics light-up experience - Demonstrate Application Insights data during VS debugging
- Open the Azure Portal and show Application Insights working in a 2.0.0 application with no code, and correlated request tracking across two application instances
- Conference Planner
- Launch the application and show the ASP.NET Core logs appearing in the VS output window
- Create an
ITagHelperComponent
that injects a heading at the top of each page - Demo Razor Pages
- Open
Index.cshtml
and show the@page
directive - Navigate to the Page Model via the
@model
directive - Create a
Customer
class &AppDbContext
, configure the context to use in-memory database
Last active
June 14, 2017 08:52
-
-
Save DamianEdwards/f1c31a44a22d39e0cbb3740339e45e18 to your computer and use it in GitHub Desktop.
NDC Oslo 2017 - What's new in ASP.NET Core 2.0
- .NET Standard 2.0
- Startup Time - DEMO
Microsoft.AspNetCore.All
meta-package - DEMO- Runtime Store
- Program/Startup.cs changes - DEMO
- Configuration changes
IConfiguration
in DI container
- Logging changes
- Configuration filtering - DEMO
ILoggerProvider
in DI container
- DefaultHostBuilder - DEMO
- Configuration changes
- Kestrel
- Pluggable transports
- Pluggable HTTP parser
- Edge readiness (timeouts)
- Pipelines
- Systemd socket activiation
- Faster
- Security (Authn/z) rewrite - DEMO
IMiddleware
- Razor rewrite
- Extensible directives
- New tooling infrastructure
- C# 7 support
IHostingStartup
- DEMOIHostedService
- DEMO- Full IIS support in VS - DEMO
- ASP.NET Core logs in VS - DEMO
WebListener
renamed toHttpSysServer
- MVC
TempData
cookie provider is now defaultITagHelperComponent
for injection of "automatic" Tag Helpers from DI container - DEMO<head>
&<body>
Tag Helpers - DEMOTempData
backed properties - DEMO- Razor Pages - DEMO
- SPA Services templates for Angular & React in Visual Studio
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment