When your plugin has a Windows specific TFM the nuget catalogs don't work #9
Description
If you have a nuget based plugin that uses a TFM like "net6.0-windows10.0.19041" the nuget catalog initializations will fail even if the executable loading the plugins is targeting the same TFM. This is due to a difference in how the NuGetFramework parse calls behave. When these calls are made within the nuget downloader they return framework objects that don't pass the test:
var _compProvider = new CompatibilityProvider(new DefaultFrameworkNameProvider());
var compatible = _compProvider.IsCompatible(bal, baz);
NuGetFramework.Parse("net6.0-windows10.0.19041")
NuGetFramework.ParseFrameworkName("net6.0-windows10.0.19041", frameworkNameProvider);