-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dotnetcore support? #426
Comments
Hello. See #303 I don't think that .NET Core supports type providers currently. They will be supported after .NET Core 2.0 release. |
This is erasing typeprovider so in theory it could be done already with 1.6 by excluding providedtypes.fs and sqldesigntime.fs from the source code project. However this relies heavily on reflection and System.Data and other things that are missing some APIs in .NET Core. So that could be done with quite a lot of work. But if .NET Core 2.0 will support referencing old .NET libraries, and it will be released this summer, what is the point of now converting anything to .NET core? |
Can I simply compile it to dll and include into my netcore project? |
I think so, but I also think there is a lot of things to modify, and intellisense and tooling for FSharp .NET Standard is not yet good enough. |
You should first adjust the type provider to be a cross-targeting type provider Then see dotnet/fsharp#3303 |
Can we reopen this thread please? I dont believe that .Net Standard or Core support is finished. As shown by this comment:
|
@charlesroddie this is by design of the TypeProviders. SQLProvider uses those and there is no point of doing our custom implementations. |
@Thorium I'd like to help you get the .NET Core 2.0 tooling type provider completed. Has there been an attempt to do this here so far based on recent updates to the TPSDK and .NET Core F# compiler? |
We are using the latest TPSDK (ProvidedTypes.fs). However I haven't followed the recent .NET Core development, so I don't know if e.g. FscToolPath is still needed and do you still need a .NET framework version of typeprovider dll to compile .NET Core. The help documents reflect the situation about half year ago. People seem in general be able to use SQLProvider with .NET Core 2.0 even though the experience is not as out-of-the-box as .NET tends to be. |
Hi,
Sorry to file this as an issue I didn't find an email or other way to communicate.
Can this provider be used with net core?
I'm getting this error when adding the package
error: Package SQLProvider 1.1.3 is not compatible with netcoreapp1.1 (.NETCoreApp,Version=v1.1). Package SQLProvider 1.1.3 supports: net (.NETFramework,Version=v0.0)
error: One or more packages are incompatible with .NETCoreApp,Version=v1.1.
The text was updated successfully, but these errors were encountered: