The Problem

What they neglect to say is all that testability and persistence ignorance flies right out the window when you create a new ASP.NET Web Application using the MVC template and "Individual User Accounts" authentication. What you get is a single-layered application, tightly coupled to Entity Framework, that:

• Ignores the patterns that facilitate testing, including: the repository pattern, unit of work pattern, and dependency injection;

• Forces you to implement their IUser interface in your application’s User entity, thereby coupling it to ASP.NET Identity;

• Eliminates any clear separation between your entities, persistence concerns, and business logic. Persistence ignorance? Forget about it.

Thankfully, due to the extensibility designed into ASP.NET Identity, it is possible to ditch the reference to the Microsoft.AspNet.Identity.EntityFramework assembly and write a custom implementation that can address these and other architectural issues. Just be forewarned: it is not a trivial undertaking, and you’ll have to put up with some code smell that is baked into the Microsoft.AspNet.Identity.Core assembly. 

This article will cover two methods of adding 1, ++i, and i++, and explain why ++i may be better than i++ in most situations.

Licensed under a Creative Commons attribution-noncommercial license. All code in this book may also be considered licensed under an MIT license 

This repo is for experimentation and exploring new ideas that may or may not make it into the main dotnet/runtime repo.  

This is a companion extension to the C# extension that brings some improvements to the experience for debugging Blazor WebAssembly in VS Code.  

Build a CRM with Blazor WebAssembly & Syncfusion in .NET 7 🔥 

What's Coming for Blazor Hybrid in .NET 7 

Multi-tenancy with EF Core in Blazor Server Apps 

3+1 ways to manage state in your Blazor application