Razor Class Libraries (RCLs) allow you to share Blazor components across multiple apps. With .NET Core 3.1 and upcoming .NET 5, they now support including static assets (CSS, JS, images) inside the NuGet package. This guide builds a reusable “Modal” component library. Project Structure Create a new RCL project: Static Web Assets Place CSS in […]
Read more →Search Results for: name
Kubernetes Operators in .NET: Getting Started
Operators extend Kubernetes with custom domain logic. While usually written in Go, the .NET ecosystem has matured with the `KubeOps` SDK. We can now write C# operators to manage custom resources like `DatabaseCluster` or `TenantNamespace`. The Operator Pattern Defining a CRD in C# The Reconciler Key Takeaways Operators encode operational knowledge into software. The Reconcile […]
Read more →Building Teams Apps with SPFx and React
SPFx web parts can run as Teams tabs. Here’s how to build a Teams-aware component. Detect Teams Manifest References SPFx for Teams
Read more →Terraform with Azure: Complete Module Development
Modules are the building blocks of reusable Terraform infrastructure. A good module encapsulates complexity and enforces company standards (naming conventions, tagging, security). This guide builds an Azure VNET module with subnets and security groups. Directory Structure Using `for_each` for Subnets Key Takeaways Keep modules focused and single-responsibility. Always define `terraform` block with version constraints. Pin […]
Read more →Azure Functions Durable Entities: Stateful Serverless
Serverless is typically stateless. Durable Functions changed that with orchestrations. Now, “Durable Entities” brings the Actor Model (similar to Akka or Orleans) to Azure Functions, allowing you to define small, stateful objects that persist across calls. Defining an Entity Signaling an Entity Entities are addressed by ID. Signals are one-way (fire and forget) writes. Key […]
Read more →Cosmos DB: Cost Optimization Strategies
Azure Cosmos DB is powerful but can be expensive if misconfigured. The “Request Unit” (RU) model abstracts hardware, but understanding it is key to cost control. This guide covers partition key selection, indexing policies, and the new Autoscale throughput. Understanding Request Units (RU) 1 RU = 1 Read of a 1KB document by ID. Queries […]
Read more →