dotNetConf2019

Editor's Notes

• #21: We’ve added a ton of features to ASP.NET Core in version 3.0 on order to make building resilient microservices easier.
• #28: There is a new microservices related Worker Service project template for building lightweight background workers, which can be run under orchestrators like Kubernetes.
• #29: Works on a GenericHost. What is a generic host, it’s just that generic. It works in the same pattern as ASP.NET but without anything web specific. The web host is preconfigured to boot Kestrel, this one is not. All it does is if you have any services in your app that is a Hosted Service, it will run them. In this snippet, Worker is the service, inherits from BackgroundService but could also inherit from IHostedService.
• #32: Worker service sidecar.
• #33: In the microservices world, each services you create does a specific process. In previous versions of .NET or ASP.NET Core specifically MVC was included in order to get the routing. However, many of the APIs we are developing are just maybe the M and C of MVC or maybe not of the letters.
• #34: Here is a very basic service that just returns HelloWorld on the /hello path. No MVC needed to route or respond to the HTTP request. We saw a similar pattern in the HealthChecks example under the /health route. Simply add the statement app.UseRouting(); and then app.UseEndPoints and map your routes
• #46: Streaming demos
• #47: Streaming demos
• #55: Worker service sidecar.
• #57: Blazor is a new client-side web UI framework based on .NET and C# instead of JavaScript.   .NET has always had great support for building server-rendered web apps with ASP.NET, where your .NET code runs on the server and generates HTML & JSON responses. But if you ever wanted to add some client-side functionality to your web app that runs in the browser on the user's device, that meant you had to write some JavaScript.   Well, not anymore! Blazor enables full-stack web development with .NET using only open web standards. .NET Core 3.0 ships support for Blazor Server apps, which enables you to handle client-side UI interactions over a real-time SignalR connection. And in the near future with Blazor WebAssembly you'll be able to run your .NET code directly in the browser on WebAssembly-based .NET runtime.
• #64: Creating components Using components Component parameters Routing Layouts Dependency injection Event handling Data binding Forms & validation JS interop Use local storage Using .NET Standard libraries
• #81: 2019 – Introduce .NET 5 – Windows, Mac, Linux, Android, IOS all run .NET Core’s runtime Same BCL used on all platforms, same runtime used on all platforms Native code compilation on all platforms, by merging .NET Native and Mono AOT JIT and AOT Runtime .NET 5 is the next major version of the .NET Platform that brings technologies from .NET Framework, .NET Core and & Mono runtimes and frameworks together into one .NET platform.  .NET 5 will have one Base Class Library (BCL) that will contain APIs for building any type of application. All .NET workloads are supported with application frameworks including cross-platform web development with ASP.NET, iOS and Android mobile development with Xamarin, Windows Desktop, and cross-platform IoT.  .NET 5 will have both Just-in-Time (JIT) and Ahead-of-Time (AOT) compilation models for the multiple compute and device scenarios it must support. JIT has better performance for server and desktop workloads as well as development environments. AOT has better startup, a small footprint, and is required for mobile and IoT devices.  .NET 5 will also have one unified toolchain supported by new SDK project types, will have a flexible deployment model (Side-by-Side and self-contained EXEs) and continue .NET Core's superior performance for server & cloud workloads.