Anthony Simmon
@anthonysimmon.com
Staff developer at Workleap. Writes blog posts on https://anthonysimmon.com about .NET, Azure, other Microsoft technologies and software development in general.
The blog post I wrote when it was still an internal tool: anthonysimmon.com/dotnet-aspir...
How Workleap uses .NET Aspire to transform local development
We built Leap, an opinionated, reliable CLI tool powered by .NET Aspire to make distributed system development easier for all Workleap developers.
anthonysimmon.com
September 30, 2025 at 12:53 AM
The blog post I wrote when it was still an internal tool: anthonysimmon.com/dotnet-aspir...
I also find it interesting to examine what other programming languages offer, but how would you convince an entire company to change their main programming language when there are more than a hundred C# developers and well-established C#-based products with a 10+ year old codebase?
August 5, 2025 at 2:48 PM
I also find it interesting to examine what other programming languages offer, but how would you convince an entire company to change their main programming language when there are more than a hundred C# developers and well-established C#-based products with a 10+ year old codebase?
I would agree maybe a few years ago, but now the built-in tooling for C# in the .NET SDK is much better. All the IDExxxx and CAxxxx rules are catching up with the third-party tooling we needed, maybe 7 or 8 years ago.
August 5, 2025 at 2:46 PM
I would agree maybe a few years ago, but now the built-in tooling for C# in the .NET SDK is much better. All the IDExxxx and CAxxxx rules are catching up with the third-party tooling we needed, maybe 7 or 8 years ago.
Faster builds: A few huge solutions have seen their build time reduced by up to 20% thanks to the removal of unnecessary StyleCop rules, in favor of built-in performant .NET rules. This translates to shortened feedback loops, faster CI runs, better developer satisfaction.
August 4, 2025 at 4:20 PM
Faster builds: A few huge solutions have seen their build time reduced by up to 20% thanks to the removal of unnecessary StyleCop rules, in favor of built-in performant .NET rules. This translates to shortened feedback loops, faster CI runs, better developer satisfaction.
Uniformity across projects: Developers can now expect the same code style across all projects, regardless of how ancient they are. This has helped reduce the friction when switching between projects or collaborating with other teams.
August 4, 2025 at 4:20 PM
Uniformity across projects: Developers can now expect the same code style across all projects, regardless of how ancient they are. This has helped reduce the friction when switching between projects or collaborating with other teams.
Less boilerplate configuration: Dozens of large, unmaintained .editorconfig files were removed across our repositories. Several csproj files were simplified. Developers no longer ask themselves why a certain rule is enabled or not, it's now documented in a centralized place.
August 4, 2025 at 4:20 PM
Less boilerplate configuration: Dozens of large, unmaintained .editorconfig files were removed across our repositories. Several csproj files were simplified. Developers no longer ask themselves why a certain rule is enabled or not, it's now documented in a centralized place.
Increased developer knowledge: By being exposed to new rules and code suggestions in their IDEs, developers end up learning more about the language and its best practices. It contributed to make them better C# developers.
August 4, 2025 at 4:20 PM
Increased developer knowledge: By being exposed to new rules and code suggestions in their IDEs, developers end up learning more about the language and its best practices. It contributed to make them better C# developers.
Improvement of code quality, performance and security: .NET has all these amazing Roslyn analysis rules that can help catch potential issues early in the development process. Enabling these rules by default has helped us catch many issues that would have otherwise gone unnoticed.
August 4, 2025 at 4:20 PM
Improvement of code quality, performance and security: .NET has all these amazing Roslyn analysis rules that can help catch potential issues early in the development process. Enabling these rules by default has helped us catch many issues that would have otherwise gone unnoticed.
Reduction of time spent in code reviews. Code style issues are now addressed automatically while writing code, or reported by CI checks to authors. This means reviewers spend less time on nitpicking and more time on verifying the actual logic and functionality of the code.
August 4, 2025 at 4:20 PM
Reduction of time spent in code reviews. Code style issues are now addressed automatically while writing code, or reported by CI checks to authors. This means reviewers spend less time on nitpicking and more time on verifying the actual logic and functionality of the code.