Some time ago, I wrote that I won't use .NET #Aspire for now, and now I checked it again. Result? It got better! Now I can finally use it! 😅 I faced some issues again, but non-blocking this time. It's clearly visible that the team is motivated and working hard to improve it.
I was really impressed by the response time, discussion on Discord with @davidfowl and quick turnaround for the issues I found. Much appreciated!
Today I learned that the prod-ready release of #dotnet#aspire is scheduled for the upcoming weeks.
What is your opinion on this? Is it ready for the big show?
I personally love it, but there are still some things I hope will make its way into it. For example I really hope that @davidfowl 'WaitFor' will be introduced before that.
Microsoft's Aspire framework looks cool to manage simple application with few dependencies.
It allows to write in application code the dependencies, and when deployed they start automatically.
For example if you add dependency to PostgreSQL or Redis then when started it starts it. Locally it uses K8s, but apparently when deployed to Azure it can use containers or services.
No need to write YAML, just pure C# & Nuget to get external services working.
Did you know @rafaelldi is working on a #dotnet#aspire plugin for #JetBrainsRider. There's an experimental feature that uses distributed traces to determine your solution's architecture and diagram it.