Any plan to support .net core 2

[darting]

Hi there,

Any plan to support .net core 2

Thanks

[rspeele]

I would like to eventually support .NET Core, but do not see it happening soon.

As a generative type provider, Rezoom.SQL is waiting for full support for type providers in .NET core.

[darting]

From this issue dotnet/fsharp#3303 seems we can use Type providers in .net core as long as we change the fsc path in project file?

[rspeele]

I believe that workaround is only for erasing type providers, based on the wording "To convert an erasing type provider to a cross-targeting erasing type provider [... rest of instructions]".

[ashalkhakov]

What is needed to convert a generative TP to an erasing one?

I don't have any experience implementing TPs. But I would like to use Rezoom.SQL on very, very old mobile devices. The kind of devices where raw SQL queries are crucial for performance, and no ORM will cut it.

[rkosafo]

Apparently a lot of work. Looks like a rewrite but not very sure. @rspeele I also have no experience in type providers but could help if pointed in the right direction.

[zaaack]

dotnet/fsharp#2406 (comment) Looks like dotnet core's generative type provider support has made big progress, not sure it's stable now, but just need more weeks?

[AndrewTakker]

@rspeele Any progress in a .net core?:)

[kaeedo]

It seems that with the latest .Net Standard release, Type Providers are now fully supported:
https://blogs.msdn.microsoft.com/dotnet/2018/05/08/f-language-and-tools-update-for-visual-studio-2017-version-15-7/

[rspeele]

Hey guys,

I finally got the motivation to attempt the upgrade. Well, also after I updated VS I lost the project template for .NET Framework F# projects (thanks...) which I take as a signal that I am well behind the times and perhaps the ecosystem is stabilizing.

I've released new versions of LicenseToCIL, FParsec-Pipes, and Rezoom targeting .NET Standard 2.0. These are my other projects that Rezoom.SQL depends on

I think I'm getting close on Rezoom.SQL, but I've hit a bit of a roadblock.

On .NET Framework, I had to do something a bit hacky to get the dependencies to load in "design mode" (i.e. from the compiler or from VS intellisense).

On .NET Standard, the same approach won't work. When I make a .NET core project, the dependencies don't even get copied to the solution folder. They live in ~/.nuget. So my .NET Standard version of the codebase builds fine, but when I try to reference the type provider from another project, it blows up because it can't even find Rezoom.SQL.Mapping and Rezoom.SQL.Compiler... let alone the NuGet dependencies like FParsec.

Maybe I should just change that AssemblyResolver hack so it can go rooting around in ~/.nuget for those. Seems pretty ugly though.

Anybody know what the best practice is for type providers that depend on other NuGet packages?

Edit: I also hacked up something here that's none too pretty. Better ideas are welcome.

[piaste]

@rspeele Maybe see if the way FSharp.Data.Npgsql does it could work for you? It's .NET Standard compatibile and it depends on Npgsql at compile time, but at a quick glance it doesn't seem to rely on assembly-loading code.

[nojaf]

Maybe @KevinRansom has some ideas, I believe he worked on migrating type providers to dotnet core. I could be wrong though.

[nojaf]

Perhaps add a resolution path property similar how SQLProvider for MySQL needs this.

[rkosafo]

@rspeele

How far with this? Is it stable enough for testing?

I just tried it but got the issues below. Now sure if I'm doing something wrong or it's currently not yet ready for .net core

I was testing with sqlite. Issue were as follows

1. Nuget complained System.Data.Sqlite is not available on .net core so is using 4.7.1
2. type MyModel = SQLModel<"./"> is complaining about a missing FParsecCS v1.0.0.0. Couldn't find that library on nuget
3. No rzsql.json was added to the project. I added one but since it was not auto added, I wondered if there was a new approach towards specifying the config.

Do point me in the right direction if there is any assistance with respect to helping with the upgrade to .net core.

Thanks,
R.