Mitch Denny
@mitchdenny.dev
Helping make distributed application better for .NET developers with .NET Aspire and ASP.NET Core.
What Is the Lego like sticker?
November 13, 2025 at 6:33 AM
What Is the Lego like sticker?
Once we got comfortable with the number - we started dropping hints. Even some members of the team where like "wait, you're serious!?!?"
November 12, 2025 at 12:53 AM
Once we got comfortable with the number - we started dropping hints. Even some members of the team where like "wait, you're serious!?!?"
We can't confirm what the next major of Aspire will be - will probably depend on just how much whimsy the team has on the day :)
November 12, 2025 at 12:51 AM
We can't confirm what the next major of Aspire will be - will probably depend on just how much whimsy the team has on the day :)
Then when we realized that we would be shipping 13 around the time of Halloween that pretty much just locked it in.
November 12, 2025 at 12:51 AM
Then when we realized that we would be shipping 13 around the time of Halloween that pretty much just locked it in.
@maddymontaquila.net and @damianedwards.com started running it up the flagpole and no one had objections (other than a few raised eyebrows) - so its kind of stuck.
November 12, 2025 at 12:51 AM
@maddymontaquila.net and @damianedwards.com started running it up the flagpole and no one had objections (other than a few raised eyebrows) - so its kind of stuck.
Truth is, we joked about picking 13 because it's the next prime number after 11. We all chuckled and thought that was absurd - but also totally on-brand for Aspire which is trying to push the envelope a bit.
November 12, 2025 at 12:51 AM
Truth is, we joked about picking 13 because it's the next prime number after 11. We all chuckled and thought that was absurd - but also totally on-brand for Aspire which is trying to push the envelope a bit.
We wanted to put some distance between .NET 10 and our next version. So, we could do 11, but then .NET 11 will be shipping previews soon too.
November 12, 2025 at 12:51 AM
We wanted to put some distance between .NET 10 and our next version. So, we could do 11, but then .NET 11 will be shipping previews soon too.
Well @maddymontaquila.net wanted to burn the world down and reversion from 9.5.x to 1.0 with the rebrand from .NET Aspire to Aspire. Once we explored that option and decided that we didn't want devs with pitchforks at our front door we knew we had to roll forward.
November 12, 2025 at 12:51 AM
Well @maddymontaquila.net wanted to burn the world down and reversion from 9.5.x to 1.0 with the rebrand from .NET Aspire to Aspire. Once we explored that option and decided that we didn't want devs with pitchforks at our front door we knew we had to roll forward.
With Aspire you can do AddOllama(...) and then hook that up to your apps pretty easily: learn.microsoft.com/en-us/dotnet...
Aspire Community Toolkit Ollama integration - Aspire
Learn how to use the Aspire Ollama hosting and client integration to host Ollama models using the Ollama container and accessing it via the OllamaSharp client.
learn.microsoft.com
November 11, 2025 at 11:15 PM
With Aspire you can do AddOllama(...) and then hook that up to your apps pretty easily: learn.microsoft.com/en-us/dotnet...
Reliability in electronics is a lie.
November 9, 2025 at 11:20 PM
Reliability in electronics is a lie.
DNS is global. SWA is hosted in West US 2 :) Its only them US bits that are flipping :)
November 9, 2025 at 11:06 PM
DNS is global. SWA is hosted in West US 2 :) Its only them US bits that are flipping :)
Need to check. Have some local connectivity issues right now. At my sons chess tournament this morning and the radio spectrum appears to be getting g hammered
November 9, 2025 at 11:04 PM
Need to check. Have some local connectivity issues right now. At my sons chess tournament this morning and the radio spectrum appears to be getting g hammered
Maybe. Although if that was the case I would expect that @damianedwards.com would be getting consistent failures because he wouldn't be getting a different resolver for each individual request (the request would be cached).
More likely some hidden AFD state somewhere. Should resolve itself in time.
More likely some hidden AFD state somewhere. Should resolve itself in time.
November 9, 2025 at 11:01 PM
Maybe. Although if that was the case I would expect that @damianedwards.com would be getting consistent failures because he wouldn't be getting a different resolver for each individual request (the request would be cached).
More likely some hidden AFD state somewhere. Should resolve itself in time.
More likely some hidden AFD state somewhere. Should resolve itself in time.
Maybe. Although if that was the case I would expect that @damianedwards.com would be getting consistent failures because he wouldn't be getting a different resolver for each individual request (the request would be cached).
More likely some hidden AFD state somewhere. Should resolve itself in time.
More likely some hidden AFD state somewhere. Should resolve itself in time.
November 9, 2025 at 10:57 PM
Maybe. Although if that was the case I would expect that @damianedwards.com would be getting consistent failures because he wouldn't be getting a different resolver for each individual request (the request would be cached).
More likely some hidden AFD state somewhere. Should resolve itself in time.
More likely some hidden AFD state somewhere. Should resolve itself in time.
I’m using a feature of Azure DNS which allows you to point an apex domain to an azure resource as opposed to a static IP.
But I think I may have exposed a bug in either SWA or AzDNS.
I initially had the DNS pointed to another SWA with the same name (but different resource group).
But I think I may have exposed a bug in either SWA or AzDNS.
I initially had the DNS pointed to another SWA with the same name (but different resource group).
November 9, 2025 at 10:45 PM
I’m using a feature of Azure DNS which allows you to point an apex domain to an azure resource as opposed to a static IP.
But I think I may have exposed a bug in either SWA or AzDNS.
I initially had the DNS pointed to another SWA with the same name (but different resource group).
But I think I may have exposed a bug in either SWA or AzDNS.
I initially had the DNS pointed to another SWA with the same name (but different resource group).
I did nothing. I suspect it was just some localized issue.
November 9, 2025 at 10:30 PM
I did nothing. I suspect it was just some localized issue.
Azure Static web apps probably depends on AFD transparently. But websites brings content publishing and even mechanisms to build frontends from source.
November 9, 2025 at 10:29 PM
Azure Static web apps probably depends on AFD transparently. But websites brings content publishing and even mechanisms to build frontends from source.
I suspect it’s a CDN issue on Azure Static Web Apps
November 9, 2025 at 10:20 PM
I suspect it’s a CDN issue on Azure Static Web Apps
The background is a little graph + gravity simulation. Vibe coded obviously.
November 9, 2025 at 10:09 PM
The background is a little graph + gravity simulation. Vibe coded obviously.
Ok thanks for the heads up. Will investigate
November 9, 2025 at 10:07 PM
Ok thanks for the heads up. Will investigate
I’ve been thinking about getting myself one of these framework desktops. I like them for a bunch of reasons. I wonder if you could replace the titles with little LED panels that are interlinked and display system stats etc.
November 9, 2025 at 10:06 PM
I’ve been thinking about getting myself one of these framework desktops. I like them for a bunch of reasons. I wonder if you could replace the titles with little LED panels that are interlinked and display system stats etc.
Really??? I just clicked on the link and it worked. What do the request / response headers look like.
November 9, 2025 at 10:03 PM
Really??? I just clicked on the link and it worked. What do the request / response headers look like.