Why I won't use .NET Aspire for now
This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).
A .NET developer shares a critical first-hand assessment of .NET Aspire (at Preview 2), arguing it is not ready for practical use outside of Windows and Visual Studio. Key complaints include an overcomplicated setup requiring two extra projects, inability to configure the local environment on Ubuntu/PopOS after several hours, a proprietary control plane that must be installed via a workload command rather than a NuGet package or Docker image, partially closed-source code, and poor documentation. The author draws parallels to the failed Tye project and suggests .NET Aspire should aim to be a 'Spring Boot for .NET' rather than reinventing existing standards like Kubernetes. The post was written at the time of Preview 2 and includes a note that the author later discussed concerns with .NET team members David Fowler and Reuben Bond.
