Here’s what’s new in this preview release:

• .NET Hot Reload updates for dotnet watch
• ASP.NET Core SPA templates updated to Angular 11 and React 17
• Use Razor syntax in SVG foreignObject elements
• Specify null for Action and RenderFragment component parameters
• Reduced Blazor WebAssembly download size with runtime relinking
• Configurable buffer threshold before writing to disk in Json.NET output formatter
• Subcategories for better filtering of Kestrel logs
• Faster get and set for HTTP headers
• Configurable unconsumed incoming buffer size for IIS 

.NET 8 RC1 is now available. This is our first of two release candidates. This release includes a new AOT mode for both Android and WASM, System.Text.Json improvements, and Azure Managed Identity support for containers. Now is great time to pick up and test .NET 8 if you haven’t yet.  

Experiments with the new WASI workload in .NET 8 Preview 4
.NET 8 adds a new "wasi-experimental" workload, replacing the earlier Wasi.Sdk. This is a step towards giving .NET native, built-in support for server-side WebAssembly scenarios.
This video shows how to get started, then demonstrates how .NET+WASI creates possibilities for new kinds of apps and new ways to use .NET. 

The current process creates friction for users. Finding an OTP within an SMS message, then copying and pasting it to the form is cumbersome, lowering conversion rates in critical user journeys. Easing this has been a long standing request for the web from many of the largest global developers. Android has an API that does exactly this. So does iOS and Safari 

Normally when Microsoft decides an end-of-life date for a product, they really just mean “you shouldn’t be using this anymore, but we understand if you do”. This won’t be the case for Silverlight, which will no longer be downloadable after October 12, 2021. 

Following my last post on my ASP.NET MVC SEO-Framework I started looking at adding support also for ASP.NET Core MVC, with its superior Dependency Injection and Tag Helpers. 

Here’s a summary of what’s new in this preview release:

• ASP.NET Core support for native AOT
• Server-side rendering with Blazor
• Render Razor components outside of ASP.NET Core
• Sections support in Blazor
• Monitor Blazor Server circuit activity
• SIMD enabled by default for Blazor WebAssembly apps
• Request timeouts
• Short circuit routes 

Here’s a summary of what’s new in this preview release:

• HTTP/2 performance improvements
• Typed results for minimal APIs
• OpenAPI improvements for minimal APIs
• Return multiple results types from minimal APIs
• Route groups
• Client results in SignalR
• gRPC JSON transcoding
• Project template option to use Program.Main method instead of top-level statements
• Rate limiting middleware 

The two most important topics I want to focus on in this post are:

• Repository Management
• Versioning Strategy

We have different options for each of them: You can go with Monorepos or Polyrepos for hosting your code, and you can pick different versioning methods like Semantic Release, Manual Versioning, Global Versioning, etc. I'll talk about each of them in the next sections. 

One of the main reasons for using .NET Core is that you can run it on multiple platforms and architectures. So you can build an app that will run on Windows, but also on Linux, macOS and on different architectures like x86 and ARM. This is perfect for lots of scenarios, including desktop applications.