On this Reddit thread today, there was a discussion about .NET Aspire something I haven't heard about until now.
One of the comments brings up this point:
I.. uh... have we not been doing this with docker and seeders for... well, near a decade for now? How much of a struggle is it for someone to get spun up on your projects? What about tests?
For us it's always:
All services up, seeders run on startup with empty projects, tests are built to handle their own data, we got cool containers for things like e-mail services such as SMTP4Dev and Minio for S3 making dev work a breeze.
Our worst project? It's Shopify, 80% of the configuration is setting up Shopify and Aspire isn't going to help that.
It seems a lot of service management is just docker, IMO this is where I feel .NET makes missteps (and has in the past) where instead of learning more native tooling, we're encouraged to "never step outside of C#'s Ecosystem".
One of the comments brings up this point:
I.. uh... have we not been doing this with docker and seeders for... well, near a decade for now? How much of a struggle is it for someone to get spun up on your projects? What about tests?
For us it's always:
Bash:
# Run Tests
docker compose up -d
dotnet watch test
# Front end dev
npm run dev
# Back end dev
docker compose up -d
dotnet watch runAll services up, seeders run on startup with empty projects, tests are built to handle their own data, we got cool containers for things like e-mail services such as SMTP4Dev and Minio for S3 making dev work a breeze.
Our worst project? It's Shopify, 80% of the configuration is setting up Shopify and Aspire isn't going to help that.
It seems a lot of service management is just docker, IMO this is where I feel .NET makes missteps (and has in the past) where instead of learning more native tooling, we're encouraged to "never step outside of C#'s Ecosystem".