Demonstration of how to create an externally extendable dynamic page, which will support all controls that we can add later in a separate assembly without the recompilation of the dynamic page
Blazor Server and Blazor WebAssembly (client) don't store state by default, resulting in a subpar user experience. This article tackles solutions to the problem.
Advanced Blazor techniques are covered such as sharing Razor class libraries between a Blazor WebAssembly project and Blazor server-side. Shows how to reference embedded resources like JavaScript libraries, debug on server-side then deploy as client-side and debug in the browser.
How can you connect securely without storing credentials in the client and hosting your own identity service? The solution is to use Azure Active Directory for authentication and communicate securely with a serverless Azure Function.
This article walks you through my project Planetary Docs, a repository that showcases a full application that supports Create, Read, Update, and Delete operations (CRUD) using Blazor (Server), Entity Framework Core and Azure Cosmos DB.
Submit an article or tip