C#, ASP.NET, .NET Core

Production .NET and Full-Stack Delivery

I have delivered full-stack production applications using the shared engineering resources I developed. My C# work spans .NET 8, 9, and 10, combining hands-on implementation with reusable architecture, integration, testing, and delivery practices.

My shared application foundations bring together .NET 10 ASP.NET Core APIs, Next.js and React clients, shared .NET libraries, and Aspire orchestration. The broader starter includes authentication integration, Redis caching, feature management, configuration validation, and configurable telemetry. A focused marketing starter applies the same engineering discipline to a smaller application boundary.

As an ICS (Information Communication Services) employee of The Church of Jesus Christ of Latter-day Saints, I have a direct assignment supporting CES (Church Education Services) applications and services, including BYU-Pathway and Seminaries and Institutes. This work connects software delivery with the architectural needs of education systems.

Explore my architecture and production-delivery contributions.

Reusable .NET QA Framework

I was the primary developer of a reusable .NET QA automation framework, carrying out nearly all of its development. Its modular architecture supports API, browser, data, and container-backed testing through shared configuration, dependency injection, logging, and fixture lifecycles.

The framework integrates NUnit, Selenium, Playwright, reusable API clients and page models, diagnostic capture, redaction, schema validation, and screenshot evidence. Isolated validation environments use controlled resource lifecycles, dynamic endpoints, API mocks, and OAuth/OIDC test flows.

Explore the framework and quality-engineering work.

Modern .NET Solution Design

My strongest current technical area is the Microsoft stack around C# and .NET. Recent public work reflects modern solution structure, standardized repository setup, layered applications, diagnostics, container-backed local development, and reusable starter patterns intended to help teams build new software faster with better consistency.

Application Types and Platforms

My public repositories include web applications, APIs, Blazor applications, Azure-oriented starter work, console tooling, and engineering support projects. DotNetProjectStartup includes multiple application shapes and .NET 9 solution organization, while Blazor-Chat-App demonstrates .NET 10, Blazor, Aspire AppHost, Redis output caching, Entity Framework Core 10, and SQL Server.

Architecture, Observability, and Maintainability

A recurring theme in my .NET work is engineering discipline: dependency injection, structured configuration, local environment repeatability, Docker-backed dependencies, test project separation, OpenTelemetry, and Seq-oriented diagnostics. I care about code that is supportable by a team, not just code that works once on a single machine.

Leadership Context

My work history adds the enterprise side of this skill set: mentoring engineers, setting code standards, reviewing solutions, helping teams deliver in Azure DevOps environments, and stepping in hands-on when architecture or delivery needs help.