Oqtane has always contained a SyncManager on the server which has traditionally only been used to synchronize specific server-side events with client-side state. In Oqtane 3.2.1 this capability has now been included using the standard .NET EventHandler capability in conjunction with the SyncManager to raise SyncEvents (which inherit from the standard .NET EventArgs).
The 3.2.1 release is primarily focused on stabilization. This includes performance improvements to the client startup logic for Blazor Hybrid and Blazor WebAssembly, improvements to base url handling and static resources for component resusability in .NET MAUI, support for Roles as part of OpenID Connect integrations, as well as a new capability to capture server-side events in your custom code.
Blazor applications utilize a client/server architecture. This means that in the majority of Blazor hosting models, a client application is deployed to a specific client device or process which interacts with the server using standard HTTP requests. One of the biggest challenges in most client/server models is how to ensure the client stays updated with the latest fixes and improvements. Obviously the more automated and seamless this process can be from an end user perspective, the more successful it will b
The 3.1.4 release is primarily focused on stabilization. This includes a variety of performance optimizations, user experience improvements, and localization enhancements. Based on the fact that performance is one of overarching goals for the framework, we conducted some load testing and optimized the most frequently executed methods both from a client and server workload perspective.
Microservices have exploded in popularity in the past decade, with many organizations attempting to use this architectural approach to avoid the limitations of large, monolithic systems. While much has been written about using this approach to decompose the backend of enterprise software applications, many companies continue to struggle with how to manage the frontend.
Hot Reload was introduced in .NET 6 and it is enabled by default in the latest versions of Visual Studio. The idea behind Hot Reload is that developers can modify code assets in their project and those changes will be immediately reflected in their run-time development environment. However there is some unexpected behavior you should be aware of.