Closed charlesroddie closed 5 years ago
@charlesroddie There is now full .NET Core support, though the facade DLLs still need to be shipped if you want to ship your TPDTC as a .NET Standard component.
I've been trying to assess the exact work required to get full, seamless support for SQLProvider both when targeting .NETCore/.NETStandard and when running at compile-time with .NETCore tooling, but it's somewhat complicated because it's quite a large matrix of different database technologies supported (and even .NET Framework support is not that seamless, e.g. requiring copying around different database driver DLLs, so it's not clear how seamless we need to be to achieve parity).
I think I'll create a tracking issue in SQLProvider to discuss this, and then we can create individual issues back here when specific extra technical problems are identified.
I've created the SQLProvider tracking issue here: https://github.com/fsprojects/SQLProvider/issues/575. Nasty matrix of possibilities.
I'll close this issue since I don't know of any specific work that needs to be done in TPSDK yet
Keeping track of full .Net Standard 2.0 support, as explained in the README:
Related: https://github.com/fsprojects/SQLProvider/issues/426#issuecomment-398683933