.NET Fest 2019. Оля Гавриш. .NET Core 3.0 и будущее .NET

Editor's Notes

• #8: <PublishSingleFile>true</PublishSingleFile> <RuntimeIdentifier>win-x64</RuntimeIdentifier> <PublishTrimmed>true</PublishTrimmed> (Фреймворк установлен на более 2 билионов компьютеров)
• #9: <LangVersion>8.0</LangVersion> <Nullable>enable</Nullable>
• #16: <LangVersion>8.0</LangVersion> <Nullable>enable</Nullable>
• #26: Blazor is in large part possible thanks to relatively new open web standard called Web Assembly. WA is a bite code for the web. The idea is that if you can compile your code into WA. It can now run in any browser on any platform at near native speed. And we’ve been working for a while now on getting .NET run great on WA. We are building a .NET runtime in WA.
• #28: This is how Blazor WA App works. The browser provides core WA support, on top of that we’ve built .NET WA runtime. Then you build your Razor components that could compile into the normal .NET assemblies. They are downloaded with the runtime into the browser and then executed directly in the browser. The browser then sends all it’s UI events to your .NET core, your components run, they render the UI, and Blazor does all the hard work to figure out what exactly changed in the UI. The difference then sent back to the DOM and updated very-very efficiently. The cool thing about Blazor is that you can host it in many different ways. We’ve just talked about running your app on WA. But alternatively you can also run your Blazor app and host them on the server. Using the same components. The way Blozor Server App works is your components run on the server, the browser sets up a real-time signalR connection with the server and that’s what it uses to handle and send all the UI events that the user is creating. When a button click occurs, it get’s sent to the server. The corresponding component runs just like it did on a Blazor WA app. Component render. Blazor does all the hard work of calculating the diff. It serialized that diff back to the browser so it can be applied to the DOM. In Core 3 – support for Server and Blazor WA will be shipped in May next year.
• #29: How do you pick between Blazor Server App and Blazor WA App.
• #33: I’d like to invite Mads up on stage to show off C# 8.0.
• #35: We know we have millions of Windows developers using .NET. So .NET Core has added support for Windows Forms and WPF. This allows you to take advantage of the innovation happening in .NET Core, while still using the UI frameworks you know and love.
• #36: And to make deploying, testing and collecting telemetry easy, we’re announcing today the release of .NET Core 3.0 Windows Apps support in App Center.
• #39: We’ve added a ton of features to ASP.NET Core in version 3.0 on order to make building resilient microservices easier.
• #42: 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.