Related to #23762, but I think it isn't clear enough.
Scenario
There are both a .NET Framework and .NET Core applications which are extensible, and provide the extensibility APIs as one or more .NET Standard assemblies. One of the extensions, which targets .NET Standard, uses Microsoft.Win32.Registry, which is expected to work, but it fails on the .NET Framework application with PlatformNotSupportedException, as the facade didn't ship with the extension.
Is this scenario unsupported? If so, is there a workaround? I think that this totally breaks the purpose of .NET Standard, by forcing the extension to know the target runtimes when building.
Related to #23762, but I think it isn't clear enough.
Scenario
There are both a .NET Framework and .NET Core applications which are extensible, and provide the extensibility APIs as one or more .NET Standard assemblies. One of the extensions, which targets .NET Standard, uses
Microsoft.Win32.Registry, which is expected to work, but it fails on the .NET Framework application withPlatformNotSupportedException, as the facade didn't ship with the extension.Is this scenario unsupported? If so, is there a workaround? I think that this totally breaks the purpose of .NET Standard, by forcing the extension to know the target runtimes when building.