So I wanted to update my cheat sheets code from .Net 4.8 to .Net Core which is a simple console project with a bunch of scripts. I tried both Net Core 3.1 and .Net 5.0 RC. What I noticed was:
1- Intellisense had serious issue with lots of unrecognized namespaces and red wiggly lines. As examples, the Font class in System.Drawing or the Form class in System.Windows.Forms were not recognized. Thats aside from things like ParallelSeq behaving similarly. Script would run no problem but intellisense all messed up.
2- Some packages and especially in case of many TypeProviders, they just don’t work with .Net Core, e.g, RegexProvider, FSharp.Data.TypeProvider, etc.
3- Some really good projects like FsLab and RProvider haven’t been really active for quite some time, even though they greatly play on and contribute to the strengths of the language. TypeProvider for python never really took off. Other valuable projects like MBrace appear to be abandoned more-or-less and it is not like current similar popular tools such as Spark are being ported.
Personally I was hoping for a much more complete and uniform experience with much better tooling within a year or so of .Net 5.0 release.