In the previous post, I showed several ways a developer can statically suppress a DiagnosticAnalyzer. However, what if you need to suppress diagnostics only when a specific code condition is met? In Roslyn, this is exactly what a DiagnosticSuppressor enables. In this post, we will explore how conditional suppression works and why it can be a powerful tool in building smarter C# analyzers.
There are two ways to implement background tasks in .NET, 1) implementing the IHostedService, or 2) inheriting from BackgroundService base class! Even though every BackgroundService is a hosted service, the way .NET framework treats them is different, and in certain scenarios this might be problematic! In this article we take a look into some gotchas of the differences.
Last week at Build 2025 a new way of running C# applications were introduce in which there is no need for a csproj files! This could help getting started with C# easier and more like python, node, or go! Let's take a look into it together!
So far we looked into Diagnostic Analyzers and Code Actions from the perspective of a creator! What if we switch roles and take a look from the consumer's view point of those tools!
In the previous post in the Roslyn series we have explored how we could create code analyzers and how to test them, to reduce the cognitive load on our development team! However, what if we take an extra mile and create a Code Fix Provider to provide some suggestions for the developers! Shall we?
As a developer if you are using Azure for cloud development, one of the first things to do is to authenticate your machine against Azure environment so that Azure knows commands issued against it are from a trusted machine! This is important to also eliminate the need of using connection strings as far as possible! Let's see how easy it is and how it could be done!
In the previous post we have seen how it is possible to create a diagnostic analyzer using Roslyn APIs. Being a TDD advocate it would be disappointing not to talk about how we could test our code analyzer! So let's take a look into it.
We are all familiar with diagnostics that are provided from the compiler when we develop an application, they could be in form of warnings, errors or code suggestions. A diagnostic or code analyzer, inspects our open files for various metrics, like style, maintainability, design, etc. However, sometimes we need to write a tailor-made analysis for our specific situation, tool, or project.
A syntax tree has knowledge about the textual content of what it represents and that content relates to C#. There are scenarios that we need to change the code, such as code fixes, refactorings, or advanced source generation, and it could be done through changing the syntax tree; since this is a bidirectional relationship. There are two approaches, Replacement Methods and SyntaxRewriter classes
I had a discussion on a meet-up a month ago with a friend of mine, and he was telling me it is not really easy or clear how one could create a simple web application in .NET and C#. Hopefully this post is going to help that friend of mine! 😊