Gauthier Segay

Related: #380 and https://github.com/dotnet/fsharp/issues/10323 Thanks @MarneeDear for the workaround and putting up the repository. I'm not clear yet how to address this in the type provider or if this is...

@jackfoxy, @omcnoe, @costa100, @keppelerj, @cr3wdayt5p I am sorry I can't really help with the issue. Please see the issue I opened https://github.com/dotnet/fsharp/issues/10323 related to discrepancy between VS shipped compiler and...

@daniellittledev thanks for creating this issue. There is a comment regarding this: https://github.com/fsprojects/FSharp.Data.SqlClient/issues/337#issuecomment-507340577 My current idea is that until the new client library provides for feature that would make it...

@daniellittledev do you know if this can achieved while keeping the same codebase and using compiler defines rather than forking the library implementation?

@daniellittledev you can have conditionals in the same fsproj as well for the reference.

@daniellittledev I'd be happy to help with this investigation effort but can't commit time authoring it right now. I can help you get acquainted with the specificities related to TP,...

@daniellittledev you'll first need to add the references, in paket.dependencies DesignTime group and paket.references next to https://github.com/fsprojects/FSharp.Data.SqlClient/tree/master/src/SqlClient.DesignTime also add the normal nuget package reference in https://github.com/fsprojects/FSharp.Data.SqlClient/blob/master/src/SqlClient/SqlClient.fsproj after this, you can...

@daniellittledev thanks a lot for the update. So the two mentionned dependencies and features related to it may be put under conditional compilation. I'm also thinking integrating the work for...

I think it is only netframework and netstandard that will be the targets.

The way I am currently seeing it is we would compile / ship two versions of the type provider, likely compiled out of the same codebase, with different `#define` and...