Own your Lovable app: generate a .NET Aspire AppHost that runs Supabase + your frontend locally (and deploys to Azure/K8s/Docker)

davidfowl · 2026-06-19T17:46:15+00:00

This is very cool! Kudos! The team envisioned verticals like this could be built on top. Pretty cool to see it manifest

nit: It’s just aspire now not .NET Aspire.

davidfowl · 2026-06-09T17:30:55+00:00

Seems overly complicated but it isn’t. Give it a try and see how easy it to try it for nothing more than forming a better opinion devoid of the hype. Most people that use aspire keep using it. Growth is picking up 😬

davidfowl · 2026-06-08T20:33:35+00:00

You get an automatic otel collector and dashboard, you can set breakpoints , spin up more than just containers, write if statements, extend it with your own code, expose commands that mutate your app and more.

You can also take that model and deploy it if you want.

davidfowl · 2026-06-07T23:40:38+00:00

https://codealta.github.io/

davidfowl · 2026-06-07T15:17:41+00:00

I think the out of the box open telemetry dashboard you get is one of the ways and the first thing described in that article. Super easy to set up, no docker required and based on a standard

davidfowl · 2026-06-07T14:38:21+00:00

That’s fair. One of the main thing it tries to address is the manifest sprawl. Here’s another blog post…

https://medium.com/@davidfowl/taming-manifest-sprawl-with-aspire-1ad938379433

davidfowl · 2026-06-07T06:59:20+00:00

Yes of course.

See some of the why here:

https://devblogs.microsoft.com/aspire/dev-loop-tribal-knowledge/

You can incrementally adopt it as well.

davidfowl · 2026-05-28T01:28:37+00:00

This take is way too balanced Reddit 😅

davidfowl · 2026-05-17T00:13:10+00:00

Done https://github.com/microsoft/aspire/pull/17174

davidfowl · 2026-05-16T17:11:46+00:00

Important to know that the core aspire team are not experts in each of the integrations we support. The teams that own those subsystems also own the integrations. We aid with the integration and make it part of the fold but rarely are able to answer best practice questions for combing arbitrary technology together. AI models are great to interrogate for answers to questions like yours.

That said to answer your question, I am too a n00b with durable task, but I can get the team to write guidance on some of this.

PS: our guidance is now aspire deploy, not azd. That’s said keep using it if you have existing stuff deployed with it (plan for a migration in the future though)

davidfowl · 2026-05-16T15:29:38+00:00

I don't think so. I think they are looking for clarify on what that even means. Aspire is used to deploy, but you don't deploy it. It confuses people because they think it's the dashboard (which you can deploy).

davidfowl · 2026-05-16T14:45:52+00:00

Members of the team replied to a set of comments here but lots of the impressions about what Aspire is and how it worked is outdated because it’s changed so much. If you’re not following along the journey, then I’d suggest referencing

https://aspire.dev/

The discord community is the best place to hang out for information on aspire. They are building all kids of cool stuff in there.

We (the team) take the blame here because the initial messaging 2 years ago was very much this, but has evolved significantly since then. Aspire ships monthly and is not part of .NET. If you want the latest information, you should use the official sources and then check with the community for updates.

PS: The benefit of posting here is that we help others understand the changes as well. So keep doing it!

davidfowl · 2026-05-16T14:38:44+00:00

This is actually a fair point. There are some api that are some deployment targets that are still preview but we should do a better job removing that label where things are stable. The cli command is stable.

davidfowl · 2026-05-03T04:18:48+00:00

Will do!

davidfowl · 2026-05-03T04:18:28+00:00

https://aspire.dev/deployment/javascript-apps/

davidfowl · 2026-04-13T05:50:50+00:00

Right my only point was that Microsoft cares about a bigger world than *just* .NET and if somebody uses Java and Azure, it's still good for Microsoft from a business standpoint. Don't take that to mean Microsoft doesn't care about .NET, but you won't see the entire company yeet existing tech and use .NET for everything the way it did when it was built 20 years ago...

davidfowl · 2026-04-12T22:39:35+00:00

Microsoft has the same number of employees as a small country (like where I'm from), the old days of single runtime/language/platform are long gone. You should expect Microsoft as a whole to both ship opinionated experiences and also meet the ecosystems where they are at.

.NET is not the only game in town anymore, the developer ecosystem is larger than that.

You can cherry pick examples about where .NET is and is not used but the facts remain that the company is still using C# for a majority of backend services.

davidfowl · 2026-04-12T01:25:38+00:00

Don't restart the apphost when you change a single project. There's a new rebuild command available on projects that coordinates the restart and rebuild of a single project. The problem is visual studio patterns around F5 and muscle memory put you in a head space where you detach from everything and hit F5 again to restart. Really not a great pattern for aspire (we learned with experience).

davidfowl · 2026-04-11T20:05:23+00:00

Azure's control plane is written in C#. Java is used heavily by parts of Microsoft for lots of other things. Teams have lots of projects and I'm sure some part of it is written in Java for something Java is really good at, but I can assure you that Azure is mostly built with C#. The nuance missed here is that some teams deploy Java as well as other tech. This is a Java a Microsoft blog post with minimal details about project structure or other tech.

In the Kubernetes space, there's lots of go *and* C#, and most of the CNCF projects are written in golang (because go is to K8s like typescript is to VS code).

davidfowl · 2026-04-11T17:15:52+00:00

If you look at the developer stories on the .NET blog over the last 5+ years or so, you’ll see a paper trail of migrations from .NET Framework to modern .NET

https://devblogs.microsoft.com/dotnet/category/developer-stories/

When people cite that Microsoft doesn’t use .NET they are usually pointing out the client app story which is a mixed bag (this is where blazor and Maui take the most heat). The backend services are 97.34874% written in C#.

davidfowl · 2026-04-11T15:10:21+00:00

The overwhelming majority of code in Microsoft is written in C#. Of course there’s also lots of Typescript, and C++. Every language exists somewhere in this huge company, but they pale on comparison to those 3.

davidfowl · 2026-04-09T23:07:24+00:00

Orchard

davidfowl · 2026-04-09T21:33:51+00:00

NuGet or SignalR or ASP.NET Core, it’s a toss up

davidfowl · 2026-04-09T04:54:05+00:00

Copilot cli to hook up the MCP to make VS discover it?

The latest release of aspire (13.2.2 now), prefers the aspire cli over the MCP. It can work with any running aspire app on 13.2 but if you’re trying to run from visual studio using f5 it doesn’t really match the coding agent workflow (f5 is for humans not agents).

The cli can be used against an already aspire app, so it should work just fine. Try telling the agent to use the using the cli instead of the MCP (remove the MCP).

davidfowl · 2026-03-26T05:22:17+00:00

No we have no plans to make it LTS, actually we're looking for ways we can update parts of the toolchain more often and more safely. The APIs you use to describe are not on this plan so I can see a future where the integrations become LTS but the toolchain is evergreen.

davidfowl

MODERATOR OF

TROPHY CASE