Part of the series: Blazor and EF Core
- In this blog post…
- Get Started: Authentication
- Extend Identity to Audit User Account Management
- The Contact Model and Data Annotations
- Data Access with Entity Framework Core
- Logging
- Repository Pattern and Server Implementation
- Implement the Repository
You are viewing a limited version of this blog. To enable experiences like comments, opt-in to our privacy and cookie policy. Show consent dialog.
Blazor WebAssembly is here and ready for production. It enables new scenarios for .NET developers to run existing code and libraries in the browser without a plugin. Blazor WebAssembly enables the creation of desktop, tablet, and mobile friendly apps with offline support as a Progressive Web Application (PWA). The built-in templates enable security for enterprise authentication and authorization scenarios. Although Blazor WebAssembly supports most .NET Standard class libraries out of the box, there are some constraints that exist due to the browser security model. For example, the raw TCP ports needed to connect directly to a SQL Server database aren’t available in the browser. That means the client must connect to data over an API.
I built the Blazor WebAssembly EF Core Example application as a learning tool and starting point for line of business applications. I wanted to go beyond a simple “Hello, World” demo and create an application that implements many features often found in line of business apps, like filtering and sorting, auditing and concurrency resolution. To get started with the application, visit the repo then follow the instructions. The rest of this blog post will explain the functionality and how it was implemented.
JeremyLikness/BlazorWasmEFCoreExample
To start with, I created an application with authentication.
Get Started: Authentication
There are several scenarios that Blazor WebAssembly supports for security. First, there is standalone Blazor WebAssembly. This handles the project as a typical standalone Single Page Application (SPA) that is deployed as a set of static assets that can be published through any web server. The second option is hosted that creates an ASP. NET Core application that can optionally host authentication as well as Web API endpoints to support the client application. These are the available options based on your hosting model:
#blazor
