search

fsprojects / FSharp.Configuration

The FSharp.Configuration project contains type providers for the configuration of .NET projects.
http://fsprojects.github.io/FSharp.Configuration/
Other
114 stars 63 forks source link

Provide a .NET Standard compatible build on nuget #127

Closed pkese closed 2 years ago

pkese commented 7 years ago

This package is only available as for dotnet 4.5 and can't be used in modern .Net Core / .Net Standard enironments (Linux...).

Is there a reason it can't be provided as Netstandard compatible.

vasily-kirichenko commented 7 years ago

It's possible if SharpYaml package is Core compatible.

pkese commented 7 years ago

Yes,
SharpYaml is compatible with NetStandard 1.6
https://www.nuget.org/packages/SharpYaml/

sergey-tihon commented 7 years ago

How is it possible? I thought that TP does not work yet on .NET Core - https://github.com/Microsoft/visualfsharp/issues/2406

@vasily-kirichenko Do you know at least one (erased) TP that is compiled to .net standard and work on .net core?

vasily-kirichenko commented 7 years ago

Ah, I don't follow .NET Core news, I thought TPs are already supported.

forki commented 7 years ago

@vasily-kirichenko no they are not.

tylerhartwig commented 5 years ago

I noticed there are alpha releases for .netstandard on nuget.

What is the state of those builds? How functional are they on netstandard?

sergey-tihon commented 5 years ago

@tylerhartwig plz, try it and tell us ;)

It is in alpha because it is does not contain ResXProvider at the moment and there is no way auto-magically load web.config.

YamlConfigTypeProvider, IniFileProvider & AppSettingsTypeProvider should be in perfect shape (as good as before).

baronfel commented 5 years ago

I had issues with the yamlprovider in Rider and vscode with regards to intellisense, but they compiled perfectly.

sergey-tihon commented 5 years ago

@baronfel what sorts of issues you had? Performance? IIRC, current alpha does not contain caching for provided types. Can it be related?

baronfel commented 5 years ago

It was always just red squigglies for unknown members on the generated type. Just a design time issue, though! One of the many things I hadn't found time to run down.

tylerhartwig commented 5 years ago

Ah I'd love to try it out and let yall know, however I was hoping to try out the resx :D

Is that piece started? What does the work on that look like?

sergey-tihon commented 5 years ago

@tylerhartwig yes, take a look here https://github.com/fsprojects/FSharp.Configuration/pull/139#issuecomment-448216452

the original implementation is heavily rely on winforms that is not net-standard thing =(

sergey-tihon commented 5 years ago

We also can ask @Liminiens opinion on how far we are ;)

Liminiens commented 4 years ago

@sergey-tihon i beleive it is be possible to target net core 3.0 for resx provider since it has win forms bits, but it needs some research

sergey-tihon commented 4 years ago

@Liminiens maybe, but it anyway will be win-only. right?

Liminiens commented 4 years ago

yes :)

jkone27 commented 3 years ago

any news on .netstandard porting effort ? maybe YAML type provider should be in the main FSharp.Data library?

sergey-tihon commented 3 years ago

@jkone27 have you tried 2.0.0-alpha2? It contains .net standard version of YAML type provider

jkone27 commented 3 years ago

Will give it a try, thanks a lot @sergey-tihon 👍

jkone27 commented 2 years ago

just a thought, but any thoughts of migrating it to FSharp.Data ? i think it could prove very useful and maybe it's a nicer fit there, or have a separate package/repo like FSharp.Data.Yaml ? Have a really nice day!