Request for Comment: Considering moving to .NET Core as the primary target.

[marklio]

I think this is good for a couple of reasons:

• Semiconductor testing is often "unix heavy" (at least it was 13 years ago), and this would provide reach to those platforms.
• .NET Core has a bunch of things that should help with perf. We copy alot of buffers around, and we could stop doing that in favor of leveraging Span<T>/Memory<T> to pass views of the file around.
• I work on the .NET team, so that would likely mean some fresh engagement on this project, which seems to have some renewed interest.
• It should be easy to get bootstrapped. This used to run on Silverlight, so we know we're in a good place API-wise.

I'd definitely open things up to other contributors as well. I'm wondering what the interest level would be here.

Step one would be incorporating the indexing perf work I did a while back that never made it back into master, and producing a "good .NET Framework package" that we can continue to service for folks on .NET Framework.

Then, I'd switch us over to the new project system and target netcoreapp 3.0, and take a stab and refrreshing code comments and annotations to help folks wanting to contribute.

Then, I'd start filing issues for stuff, and folks can pick those up and do them, or I'd do them.

I'd also love to get a good test suite. As has always been the problem, I don't have access to any real STDF files anymore, and folks seem reluctant to give out their own files, so real world testing is really hard.

Thoughts?