.NET OSS has been a journey!
Happy to say I am still walking it!
.NET OSS has been a journey!
Happy to say I am still walking it!
I am in the upside down.
I am in the upside down.
Why raise a seed now? What's ahead?
Read more👇
Why raise a seed now? What's ahead?
Read more👇
Today is not that day.
Today is not that day.
Date: 2025-07-09 Wednesday
Time: 17:00 UTC
#2codeOrNot2code
www.youtube.com/watch?v=JhBI...
Date: 2025-07-09 Wednesday
Time: 17:00 UTC
#2codeOrNot2code
www.youtube.com/watch?v=JhBI...
More details about Astro and why we are sponsoring on our blog: duende.link/astr055 #dotnet #astro #identity
More details about Astro and why we are sponsoring on our blog: duende.link/astr055 #dotnet #astro #identity
Any traction on the performance testing of analyzers? It's becoming more an more important.
I've got a codebase with over a million lines of C# and I want to test the perf of my analysis.
Any traction on the performance testing of analyzers? It's becoming more an more important.
I've got a codebase with over a million lines of C# and I want to test the perf of my analysis.
I think I am going to attempt the separation for learning, not sure if I will ship it that way.
I think I am going to attempt the separation for learning, not sure if I will ship it that way.
I am still a bit shaky on how the separation of the assemblies but the single nuget package gets around the Workspace API problem.
I am sure it will come to me as I am building the package
I am still a bit shaky on how the separation of the assemblies but the single nuget package gets around the Workspace API problem.
I am sure it will come to me as I am building the package
Is the thought that I should expect consumers to use two nuget packages?
Or should I find a way to bring them back together under a single package?
Is the thought that I should expect consumers to use two nuget packages?
Or should I find a way to bring them back together under a single package?