Roslyn, New York
Population: 2,902
Photos from Google Places API
Link: https://en.wikipedia.org/wiki/Roslyn,_New_York
Population: 2,902
Photos from Google Places API
Link: https://en.wikipedia.org/wiki/Roslyn,_New_York
February 18, 2024 at 7:01 AM
Roslyn, New York
Population: 2,902
Photos from Google Places API
Link: https://en.wikipedia.org/wiki/Roslyn,_New_York
Population: 2,902
Photos from Google Places API
Link: https://en.wikipedia.org/wiki/Roslyn,_New_York
I just wrote a Roslyn refactoring! I have to say the Roslyn API is beautiful and I loved the experience.
gist.github.com/KirillOsenko...
gist.github.com/KirillOsenko...
September 26, 2025 at 1:02 AM
I just wrote a Roslyn refactoring! I have to say the Roslyn API is beautiful and I loved the experience.
gist.github.com/KirillOsenko...
gist.github.com/KirillOsenko...
Suppressing Roslyn Analyzer Warnings Programmatically using DiagnosticSuppressor #dotnet #roslyn https://www.meziantou.net/suppressing-roslyn-analyzer-warnings-programmatically-using-diagnosticsuppressor.htm?utm_medium=social&utm_source=bluesky
Suppressing Roslyn Analyzer Warnings Programmatically using DiagnosticSuppressor - Gérald Barré
Learn how to programmatically suppress Roslyn analyzer warnings using the DiagnosticSuppressor API.
www.meziantou.net
April 14, 2026 at 2:59 PM
Suppressing Roslyn Analyzer Warnings Programmatically using DiagnosticSuppressor #dotnet #roslyn https://www.meziantou.net/suppressing-roslyn-analyzer-warnings-programmatically-using-diagnosticsuppressor.htm?utm_medium=social&utm_source=bluesky
Released a first version for a solution template for building professional class libraries as a NuGet package with everything you need. Build scripts, API validation, a nice read-me, .editorconfig, Roslyn, automatic versioning, unit tests, etc.
github.com/dennisdoomen...
github.com/dennisdoomen...
GitHub - dennisdoomen/dotnet-package-templates: "dotnet new" templates for building NuGet-published (content-only) multi-targeting libraries with all the bells and whistles
"dotnet new" templates for building NuGet-published (content-only) multi-targeting libraries with all the bells and whistles - dennisdoomen/dotnet-package-templates
github.com
January 21, 2025 at 1:11 PM
Released a first version for a solution template for building professional class libraries as a NuGet package with everything you need. Build scripts, API validation, a nice read-me, .editorconfig, Roslyn, automatic versioning, unit tests, etc.
github.com/dennisdoomen...
github.com/dennisdoomen...
Added git support to my .NET OMD generator tool, and now you can create a GitHub action that'll add a comment to your PR if there are API changes and list them. It'll even update its comment as you update the PR. See doc here how: github.com/dotMorten/Do...
GitHub - dotMorten/DotNetOMDGenerator: A Roslyn-based cross-platform tool that generates an object model diagram from a set of C# source files or assemblies
A Roslyn-based cross-platform tool that generates an object model diagram from a set of C# source files or assemblies - dotMorten/DotNetOMDGenerator
github.com
May 24, 2026 at 12:25 AM
Added git support to my .NET OMD generator tool, and now you can create a GitHub action that'll add a comment to your PR if there are API changes and list them. It'll even update its comment as you update the PR. See doc here how: github.com/dotMorten/Do...
Roslyn, South Dakota
Population: 168
Photos from Google Places API
Link: https://en.wikipedia.org/wiki/Roslyn,_South_Dakota
Population: 168
Photos from Google Places API
Link: https://en.wikipedia.org/wiki/Roslyn,_South_Dakota
July 7, 2023 at 1:35 AM
Roslyn, South Dakota
Population: 168
Photos from Google Places API
Link: https://en.wikipedia.org/wiki/Roslyn,_South_Dakota
Population: 168
Photos from Google Places API
Link: https://en.wikipedia.org/wiki/Roslyn,_South_Dakota
IOperation vs SyntaxNode vs Symbol in Roslyn: Choosing the Right Analysis API
Learn when to use IOperation Roslyn vs SyntaxNode vs Symbol APIs. Compare the three analysis layers to pick the right one for your C# analyzer in .NET 10.
Read the article here:
https://bgh.st/53eil9
Learn when to use IOperation Roslyn vs SyntaxNode vs Symbol APIs. Compare the three analysis layers to pick the right one for your C# analyzer in .NET 10.
Read the article here:
https://bgh.st/53eil9
July 16, 2026 at 10:58 PM
IOperation vs SyntaxNode vs Symbol in Roslyn: Choosing the Right Analysis API
Learn when to use IOperation Roslyn vs SyntaxNode vs Symbol APIs. Compare the three analysis layers to pick the right one for your C# analyzer in .NET 10.
Read the article here:
https://bgh.st/53eil9
Learn when to use IOperation Roslyn vs SyntaxNode vs Symbol APIs. Compare the three analysis layers to pick the right one for your C# analyzer in .NET 10.
Read the article here:
https://bgh.st/53eil9
I love/hate to say: It depends.
For maximum compatibility and safety, separate Roslyn-Extensions by Diagnostics-API (Analyzers + Suppressors + Generators) and Workspaces-API (Fixers + Refactorings), as well as separate Compiler-Extensions by Language (Common / CSharp / VisualBasic).
...
For maximum compatibility and safety, separate Roslyn-Extensions by Diagnostics-API (Analyzers + Suppressors + Generators) and Workspaces-API (Fixers + Refactorings), as well as separate Compiler-Extensions by Language (Common / CSharp / VisualBasic).
...
June 17, 2025 at 8:27 AM
I love/hate to say: It depends.
For maximum compatibility and safety, separate Roslyn-Extensions by Diagnostics-API (Analyzers + Suppressors + Generators) and Workspaces-API (Fixers + Refactorings), as well as separate Compiler-Extensions by Language (Common / CSharp / VisualBasic).
...
For maximum compatibility and safety, separate Roslyn-Extensions by Diagnostics-API (Analyzers + Suppressors + Generators) and Workspaces-API (Fixers + Refactorings), as well as separate Compiler-Extensions by Language (Common / CSharp / VisualBasic).
...
reached a new level of nerd recently, generating C# scripts with the Roslyn SyntaxFactory API in Godot. it's mostly a miserable experience, and inefficient compared to just writing string chunks for simple use cases, but something about connecting the bricks just tickles my brain ☀️
August 23, 2026 at 3:26 PM
reached a new level of nerd recently, generating C# scripts with the Roslyn SyntaxFactory API in Godot. it's mostly a miserable experience, and inefficient compared to just writing string chunks for simple use cases, but something about connecting the bricks just tickles my brain ☀️
Roslyn lacks a higher level tree API that would be convenient. SyntaxFactory is too high fidelity and low level, it cares about punctuation, whitespace, etc. Something like CodeDom or CodeModel would be more usable.
February 9, 2025 at 5:38 PM
Roslyn lacks a higher level tree API that would be convenient. SyntaxFactory is too high fidelity and low level, it cares about punctuation, whitespace, etc. Something like CodeDom or CodeModel would be more usable.
Is the built-in API compatibility verification of the .NET SDK the replacement for `Microsoft.CodeAnalysis.PublicApiAnalyzers`?
https://github.com/dotnet/roslyn-analyzers/issues/7506
#dotnet
https://github.com/dotnet/roslyn-analyzers/issues/7506
#dotnet
Is the built-in API compatibility verification of the .NET SDK the replacement for Microsoft.CodeAnalysis.PublicApiAnalyzers? · Issue #7506 · dotnet/roslyn-analyzers
The .NET SDK itself now has means to check for source or binary breaking changes in the public API against an earlier version of an assembly or package. In addition to the MSbuild tasks there is ev...
github.com
December 15, 2024 at 3:42 PM
Is the built-in API compatibility verification of the .NET SDK the replacement for `Microsoft.CodeAnalysis.PublicApiAnalyzers`?
https://github.com/dotnet/roslyn-analyzers/issues/7506
#dotnet
https://github.com/dotnet/roslyn-analyzers/issues/7506
#dotnet
This probably seems like one of the most sensible approaches - The VSCode dev docs actually call this out, and link to docs from their PHP parser which says it borrows from Roslyn: code.visualstudio.com/api/language...
I might have to go this route when I next have time to poke at this...
I might have to go this route when I next have time to poke at this...
March 28, 2025 at 10:20 PM
This probably seems like one of the most sensible approaches - The VSCode dev docs actually call this out, and link to docs from their PHP parser which says it borrows from Roslyn: code.visualstudio.com/api/language...
I might have to go this route when I next have time to poke at this...
I might have to go this route when I next have time to poke at this...
This is good to know what when designing APIs.
I always felt the cursor should be forward moving and anything that requires you to shift back is a hassle so this is a good option for it.
Is there an API for it a la Roslyn completion providers?
I always felt the cursor should be forward moving and anything that requires you to shift back is a hassle so this is a good option for it.
Is there an API for it a la Roslyn completion providers?
December 28, 2024 at 11:42 PM
This is good to know what when designing APIs.
I always felt the cursor should be forward moving and anything that requires you to shift back is a hassle so this is a good option for it.
Is there an API for it a la Roslyn completion providers?
I always felt the cursor should be forward moving and anything that requires you to shift back is a hassle so this is a good option for it.
Is there an API for it a la Roslyn completion providers?
Suppressing Roslyn Analyzer Warnings Programmatically using DiagnosticSuppressor www.meziantou.net/suppressing-...
Suppressing Roslyn Analyzer Warnings Programmatically using DiagnosticSuppressor - Gérald Barré
Learn how to programmatically suppress Roslyn analyzer warnings using the DiagnosticSuppressor API.
www.meziantou.net
April 13, 2026 at 3:49 PM
Suppressing Roslyn Analyzer Warnings Programmatically using DiagnosticSuppressor www.meziantou.net/suppressing-...
The fact a Roslyn dev put up an issue about it (as an analyzer) should have given pause that maybe this was a bad idea. https://github.com/clariuslabs/clide
He was the primary dev for Clide, which is used all over the Xamarin extensions. It’s useful! It also is a huge performance headache!
He was the primary dev for Clide, which is used all over the Xamarin extensions. It’s useful! It also is a huge performance headache!
GitHub - clariuslabs/clide: An Enjoyable IDE Automation API
An Enjoyable IDE Automation API. Contribute to clariuslabs/clide development by creating an account on GitHub.
github.com
August 10, 2023 at 6:49 AM
The fact a Roslyn dev put up an issue about it (as an analyzer) should have given pause that maybe this was a bad idea. https://github.com/clariuslabs/clide
He was the primary dev for Clide, which is used all over the Xamarin extensions. It’s useful! It also is a huge performance headache!
He was the primary dev for Clide, which is used all over the Xamarin extensions. It’s useful! It also is a huge performance headache!
Old source generators API was much easier, but also much slower.
New incremental generators are difficult. Although roslyn team has a very informative cook book.
New incremental generators are difficult. Although roslyn team has a very informative cook book.
July 8, 2025 at 1:14 AM
Old source generators API was much easier, but also much slower.
New incremental generators are difficult. Although roslyn team has a very informative cook book.
New incremental generators are difficult. Although roslyn team has a very informative cook book.
If you were to add scripting support to a .NET app, would you pick C# (via Roslyn Scripting API) or PowerShell as your app's scripting language? It's a side project, a free productivity helper tool aimed mostly at developers. #PowerShell, #dotnetcore, #csharp
November 18, 2024 at 9:59 PM
If you were to add scripting support to a .NET app, would you pick C# (via Roslyn Scripting API) or PowerShell as your app's scripting language? It's a side project, a free productivity helper tool aimed mostly at developers. #PowerShell, #dotnetcore, #csharp
Roslyn compiler provides a convenient API that converts source code into a syntax tree. It’s then very easy to check whether a certain convention adopted by your team is followed. 🧵 8/15 👇
April 7, 2025 at 12:41 PM
Roslyn compiler provides a convenient API that converts source code into a syntax tree. It’s then very easy to check whether a certain convention adopted by your team is followed. 🧵 8/15 👇
Wrote a small Roslyn code generator to help me with my Roslyn code generator: github.com/xamarin/xama...
#csharp #roslyn
#csharp #roslyn
[Rgen] Use a roslyn code generator to help generate the flag parsing of all attributes. by mandel-macaque · Pull Request #22032 · xamarin/xamarin-macios
The old Xamarin API used A LOT of attributes as flags to indicate different generating methods. All this attributes do not have any data and can be used as a feature flag.
For example, if we wanted...
github.com
January 23, 2025 at 7:06 PM
Wrote a small Roslyn code generator to help me with my Roslyn code generator: github.com/xamarin/xama...
#csharp #roslyn
#csharp #roslyn
Dew Drop – July 23, 2012 (#1,369)
Top Links Roslyn Code Quoter tool – generating syntax API...
alvn.me
December 2, 2024 at 11:10 PM
Dew Drop – October 3, 2012 (#1,414)
Top Links Scripting Web API self host with Roslyn CTP – P...
alvn.me
December 2, 2024 at 9:42 PM
Random C# tip: install the Banned APIs Roslyn Analyzer (www.nuget.org/packages/Mic...) and promptly ban the default constructor of TaskCompletionSource. If people don't want RunContinuationsAsynchronously, they can explicitly pass in None. It will save you some headaches!
Microsoft.CodeAnalysis.BannedApiAnalyzers 3.3.4
Banned API Analyzers
www.nuget.org
January 31, 2026 at 8:28 AM
Random C# tip: install the Banned APIs Roslyn Analyzer (www.nuget.org/packages/Mic...) and promptly ban the default constructor of TaskCompletionSource. If people don't want RunContinuationsAsynchronously, they can explicitly pass in None. It will save you some headaches!
【C#】Incremental Source Generator入門
! この記事は以前別のブログに投稿した記事を再編したものです。 今回の記事はC#のIncremental Source Generatorについて。 C#ではSource Generatorを用いることで、コンパイル時に属性などの情報から動的にコードを生成することが可能です。これはシリアライザや通信層のライブラリなどによく使われていて、ボイラーコードの生成を自動化するのに役立ちます。また、近年ではNativeAOTへの対応から、従来ではリフレクションやIL生成で行っていた処理をSource…
! この記事は以前別のブログに投稿した記事を再編したものです。 今回の記事はC#のIncremental Source Generatorについて。 C#ではSource Generatorを用いることで、コンパイル時に属性などの情報から動的にコードを生成することが可能です。これはシリアライザや通信層のライブラリなどによく使われていて、ボイラーコードの生成を自動化するのに役立ちます。また、近年ではNativeAOTへの対応から、従来ではリフレクションやIL生成で行っていた処理をSource…
【C#】Incremental Source Generator入門
! この記事は以前別のブログに投稿した記事を再編したものです。 今回の記事はC#のIncremental Source Generatorについて。 C#ではSource Generatorを用いることで、コンパイル時に属性などの情報から動的にコードを生成することが可能です。これはシリアライザや通信層のライブラリなどによく使われていて、ボイラーコードの生成を自動化するのに役立ちます。また、近年ではNativeAOTへの対応から、従来ではリフレクションやIL生成で行っていた処理をSource Generatorに置き換える作業が進んでいます。 そこで今回はRoslynの基本的な部分からIncremental Source Generatorの実装までを解説していきます。ややとっつきにくさはありますが、使いこなせれば非常に強力なツールになるので、特にライブラリなどを開発する方は覚えておくと良いでしょう。 前提知識 C#の基礎的な知識 構文解析に関する基本的な知識 (字句解析、抽象構文木など) Source Generatorの開発ではRoslynのAPIでC#コードの構文解析を行うため、構文解析に関してある程度の知識があると理解がしやすいでしょう。 プロジェクトの作成 Source Generatorのプロジェクト まずは、Source Generatorの開発用のプロジェクトを作成しましょう。 通常通りクラスライブラリを作成すれば良いのですが、一点注意としてTargetFrameworkはnetstandard2.0にする必要があります。これはVisual Studioが.NET Frameworkで動作しているため、最新のバージョンと互換性がないためです。 プロジェクトを作成したら、NuGetからMicrosoft.CodeAnalysis.CSharpをインストールします。ただし、最新のバージョンを入れれば良いわけではなく、ターゲットとなるVisual StudioやUnityに対応したバージョンを明示的に指定する必要があります。Unity 2022.3.12f1以降であれば4.3.0が利用可能であるため、その辺りを目安にすると良いでしょう。 .NET CLI dotnet add package Microsoft.CodeAnalysis.CSharp --version 4.3.0 Package Manager NuGet\Install-Package Microsoft.CodeAnalysis.CSharp -Version 4.3.0 Package Reference PackageReference Include="Microsoft.CodeAnalysis.CSharp" Version="4.3.0" /> また、Source Generator専用の設定やNuGet配布用に設定をいくつか追加する必要があります。.csprojファイルに以下の項目を追加してあげればOKです。 Project Sdk="Microsoft.NET.Sdk"> PropertyGroup> TargetFramework>netstandard2.0TargetFramework> ImplicitUsings>enableImplicitUsings> Nullable>enableNullable> LangVersion>13LangVersion> IsRoslynComponent>trueIsRoslynComponent> AnalyzerLanguage>csAnalyzerLanguage> IncludeBuildOutput>falseIncludeBuildOutput> DevelopmentDependency>trueDevelopmentDependency> IncludeSymbols>falseIncludeSymbols> SuppressDependenciesWhenPacking>trueSuppressDependenciesWhenPacking> PropertyGroup> ItemGroup> PackageReference Include="Microsoft.CodeAnalysis.CSharp" Version="4.3.0" /> ItemGroup> ItemGroup> None Include="$(OutputPath)\$(AssemblyName).dll" Pack="true" PackagePath="analyzers/dotnet/cs" Visible="false" /> ItemGroup> Project> …
inmobilexion.com
June 13, 2025 at 2:44 PM
【C#】Incremental Source Generator入門
! この記事は以前別のブログに投稿した記事を再編したものです。 今回の記事はC#のIncremental Source Generatorについて。 C#ではSource Generatorを用いることで、コンパイル時に属性などの情報から動的にコードを生成することが可能です。これはシリアライザや通信層のライブラリなどによく使われていて、ボイラーコードの生成を自動化するのに役立ちます。また、近年ではNativeAOTへの対応から、従来ではリフレクションやIL生成で行っていた処理をSource…
! この記事は以前別のブログに投稿した記事を再編したものです。 今回の記事はC#のIncremental Source Generatorについて。 C#ではSource Generatorを用いることで、コンパイル時に属性などの情報から動的にコードを生成することが可能です。これはシリアライザや通信層のライブラリなどによく使われていて、ボイラーコードの生成を自動化するのに役立ちます。また、近年ではNativeAOTへの対応から、従来ではリフレクションやIL生成で行っていた処理をSource…