I honestly have to admit I was not aware of this ability before today, but I will try to do my best to describe it.
First We need to differentiate between 3 things here:
- .NET Standard
- .NET Framework
- .NET Core
.NET Core and .NET Framework are both implementations of the Standard - and a whole lot on top of that. WinForms was never part of the Standard. It was the .NET Framework going "above and beyond". Wich also explains why .NET Core could so easily drop it. Now apparently besides targetting a .NET project agianst .NET Core, .NET Framework or Mono, you can apparently also aim it against .NET Standard.
That means it can be used in both .NET Core and .NET Framework applications, but you only get exactly what was defined in the .NET Standard - none of the additional stuff. And you also have to manually change it in the project properties, there are not (a lot?) of default templates for it.
WPF apps must target .NET Framework. And UWP is little more then WPF + some app related stuff, when you target .NET Core. So they both must target a specific Target Framework.
Unfortunately the OLEDB classes were never part of .NET Standard. If you look at the "Applies to" section, it only applies to the .NET Framework and one version of Xamarian.
If you look at the SQL related classes, it applies both to Core and Framework - but not the Standard. So you could use them in Project targetting Core or Framework, but not the Standart. It appears the DB related classes are just not nearly generic enough to have made it into the Standard.
Mind you the abstract baseclasses for both are in the Standard 2.0. Just their concrete implementations are a minor detail. So you could write your own DB Access clases based on those abstract classes and Interfaces, if you really felt like it.