ASP.NET Core

Tales from the .NET Migration Trenches - Turning Off the Lights

Posts in this series: * Intro * Cataloging * Empty Proxy * Shared Library * Our First Controller * Migrating Initial Business Logic * Our First Views * Session State * Hangfire * Authentication * Middleware * Turning Off the Lights In the last post, we looked at migrating our middleware, which we tackle in an as-needed basis. When a controller needs

ASP.NET Core

Tales from the .NET Migration Trenches - Middleware

Posts in this series: * Intro * Cataloging * Empty Proxy * Shared Library * Our First Controller * Migrating Initial Business Logic * Our First Views * Session State * Hangfire * Authentication * Middleware * Turning Off the Lights In the last post, we looked at tackling probably the most important pieces of middleware - authentication. But many ASP.NET

ASP.NET Core

Tales from the .NET Migration Trenches - Authentication

Posts in this series: * Intro * Cataloging * Empty Proxy * Shared Library * Our First Controller * Migrating Initial Business Logic * Our First Views * Session State * Hangfire * Authentication * Middleware * Turning Off the Lights Of all the topics in .NET migration, authentication, like always, is the one that is most characterized by "It Depends&

ASP.NET Core

Tales from the .NET Migration Trenches - Hangfire

Posts in this series: * Intro * Cataloging * Empty Proxy * Shared Library * Our First Controller * Migrating Initial Business Logic * Our First Views * Session State * Hangfire * Authentication * Middleware * Turning Off the Lights In the last post, we encountered our first instance of shared runtime data between our different ASP.NET 4.8 and

ASP.NET Core

Tales from the .NET Migration Trenches - Session State

Posts in this series: * Intro * Cataloging * Empty Proxy * Shared Library * Our First Controller * Migrating Initial Business Logic * Our First Views * Session State * Hangfire * Authentication * Middleware * Turning Off the Lights Believe it or not, things have been relatively simple so far. In the next few posts, we'll get to

ASP.NET Core

Tales from the .NET Migration Trenches - Our First Views

Posts in this series: * Intro * Cataloging * Empty Proxy * Shared Library * Our First Controller * Migrating Initial Business Logic * Our First Views * Session State * Hangfire * Authentication * Middleware * Turning Off the Lights Back when we looked at our first controller, we tried out the "automatic" migration and the controllers migrated just

ASP.NET Core

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 * Our First Views * Session State * Hangfire * Authentication * Middleware * Turning Off the Lights In the last post we moved just our initial controller over but none of the code used by the controller yet.

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 * Our First Views * Session State * Hangfire * Authentication * Middleware * Turning Off the Lights In the last post, we prepped for our first set of pages migrated by extracting common logic into a shared library.

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 * Our First Views * Session State * Hangfire * Authentication * Middleware * Turning Off the Lights In the previous post, we established a beachhead with a completely empty proxy application to prepare for migrating controllers incrementally all

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 * Our First Views * Session State * Hangfire * Authentication * Middleware * Turning Off the Lights In the previous post, we looked at techniques for determining the size and scope of our .NET migration effort, as well

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 * Our First Views * Session State * Hangfire * Authentication * Middleware * Turning Off the Lights When I talk with folks about modernization, inevitably the question comes up "OK but how much is it going to

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 * Our First Views * Session State * Hangfire * Authentication * Middleware * Turning Off the Lights Over the past year or so I've been part of a large-ish modernization effort, both migrating from .NET 4.

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]

Dependency Injection

Choosing a ServiceLifetime

A subtle source of errors and less-than-subtle source of frustration is understanding and using service lifetimes appropriately with .NET Core dependency injection. Service lifetimes, while complicated on the surface, can help developers that need to share state across different lifetimes of an application. Typically, a long-running application has three service

Architecture

Vertical Slice Example Updated to .NET 5

With the release of .NET 5, I wanted to update my Vertical Slice code example (Contoso University) to .NET 5, as well as leverage all the C# 9 goodness. The migration itself was very simple, but updating the dependencies along the way proved to be a bit more of a

NServiceBus

End-to-End Integration Testing with NServiceBus

One of the interesting side effects of adding diagnostic events to infrastructure is that you can now "listen in" to what's going on in your applications for black box testing. This can be especially useful in scenarios where you're building on top of a

Microservices

Building End-to-End Diagnostics and Tracing: An Intro

Posts in this series: * An Intro * Trace Context * Diagnostic Events * OpenTelemetry Integration * Activity and Span Correlation * Visualization with Exporters * User-Defined Context with Correlation Context * ActivitySource and OpenTelemetry 1.0 Source Code As microservices introduced (forced) highly complex distributed systems into organizations, the tools required to operate these architectures needed to

OSS

Contoso University Examples with CQRS, MediatR, AutoMapper and more

I was a bit surprised yesterday to see Scott Hanselman's post on my Contoso University sample app. That application basically takes the traditional Contoso University sample applications (of which there have been many), and try to adapt it to how our "normal" ASP.NET applications are

ASP.NET Core

Migrating Contoso University Example to Razor Pages

A coworker noticed that it looked like Razor Pages were the new "recommended" way of building server-side rendered web applications in ASP.NET Core 2.0. I hadn't paid much attention because at first glance they looked like Web Forms. However, that's not the