Anthony Simmon

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.

121 followers68 following39 posts

So honored to have been awarded Microsoft MVP earlier this month. Three years ago, I never would've imagined being interviewed by Scott Hanselman, giving talks, and being on podcasts. Thanks to everyone who believed in me! #mvpbuzz #dotnet #csharp #aspire

Workleap's C#/.NET coding standards has reached 100 stars in just a couple of days. It seems that people like the idea of simply installing a NuGet package to get code styling, best practices for performance, quality, and security enforced by default in any IDE and during CI builds! #dotnet #csharp

Anthony Simmon@anthonysimmon.com

We standardized our C# code style, fine-tuned hundreds of built-in Roslyn analyzers and MSBuild properties, all bundled into a single reusable NuGet package. No more EditorConfig files! Learn more at medium.com/p/02ff340b4a96 🧵Learnings and benefits in thread... #dotnet #csharp

We standardized our C# code style, fine-tuned hundreds of built-in Roslyn analyzers and MSBuild properties, all bundled into a single reusable NuGet package. No more EditorConfig files! Learn more at medium.com/p/02ff340b4a96 🧵Learnings and benefits in thread... #dotnet #csharp

medium.comHow we enforce .NET coding standards at Workleap to improve productivity, quality and performanceDistributing .editorconfig and MSBuild properties across hundreds of .NET projects is now as easy as adding a single NuGet package.
View full thread

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.

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.

We standardized our C# code style, fine-tuned hundreds of built-in Roslyn analyzers and MSBuild properties, all bundled into a single reusable NuGet package. No more EditorConfig files! Learn more at medium.com/p/02ff340b4a96 🧵Learnings and benefits in thread... #dotnet #csharp

medium.comHow we enforce .NET coding standards at Workleap to improve productivity, quality and performanceDistributing .editorconfig and MSBuild properties across hundreds of .NET projects is now as easy as adding a single NuGet package.
View full thread

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.

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.

We standardized our C# code style, fine-tuned hundreds of built-in Roslyn analyzers and MSBuild properties, all bundled into a single reusable NuGet package. No more EditorConfig files! Learn more at medium.com/p/02ff340b4a96 🧵Learnings and benefits in thread... #dotnet #csharp

medium.comHow we enforce .NET coding standards at Workleap to improve productivity, quality and performanceDistributing .editorconfig and MSBuild properties across hundreds of .NET projects is now as easy as adding a single NuGet package.

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.

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.

Extract OpenAPI specs from #dotnet web apps automatically. Fail CI checks if the spec isn't synced with #csharp code, validate it against Spectral rules, and catch breaking changes. All handled at build time by a single NuGet package made at Workleap. medium.com/p/8a535d813244

medium.comHow we enforce web API standards and guidelines at WorkleapWe automate API specs as first class citizens, keeping them versioned, validated, and checked for breaking changes in ASP.NET Core projects.

Ce mardi 3 juin à 17h30, rendez-vous chez Microsoft Montréal pour un meetup sur comment améliorer l'expérience de développement avec .NET Aspire. Démos, expérimentations poussées et astuces pour tirer le meilleur de Aspire. 📍 www.meetup.com/msdevmtl/eve... #dotnet #aspire #msdevmtl

meetup.comAméliorer l'expérience de développement grâce à .NET Aspire, Tue, Jun 3, 2025, 5:30 PM | MeetupUne bonne expérience de développement offre de nombreux avantages. Une productivité accrue, une durée d'onboarding réduite, une meilleure satisfaction des développeurs. Exp

Anthony Simmon reposted

Windows Advanced settings is here! We restructured the For Developers page and added new features such as File Explorer with version control 🚀 Easily view your Git information directly in columns within File Explorer! 🔥

It's kind of the best of both worlds - the Jetbrains developer experience and productivity, and the latest available GitHub Copilot features on VS Code #dotnet #jetbrains #vscode #csharp

JetBrains ReSharper@resharper.jetbrains.com

ReSharper in #VSCode: Public Preview Begins! 🚀 The legendary C# productivity toolkit has just become available for Visual Studio Code. Your editor may change, but your ReSharper benefits remain. Dive into the details here: jb.gg/rs-in-vscode... #dotnet #visualstudio #csharp #.net #jetbrains

Anthony Simmon reposted

Aspire 9.3 new dashboard features, day 6: The console logs page URL now uses a friendly resource name (e.g., frontend) instead of an internal ID. This means you can bookmark the page and it’ll work across dashboard launches 🔖 #dotnet #aspire

Anthony Simmon reposted

Au menu de notre table ronde de Mai : - Les avancés de Docker dans l'IA, - Choisir (ou pas) entre SMB et NFS, - Les AI Agents dans Azure AI Foundry, - Les simplifications qu'apporte Workload Identity Federation. Bonne écoute et visionnage de notre 69ème épisode...⬇️⬇️⬇️

That was a nice French early .NET Aspire 9.2 release party! #dotnet #aspire @scott.hanselman.com See, I have a better setup now. I still need to get rid of the vacuum cleaner and have better lighting...

Si vous voulez en savoir plus sur la nouvelle version de .NET Aspire 9.2, écoutez notre dernier podcast avec @anthonysimmon.com #aspire @davidfowl.com 🎞️ www.youtube.com/watch?v=H9pH... 🎧 devdevdev.net/tr04-25-dapr...

There's an upcoming feature in .NET Aspire that adds a live graph view of resources in the dashboard. However, I believe there's value in generating a static architectural diagram that could be embedded in documentation, for instance. Here's how: anthonysimmon.com/generating-a... #dotnet #aspire

anthonysimmon.comGenerating architecture diagrams from .NET Aspire resources at publish timeUse the new relationship capabilities in .NET Aspire 9.1 to build a custom Mermaid exporter for generating architecture diagrams that are always up-to-date.

FluentAssertions costs more than my @jetbrains.com Rider IDE, which I can't live without and has greatly contributed to making me the #dotnet developer I am today. I find it hard to justify the $130 per-user price for a non-critical library. Where's the enterprise offering?

Did you know that you could run an #aspnetcore app over named pipes instead of TCP/IP? Another great alternative for inter-process communication is StreamJsonRpc, which is used by C#'s LSP server in VS Code. Check out how this works at: anthonysimmon.com/local-ipc-ov... #csharp #dotnet

anthonysimmon.comLocal inter-process communication over named pipes with ASP.NET Core or StreamJsonRpc in .NETLearn how to set up efficient RPC communication between two processes using bidirectional named pipes, well-defined contracts, and structured messages.

You are up to date.