Based on interactions with customers using .NET Core in different environments, this article explores options for adding observability to .NET Core apps. Looking specifically into OpenTelemetry and Application Insights SDKs to add observability to a sample distributed application.
Since its inception, the .NET Core configuration provider for Azure App Configuration has provided the capability to monitor changes and sync them to the configuration within a running application. We recently redesigned this functionality to allow for on-demand refresh of the configuration.
Blazor 0.8.0 is now available! This release updates Blazor to use Razor Components in .NET Core 3.0 and adds some critical bug fixes. Get started with Blazor 0.8.0 today - installation details included.
.NET Core 3.0 Preview 2 is now available and it includes the list of what's new in this preview. To get started with ASP.NET Core in .NET Core 3.0 Preview 2 install the .NET Core 3.0 Preview 2 SDK
Blazor 0.7.0 is now available! This release focuses on enabling component coordination across ancestor-descendent relationships. We've also added some improvements to the debugging experience.
Here's what's new in the Blazor 0.7.0 release:
Cascading values and parameters
A full list of the changes in this release can be found in the Blazor 0.7.0 release notes.
We’ve just released the second preview of the upcoming 2.4.0 release of ASP.NET SignalR. As we mentioned in our previous blog post on the future of ASP.NET SignalR we are releasing a minor update to ASP.NET SignalR (the version of SignalR for System.Web and/or OWIN-based applications) that includes,
Blazor 0.6.0 is now available! This release includes new features for authoring templated components and enables using server-side Blazor with the Azure SignalR Service. We're also excited to announce our plans to ship the server-side Blazor model as Razor Components in .NET Core 3.0!
Today we’re very happy to announce that the first preview of the next minor release of ASP.NET Core and .NET Core is now available for you to try out. We’ve been working hard on this release over the past months, along with many folks from the community,
Blazor 0.5.0 is now available! This release explores scenarios where Blazor is run in a separate process from the rendering process. Specifically, Blazor 0.5.0 enables the option to run Blazor on the server and then handle all UI interactions over a SignalR connection. This release also adds some very early support for debugging your Blazor .NET code in the browser!
Blazor 0.4.0 is now available! This release includes important bug fixes and several new feature enhancements.
New features in Blazor 0.4.0 (details below):
Add event payloads for common event types
Use camelCase for JSON handling
Automatic import of core Blazor namespaces in Razor
Send and receive binary HTTP content using HttpClient
Templates run on IIS Express by default with autobuild enabled
Bind to numeric types
A full list of the changes in this release can be found in the Blazor 0.4.0 release notes.