Coding With David

  Introduction When building enterprise applications in C#, efficiently managing data access is crucial for maintainability and performance. As applications grow, coordinating multiple repositories becomes increasingly complex. The Unit of Work pattern offers an elegant solution to this challenge, allowing you to simplify your service layer while maintaining a clean separation of concerns. In this post, I'll show you how to implement the Unit of Work pattern in a .NET application to coordinate multiple generic repositories. The Problem: Repository Proliferation Imagine you're working on an approval workflow system. You have several related entities: ApprovalRequest , ApprovalAction , and User . Following the repository pattern, you might create a separate repository for each: public interface IRepository<T> where T : class { Task<T> GetByIdAsync(object id); Task AddAsync(T entity); // Other CRUD operations } Your service might look like this: publ...

  If you've been working with Blazor applications for a while, you've likely encountered Razor files and C# classes that have accumulated numerous @using statements. As these applications grow in size and complexity, it's common to see components with 10 or more imports at the top of each file. This article explores best practices for organizing these statements to keep your codebase clean, maintainable, and efficient. The Challenge of Growing Using Statements As Blazor applications expand, the number of dependencies increases. Components begin to require additional namespaces for: Core framework functionality Component libraries Custom models and services Utility classes Third-party integrations Before you know it, the top third of your files is consumed by import statements, making the actual component code less immediately visible and maintainable. Three Approaches to Managing Using Statements C# and Blazor offer several mechanisms for organizing these imp...

  As Blazor continues to gain traction in the .NET ecosystem, one challenge that remains universal across web development is organizing CSS effectively. In this post, I'll share a structured approach to CSS organization in Blazor applications that promotes maintainability, reusability, and a clean separation of concerns. The Three-Tier CSS Architecture After working on numerous enterprise-scale Blazor applications, I've found that a "three-tier" CSS architecture works exceptionally well: Global CSS - Core design system elements Page-specific CSS - Layout and page-specific overrides Component-specific CSS - Isolated styles for reusable components Let's break down each tier and explore how they work together. Global CSS: Your Design System Foundation Your main CSS file should form the foundation of your application's design system, containing: A limited color palette (6 colors maximum) A controlled font selection (3 fonts maximum) Utility clas...

  Progressive Web Apps (PWAs) have revolutionized the way we build and deliver applications, offering a native-like experience with the flexibility of the web. Blazor, as a modern framework for building PWAs with .NET, empowers developers to create robust applications. However, with increased functionality comes greater responsibility to ensure your app is secure. In 2025, security threats are more sophisticated than ever, making it critical to adopt best practices when building Blazor PWAs. In this post, we’ll explore modern security strategies, including HTTPS, authentication, CSRF protection, and securing service workers, to safeguard your Blazor PWA. 1. Enforce HTTPS Everywhere Why HTTPS? HTTPS encrypts the communication between your app and the user, protecting sensitive data from being intercepted by attackers. For PWAs, HTTPS is a requirement to use service workers and enable features like push notifications and offline support. Best Practices Enforce HTTPS : Configure your ...