More #Roslyn ...
17.02.2026 08:15 — 👍 0 🔁 0 💬 0 📌 0@flash0ver.bsky.social
I C# .NET Sentry for #dotnet @sentry.io Microsoft MVP #MVPBuzz JetBrains Community Contributor @jetbrains.com Code @ github.com/Flash0ver Live: @FlashOWare.bsky.social #2codeOrNot2code Speaking: sessionize.com/FlashOver Co-organizing @dotnetdevs.at
More #Roslyn ...
17.02.2026 08:15 — 👍 0 🔁 0 💬 0 📌 0And we're back!
Starting into the premiere Episode of Season 2026 of #2codeOrNot2code by announcing our brand-new and year-long (and probably beyond) project, perhaps even our Opus Magnum.
on 2026-02-03 (Tuesday)
at 18:00 UTC
#dotnet #CSharp #Roslyn
www.youtube.com/watch?v=5rgb...
In two days, we finally start a new year of awesome events!
And we start big! Alex Thissen is coming to Vienna to talk about DevContainers!
Thanks to RUBICON IT GmbH for hosting us!
RSVP: dotnetdevs.at/events/2026-...
#dotnet #meetup
...
With that being said, I might host my blog at a custom website in the future. Especially considering that @merelyeva.bsky.social and I are about to start coding a UI-heavy Roslyn-based inspection tool—gaining Web-UI experience—during the #2codeOrNot2code live stream: see @flashoware.bsky.social
...
GitHub as a host has plenty of features already built in: Markdown & Code rendering, Discussions, watching notifications, fixes via PRs, git History, automation via Actions/Workflows, Stars & Sponsors, and simply clone the repository for a local copy to feed the context of AI-powered tools.
...
I was contemplating a custom website indeed, bikeshedding to infinity and beyond, resulting in me procrastinating the launch of my blog for years. My New Year's resolution is to Just Do It!
...
At long last: my very first blog post.
Thank you @csadvent.christmas for this incredible kick-starting opportunity. My next blog post is already (early) in the making, and here's to more to come in 2026: Cheers!
Day 11 of the C# Advent Calendar 2025: www.csadvent.christmas
As the final episode of this season, @merelyeva.bsky.social and @flash0ver.bsky.social build a Roslyn Source Generator polyfilling a Throw-Helper live, at 18:00 UTC.
#CSAdvent #CSharp #dotnet #Roslyn
www.youtube.com/watch?v=sB37...
It is a #2codeOrNot2code tradition to host @stu.dev diving deep into the latest #CSharp language features, as well as discussing what's new in #dotnet. Join us for some sweet syntactic sugar of C# 14 and .NET 10.
Date: 2025-11-18 (Tuesday)
Time: 18:00 (UTC±00:00)
www.youtube.com/watch?v=61kj...
It's time for the multi-targeting finale, dear dedicated #dotnet developers.
We're concluding our journey of packing #MSBuild .props and .targets for versioning of #Roslyn components like #CSharp analyzers.
Date: 2025-11-10 (Monday)
Time: 18:00 (UTC)
#2codeOrNot2code
www.youtube.com/watch?v=RuOl...
Thank you so much for your uplifting feedback @bayn.es. I am really glad you liked my session.
I just left a couple of rough months behind me, so your kind words are a true pick-me-up for my spirit.
You are very welcome.
Again, it's multi-targeting Wednesday, dear dedicated #dotnet developers.
We're back with packing #MSBuild .props and .targets for versioning of #Roslyn components like #CSharp analyzers.
Date: 2025-09-17 (Wednesday)
Time: 17:00 (UTC)
#2codeOrNot2code
www.youtube.com/watch?v=wxUQ...
It's multi-targeting Wednesday, dear dedicated #dotnet developers,
where we pack some .props and .targets for versioning of Roslyn components like #CSharp source generators.
Date: 2025-08-27 (Wednesday)
Time: 17:00 (UTC)
#2codeOrNot2code
www.youtube.com/watch?v=ipoG...
Even more Performance Measurement and Profiling of Roslyn Source-Generators included in Part 3 of Benchmarking Compiler Extensions.
- Wednesday, 2025-08-13
- 17:00 UTC
#dotnet #CSharp #Roslyn
#2codeOrNot2code
www.youtube.com/watch?v=8kpl...
More Performance Measurement and Profiling of Roslyn Source-Generators upcoming in Part 2 of Benchmarking Compiler Extensions.
We moved the live-stream by one day,
to: Thursday, 2025-08-07
at the same time: 17:00 UTC
#dotnet #CSharp #Roslyn
#2codeOrNot2code
www.youtube.com/watch?v=pRLR...
@rlittlesii.bsky.social
We are now starting a series on #Benchmarking #Roslyn Compiler Extensions.
We begin with setting up the project and building a first prototype.
bsky.app/profile/flas...
The (run)time has come!
We allocate this series to build a library that supports Benchmarking of #Roslyn Compiler Extensions, like #dotnet Analyzers and #CSharp Source-Generators.
2025-07-23 Wednesday
17:00 UTC
#2codeOrNot2code
www.youtube.com/watch?v=Rbu8...
Can't wait till Saturday.
10.07.2025 22:04 — 👍 0 🔁 0 💬 0 📌 0We're building up to it:
Today, we will inspect, together with @kevingosse.net, what methods and calls really are
bsky.app/profile/flas...
and then - probably next episode - kick-start our journey of Tools for Roslyn Compiler Extensions; starting with Benchmarking.
We'll ping you when announced.
Let's inspect "The hidden life of method calls" in #dotnet via #CSharp with @kevingosse.net.
Date: 2025-07-09 Wednesday
Time: 17:00 UTC
#2codeOrNot2code
www.youtube.com/watch?v=JhBI...
We're back! After our "Tour de Talk", we continue our theme of #dotnet Memory Management and combine it with our session about Patterns from both #NDCOslo and #TechoramaBE 2025:
Let's dive deep into the #CSharp Dispose Pattern.
on Tuesday, 2025-06-24
at 17:00 UTC
www.youtube.com/watch?v=qRuG...
Not quite yet.
But we are about to get back into live-streaming next week, and will be building up towards Benchmarking of Roslyn Compiler Extensions.
I'll get back to you once we actively start that endeavour.
From what I read is that "Compiler-Extensions" is the official term used in (limited) documentation for Plugins that Roslyn-Hosts may load for compilations (Analyzers, Suppressors, Generators) and IDEs/Editors may interact with via Workspaces (Fixers, Refactorings, Completions).
17.06.2025 16:33 — 👍 1 🔁 0 💬 1 📌 0Also ... so I think, I'm not positive though ... that, technically speaking, if your Extensions only use types that they are safe/meant to use, in accordance with the respective [Attribute], you should be fine putting all together in a single Assembly and it should work for the most common scenarios
17.06.2025 15:57 — 👍 1 🔁 0 💬 1 📌 0...
Example:
Should you use a type from "Microsoft.CodeAnalysis.CSharp.Workspaces" in your Analyzer or Suppressor or Generator, but your Extension is loaded in a Build/Compilation-Scneario (only Editor-Scenarios usually require the Workspaces-APIs to be loaded), then your Extension might not work.
...
The reason for this guideline is that Roslyn is a Library which can be hosted by any tool, so the Extension-Author does not necessarily know under which environment the Compiler will run and whether, e.g., the Workspaces-Assembly is loaded or just "Microsoft.CodeAnalysis.CSharp/VisualBasic".
...
...
And for NuGet, you can pack them together in PackagePath="analyzers/dotnet/cs".
I usually have a separate CSPROJ that only represents the NuGet package and packs all netstandard2.0 libraries together.
...
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).
...
I never had matching T-shirts before 👕
I got mine from @updateconference.bsky.social #UpdateConference
Pro .NET Memory Shenanigans:
In this April Fools' Day episode, @merelyeva.bsky.social and @flash0ver.bsky.social unveil some Memory-related inner workings of #dotnet with unsafe and unexpected #CSharp shenanigans.
2025-04-01 | 17:00 UTC (5 PM)
#2codeOrNot2code
www.youtube.com/watch?v=Xqdk...