My First look at .NET Aspire. What's with the Hype?

Follow along as I take a look at .NET Aspire. I've been hearing a lot about it, but is it worth the hype? Good question! I haven't used it or really read much about it in detail so here's my first look and first impressions.

🔗 EventStoreDB

💥 Join this channel to get access to a private Discord Server and any source code in my videos.

🔥 Join via Patreon

✔️ Join via YouTube

[marna_li]

I recently converted my solution to Aspire - 20+ projects. I'm glad that I had my own service defaults. But it was so tedious to do.
I had been using Tye before, and I liked it, but switched to Docker Compose when that experiment ended. I kind of miss the YAML now.

[AlexanderZeitler]

This video is my first look at Aspire and I think I can ignore it for while (maybe forever)

[qbiiped]

I've been playing around with it and I think it has a lot of promise but it falls just short right now. Specifically when it comes to testing, I'd like to use the same AppHost configuration to spin up instances of my dependencies for integration tests and to configure test services like you can with WAF. It feels very all-or-nothing right now but hopefully, it'll be more flexible in the future.

I've been using a combination of docker/compose/makefile to simplify local setup and I don't think I can walk away from it yet. However I might use both Aspire and my current tooling together in my next greenfield project to get a better sense.

[mdev]

Just got the time to try aspire and can say that it’s really nice! Have moved some of my small projects to it from docker compose, and it’s super convenient since I can debug normally both front and back end in parallel, plus the dependency injection that aspire offers is also pretty nice 👍

[Rick]

The standalone aspire dashboard is the easiest way to see Opentelemetry data locally. Using it daily already.

Not sure about the rest of aspire. Feels like there's potential here but also feels like this might turn into yet another excuse to do microservices in the wrong context.

[awright]

Still need to look at this more, my gut reactions to this were a concern about centralized configuration and not quite understanding how or if various teams working on parts of a system would or could use this. It feels like a solition in search of a real problem. Really feels like DevDiv is being asked to try hard to influence devs to use more azure instead of solving real problems. Apologies for the sinicism, I've just been doing this too long. Maybe it will be the next big thing and i'll see the light, as of now though I'm not convinced.

[dustedcodes]

What's with the Hype?

There is no hype. It's literally just Fowler tweeting about his newest framework pet project because he wants to make it a thing.

[samuelnettey]

Isn't this supposed to beef up your local development? I think you are missing the point with Aspire.

[mayikx]

This is a bit far from Spring Boot 3, but not too far.

[georgehelyar]

It's just pointless right now. I was hyped for dapr and that turned out pretty bad when i tried to actually use it but aspire is not even on the level of dapr. It reminds me more of service fabric, which was truly awful.

[Wfmike]

I dont get aspire at all. If i need to load all my projects and dependencies at once for aspire to do its discovery and orchestration then its just a modular monolith.

[siya.abc]

I'll continue to work as a C# Dev for work, but C# is too much for side projects which is why I've moved on to Go