Andrii Kurdiumov

@JonathanMagnan Will you in principle support that change to API ? There modern tools for writing more performance oriented parsing, using for example Span and System.Memory infrastructure in .NET Core....

@JonathanMagnan I'm more asking if you are up to accepting contribution which could help you move in that direction?

@jbevain I was hitting that in the actual snippet which I wrote in the issue. That snipped was created by @fornever when he play with C compiler in .NET. He...

@jbevain I think this is ready for another round of review.

Bye bye IE. let mark classes as obsolete. What are internal position? Does any discussion should happen for this plan?

> enhancing the [.NET Upgrade Assistant](https://dotnet.microsoft.com/platform/upgrade-assistant) to help converting MsgBox to MessageBox API. Not clear what this is means. Does MsgBox uses HTML related classes internally? Where is .NET Upgrade...

@JeremyKuhne Yes. I potentially willing to contribute in that area. I have further questions which will affect my contributions. Does this repo should take into account .NET 3.1? If yes,...

> So changes will go into .NET 6.0 onwards. Quick question to double-check that I understand correctly. For me this is means that I should not worry about .NET 3.1...

Most work in ComWrappers would be like in #5174 where private instances would be used to provide access to COM instances. This would work for handful of places, but not...

# Problematic API which rely on the built-in COM During my ComWrappers work, I start noticing API which make my life miserable. I would like to document them, so some...