Some notes on the final day @ LEAP! This was the final day and filled with various talks. For me the most interesting one today was related to the upcoming .NET 3.0 Image may be NSFW.
Clik here to view.
.NET 3.0
- Microsoft has the focus on two new workloads for .NET: AI and IoT
- Open Sourced WinForms and WPF in December 2018
- Improved performance
Clik here to view.
- Repl: Browse your API as a filesystem (list the methods etc.)
- Swagger IntelliSense helps decorating API’s
- Windows desktop support with WPF and WinForms
- Designers and templates will come later
Demo: proposal of some new features for Visual Studio and .NET 3.0. Under NDA, very fresh. Mentioned the NSwag package for producing OpenAPI Spec documentation.
Migrate Full Framework to Core by going through the .NET Standard. Nuget Microsoft.Windows.Compatibility will fix build errors. There is also a .NET Analyzer (Microsoft.DotNet.Analyzers.Compatibility) to provide full text warnings and hints.
Microservices: https://github.com/dotnet-architecture/eShopOnContainers
Clik here to view.
- ML.NET 0.9 enables simple entry point to ML for developers. Few lines of code and your good.
- EF for Cosmos DB will come soon,
- followed by EF for Redis.
Blazor is now Razor Components and part of .NET Core. Because of WebAssembly it runs in all desktop and mobile browsers and is truly client-side. It’s a full single-page application (SPA) framework inspired by the latest JavaScript SPA frameworks, featuring support for offline/PWA applications, app size trimming, and browser-based debugging.
Clik here to view.
Blazor uses only the latest web standards. No plugins or transpilation needed. It runs in the browser on a real .NET runtime (Mono) implemented in WebAssembly that executes normal .NET assemblies.
It is currently being moved to the ASP.NET Core 3.0 repo, so there is most of the information on this topic: https://github.com/aspnet/AspNetCore/tree/master/src/Components
