Jimmy Bogard - Jimmy Bogard

Tales from the .NET Migration Trenches - Migrating Initial Business Logic

Posts in this series: * Intro * Cataloging * Empty Proxy * Shared Library * Our First Controller * Migrating Initial Business Logic In the last post we moved just our initial controller over but none of the code used by the controller yet. The first "feature" migrated will be this controller and its vertical slice

ASP.NET Core

Tales from the .NET Migration Trenches - Our First Controller

Posts in this series: * Intro * Cataloging * Empty Proxy * Shared Library * Our First Controller * Migrating Initial Business Logic In the last post, we prepped for our first set of pages migrated by extracting common logic into a shared library. With that in place, we're now ready to migrate our first controller.

ASP.NET Core

Tales from the .NET Migration Trenches - Shared Library

Posts in this series: * Intro * Cataloging * Empty Proxy * Shared Library * Our First Controller * Migrating Initial Business Logic In the previous post, we established a beachhead with a completely empty proxy application to prepare for migrating controllers incrementally all the way to production. There's still one more step we need to

ASP.NET Core

Tales from the .NET Migration Trenches - Empty Proxy

Posts in this series: * Intro * Cataloging * Empty Proxy * Shared Library * Our First Controller * Migrating Initial Business Logic In the previous post, we looked at techniques for determining the size and scope of our .NET migration effort, as well as clarifying what our goals should be. But before we start migrating

ASP.NET Core

Tales from the .NET Migration Trenches - Cataloging

Posts in this series: * Intro * Cataloging * Empty Proxy * Shared Library * Our First Controller * Migrating Initial Business Logic When I talk with folks about modernization, inevitably the question comes up "OK but how much is it going to cost?" This is never an easy question but first we need to understand

ASP.NET Core

Tales from the .NET Migration Trenches - Intro

Posts in this series: * Intro * Cataloging * Empty Proxy * Shared Library * Our First Controller * Migrating Initial Business Logic Over the past year or so I've been part of a large-ish modernization effort, both migrating from .NET 4.8 to .NET 6 (the latest LTS at the time) and from an on-premise

Microservices

A Service Boundary Homework Problem

I guess it was inevitable, but quite often I see homework problems on r/microservices seemingly assigned in some intro CS class. Peculiarities of that aside, they can be quite fun to work through as thought experiments. One recent one came up: Hi, I am working on a school app.

MediatR

MediatR 12.1 Released

This release removes all scanning around behaviors, stream behaviors, and pre/post processors. That proved too problematic so you MUST register each of these explicitly with the appropriate registration methods inside AddMediatR. This also ensures that the order of behaviors and pre/post processors reflects the explicit order of registration.

MediatR

MediatR 12.0 Released

This is a pretty big release, with a number of breaking changes. * Release Notes * Migration Guide Breaking changes include: * Depending directly on IServiceProvider to resolve services * Making "void" request handlers return Task instead of Unit * IRequest does not inherit IRequest instead IBaseRequest * Consolidating the MediatR.Extensions.Microsoft.DependencyInjection package

Azure

Securing Web APIs with Azure AD: Connecting Azure Clients

Posts in this series: * A Case Study * Designing Authentication Schemes * Authorizing Client Applications * Building the Server * Enabling Local Development * Connecting External Clients * Connecting Azure Clients Full example In the last post, we used OAuth 2.0 Client Credentials flow to connect an external client (modeling our on-prem scenario). We can

Azure

Securing Web APIs with Azure AD: Connecting External Clients

Posts in this series: * A Case Study * Designing Authentication Schemes * Authorizing Client Applications * Building the Server * Enabling Local Development * Connecting External Clients * Connecting Azure Clients Full example In the previous post, we looked at enabling local development by creating an Azure AD Group, assigning our user (me) to that group,

Azure

Securing Web APIs with Azure AD: Enabling Local Development

Posts in this series: * A Case Study * Designing Authentication Schemes * Authorizing Client Applications * Building the Server * Enabling Local Development * Connecting External Clients * Connecting Azure Clients Full example In the last post, we looked at creating the server application and corresponding Azure resources to secure it. If we try to test

Azure

Securing Web APIs with Azure AD: Building the Server

