Sam Hanes

FWIW there is an issue tracking the lack of netstandard support for Microsoft.SqlServer.Types, but it's filed under "Ideas for Future" so I don't think there will be movement on it...

>I'm also trying to figure out how the Type Provider is loaded, or more specifically how can you verify which framework the tooling is running in. And how do type...

@richardjharding What version of Visual Studio do you have installed? Are you following all of the guidance here? https://github.com/Microsoft/visualfsharp/issues/3303 @vjraitila Mono is required to run the design time component on...

@vjraitila Yes that's right - this is a SqlClient-specific requirement. The design-time component depends on a couple of libraries (`Microsoft.SqlServer.TransactSql.ScriptDom` and `Microsoft.SqlServer.Types`) which require full framework.

@richardjharding But what version do you have installed? `fsc.props` is setting the path to the F# compiler, trying to find out which version it is using.

@richardjharding The issue is that SqlClient uses a netfx-only DTC with a netstandard RTC - in order for that to work with a netcore project, I believe that you need...

@vasily-kirichenko A few weeks ago I did send an email to the maintainer of those `Microsoft.SqlServer` nuget packages, asking about the possibility of a netstandard version. Have not heard anything....

Does adding `fsc.props` fix this problem?

@r1sc @vjraitila I really need to document this better, but the underlying issue is that FSharp.Data.SqlClient is *not* fully netstandard compliant. The TP is split into a design-time component (DTC)...

@vjraitila Glad the workaround is working for you. I can't imagine there is any missing API surface in Core required by those `Microsoft.SqlServer` libs - so it probably wouldn't be...