From the Backlog to the Build Log

A .NET 11 Upgrade and the Agent View: November 13 - November 19, 2026

What I Worked On

A week after I moved everything to the 10.0.14 packages, I gave DevNitro Microsoft's migration guide for ASP.NET Core 10 to 11 and asked for a .NET 11 upgrade of the whole solution. The Visual Studio extension had to stay on .NET 8. That session ran about 50 minutes on Friday afternoon. Upgrades like this are where I want Intelligent Engineering to pay off, because the AI can do most of the editing while the build and the tests show what it missed.

Later in the week I upgraded GCT, the GlobalCove packages DevNitro and my apps build on, so it supports .NET 11 apps alongside .NET 10, and then got DevNitro building against it. I also added an Agent View to the DevNitro CLI for reading a sub-agent's conversation while it runs.

What the AI Did Well

I'd started the upgrade myself with a find and replace on the csproj files, and I told DevNitro that was all I'd done. It found what I missed. Ten libraries that build for both .NET 10 and .NET 8 use the plural <TargetFrameworks>, so my search skipped them. Two BlueprintUpgradeTests replace net10.0 in a test string, and after my edit that string no longer contained it, so both tests passed without testing anything. The check that scans the build output before a deploy still pointed at a net10.0 folder, where it would have found nothing to scan and passed.

The 11.x packages ship nothing for .NET 8, so DevNitro split Directory.Packages.props by target framework. The extension's .NET 8 builds stay on 10.0.x, and everything else moves to 11. All 3,471 unit tests passed.

Of the 2,101 integration tests, 79 failed, and DevNitro didn't blame .NET 11 or my machine until it knew which. It grouped the failures by error message and found 168 refused connections to Azurite, the local Azure storage emulator. Its first two tries at starting Azurite failed, because the shim Visual Studio installs passes along only its first argument. Fortunately, once DevNitro ran azurite.exe directly, all 132 tests in the failing classes passed. The other five run Docker against an image built before the change, so it listed them as not verified.

For the Agent View, I asked for Ctrl+A to cycle through sub-agents and told DevNitro to check how the open-source oh-my-pi agent handles it. DevNitro pointed out that Ctrl+A already jumps to the start of the line in the CLI's editor, so DevNitro uses Alt+A now. It also found the CLI had been throwing away sub-agent text, because it streamed only the main agent's. Now the CLI keeps each sub-agent's messages, tool calls, and errors, and Alt+A shows them live, drawn with the same code as the main chat.

What Needed Correction

The corrections were part of the upgrade itself: GCT first, then DevNitro on top of it. DevNitro builds on GCT, so GCT had to support .NET 11 apps while still serving my .NET 10 apps. My first GCT commit Thursday night added net11.0 to GlobalCove.Startup only. The shared test fixtures package still targeted only .NET 10 and listed the .NET 10 OpenAPI packages as direct dependencies. DevNitro's test projects reference those fixtures directly, so NuGet's nearest-wins rule picked that pin over Startup's >= 11.0.0, and DevNitro's restore failed with NU1608. DevNitro multi-targeted the fixtures, repacked 2.4.0, and cleared the old 2.4.0 from the NuGet cache, since a repack under the same version number doesn't replace the cached copy. I folded that into the GCT commit at 8:56 that night.

Then DevNitro moved to GCT 2.4.0. After that version bump, Directory.Packages.props had plain 11.0.0 entries where the per-framework split had been, so the extension's .NET 8 builds were on packages with nothing for .NET 8. DevNitro restored the split with the .NET 8 side on 10.0.15 and added a comment telling whoever bumps versions next not to merge the groups. That fix isn't committed yet.

What Shipped

The .NET 11 upgrade went into DevNitro on Tuesday and GCT 2.4.0 on Thursday. GCT also dropped a validation source generator whose code relied on experimental .NET 10 types that .NET 11 removed, which made GlobalCove.Startup throw TypeLoadException in .NET 11 apps. A new test fails if that generated code comes back.

On the HowdyChad site, the contact form now saves what its spam checks catch to a spam folder instead of dropping it, and deletes that spam after 30 days.

On YouTube I published "How Microsoft 365 Took Itself Down for Almost a Day" on Saturday and "4 Cheap AI Models Kept Falling in the Lava. One Change Fixed It." on Wednesday.

In the Studio

Two of this week's studio videos were about security news from the same few days, and two agents built them at the same time Wednesday night. "Java4Shell (Shut the Door)" covers CVE-2026-114938, the OpenJDK Base64 bug disclosed November 17. Every headline on screen uses the source's own words, written down with its date, and the video never shows the real trigger input. "The Page Looked Fine" covers the Optimizely attack, where a script that big sites already trusted carried malicious JavaScript. The first version was a 3D world of web pages that I found boring, so I asked the agent to give me a couple of different looks, and it gave me three. I picked the third look it gave, a 16-bit game.

I approved both around 2:20 Thursday morning and went to bed. While I slept, DevNitro rendered the 4K finals and a 9:16 Short of each, and Thursday I posted both videos and both Shorts at the same time.

They came together much faster, and with much less supervision, than the two like them before. "Make One More Call," about the $129 million deepfake robbery, went live November 12 and took 15 notes from me across about 12 hours. "Everybody Hit Refresh," about the Microsoft 365 outage, went live November 14 and took 8. Java4Shell took 4, counting my first ask and the approval, and The Page Looked Fine took 7, three of them about its look. Each was ready to approve less than five hours after I started it.

The difference is my AI video studio, which carries the rules from earlier videos into each new one. I never meant for DevNitro to make music videos, but as the models underneath it get better, DevNitro keeps getting better with them.

The Numbers

Category Hours
Content 18h 42m
Business 11h 40m
Product / Features 4h 2m
Testing 2h 41m
Total 37h 5m

Product work came to 6h 43m, down from 11h 46m last week, for a framework upgrade across DevNitro and GCT. Go-to-market rose from 7h 39m to 11h 40m. Studio videos took 12h 48m of the content time, more than I meant to spend.

Where This Fits in Intelligent Engineering

.NET 11 added Blazor analyzers that found 208 issues in existing DevNitro code, 165 of them unneeded StateHasChanged() calls. Fixing 64 files of UI code inside the upgrade would have made both changes hard to review, and switching the rules off would have hidden them. So DevNitro let the three rules through as warnings, wrote in Directory.Build.props why and that it's temporary, and opened an issue for each rule. In Intelligent Engineering, work comes from the backlog, including cleanup you choose to put off. A deferred fix with an issue behind it is one someone can see, assign, and close.


That's the week: DevNitro did the .NET 11 upgrade in about 50 minutes, and by Thursday night GCT and DevNitro both built on .NET 11. If you want to see DevNitro in action, grab a spot on my calendar and I'll give you the tour. If you want help getting more out of the AI tools your team already uses, I can help with that too.