Posts in this series: * A Case Study * Designing Authentication Schemes * Authorizing Client Applications * Building the Server * Enabling Local Development * Connecting External Clients * Connecting Azure Clients Full example In the last couple of posts, we looked at authentication and authorization options and picked some strategies for each. With those pieces chosen,

Azure

Securing Web APIs with Azure AD: Authorizing Client Applications

Posts in this series: * A Case Study * Designing Authentication Schemes * Authorizing Client Applications * Building the Server * Enabling Local Development * Connecting External Clients * Connecting Azure Clients Full example In our last post, we chose the OAuth 2.0 Client Credentials grant scheme to authenticate our APIs and daemon applications: Once we

Azure

Securing Web APIs with Azure AD: Designing Authentication Schemes

Posts in this series: * A Case Study * Designing Authentication Schemes * Authorizing Client Applications * Building the Server * Enabling Local Development * Connecting External Clients * Connecting Azure Clients Full example In our last post, I walked through my real-world scenario of needing to follow Zero Trust principles in securing microservice-based APIs inside (and

Azure

Securing Web APIs with Azure AD: A Case Study

Posts in this series: * A Case Study * Designing Authentication Schemes * Authorizing Client Applications * Building the Server * Enabling Local Development * Connecting External Clients * Connecting Azure Clients Full example Recently, I was on a project where the company had a big push towards a "Zero Trust" security model. This concept was new

Azure

Building Messaging Endpoints in Azure: Container Apps

Posts in this series: * Evaluating the Landscape * A Generic Host * Azure WebJobs * Azure Container Instances * Azure Functions * Azure Container Apps Well it's been a while since we visited this! I intended to follow up with a post on Kubernetes but to be honest, Kubernetes is far too complicated to get

MediatR

You Probably Don't Need to Worry About MediatR

I've been pointed at this post from various sources, and I thought I'd take the time to address the criticisms one by one. Not because I personally care too much, MediatR evolved over many years to solve the problems my teams faced, but since others seem to care, here we

AutoMapper

Dissecting AutoMapper Programming Horror

My AutoMapper search alerts brought me this gem this morning: Hey... let's use automapper to generate passwords. This post illustrates basically all the wrong reasons to use AutoMapper. Here's the code minus the unimportant bits: public class RequestProfile : Profile { public RequestProfile() { CreateMap() .ForMember(d => d.Address, e => e.

NServiceBus

NServiceBus.Extensions.Diagnostics 2.1 Released

From the previous post on building NServiceBus metrics, I've pushed a new version of the NServiceBus.Extensions.Diagnostics and OpenTelemetry packages: * NServiceBus.Extensions.Diagnostics NuGet * NServiceBus.Extensions.Diagnostics ReadMe * NServiceBus.Extensions.Diagnostics.OpenTelemetry NuGet * NServiceBus.Extensions.Diagnostics.OpenTelemetry ReadMe As before, the OpenTelemetry packages are just small wrappers around TracerBuilderProvider.

Distributed Systems

Building NServiceBus Metrics with OpenTelemetry and System.Diagnostics.Metrics

The release of System.Diagnostics.DiagnosticSource version 6.0 a few months back brought something entirely new to the library - support for OpenTelemetry Metrics. Since this package releases out-of-band from the .NET 6 SDK, it also means you can use these new metrics APIs in any application targeting .NET

Microservices

Activity Enrichment in ASP.NET Core 6.0

Waaaaay back in the ASP.NET Core 3.1 days, I wrote about increasing the cardinality of traces using Tags and Baggage. You could write code in your controllers, filters, or application code to be able to add custom information to traces to help find these traces more effectively: [HttpGet]

NServiceBus.Extensions.Diagnostics 2.0 Released

Last week I pushed out the 2.0 release of NServiceBus.Extensions.Diagnostics package: * NuGet * Release Notes And related packages: * NServiceBus.Extensions.Diagnostics.OpenTelemetry * NServiceBus.Extensions.IntegrationTesting The biggest feature change was to allow behaviors to be able to modify the original activity started by accessing an ICurrentActivity from the

MediatR

Diagnosing and Fixing MediatR Container Issues

An issue I see come up quite frequently, much to the chagrin of DI container maintainers, are problems of complex generics edge cases and how they come up in MediatR. In fact, more than one container author has demanded some kind of recompense for the questions received and issues opened

OSS

Respawn 5.0 Released

I pushed out a new version of Respawn today: * Release notes * NuGet Enjoy!