I likely won't be contributing. I am just digging around to see what I can see.

.NET OSS has been a journey!

Happy to say I am still walking it!

dotnet now owns mono. I need to hack at mono. Which means the runtime reposittory.

I am in the upside down.

No fun. Maybe less cursing? Maybe ... 😆

This was a lot of fun!

Thank You again for the opportunity to share my opinions!

Going to watch this tonight!

Let me know when the streams are so I can pop in and be a pest

After looking through a few analyzer code fix repos, only a few actually separate those assemblies.

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.

Also. You continue to use Extensions. Which makes me feel like I am missing how you are using it in context.

Yeah. I was migrating a set of Analyzers when I thought about our conversation. I figured I'd try it and see. It's only Analyzers and CodeFixes, no source generation.

I think I am going to attempt the separation for learning, not sure if I will ship it that way.

I love/hate that you explained it so well and that it's in line with what I was thinking I should do.

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

It's called exercise or manual labor. It's been around as long as we have.

I am definitely not the authority on that. 🤷

I'm only two in as a professional. Three total. I am looking forward to achieving these milestones and excited to have the opportunity to grow between now and six!

The only way to Roslyn.