Target lower .NET Standard about giraffe

[davidfowl]

Hmmmmm, we should figure out why

[dustinmoris]

Hi David, as far as I know I had to target >= 1.6 because FSharp.Core doesn't target anything lower.

[dustinmoris]

It could be a remainder from the previous Microsoft.FSharp.Core.netcore package which was the FSharp NuGet lib for .NET Core while it was still in development. Perhaps it is as simple as they didn't bother with targeting anything lower than 1.6 whilst in development and now forgot to check if they can actually target a lower version. I will see if I find something otherwise I can open an issue and ask.

[slang25]

I've just had a go at this on the train. We can use one of the PCL profiles, which line up to 1.0 & 1.1, then ourselves target netstandard 1.3. However I've tried the following and the packages won't restore:

<TargetFramework>netstandard1.3</TargetFramework>
<PackageTargetFallback Condition=" '$(TargetFramework)' == 'netcoreapp1.3' ">$(PackageTargetFallback);portable-net45+win8;</PackageTargetFallback>

@davidfowl is my understanding correct? Any suggestions?

[slang25]

Also, in the package description for FSharp.Core the bits in the brackets don't appear to be the official TFMs, or am I wrong about that?

[dustinmoris]

Reopening because #6 has added RazorLight which targets NETStandard 1.6 again. I have opened an issue to lower it at least to NETStandard 1.5.

In the interim I could move the razor handler into a 2nd assembly (e.g. AspNetCore.Lambda.Razor) if you think there's a lot of value to keep the main package targeting 1.3 now @slang25?

[enricosada]

@dustinmoris FSharp.Core will not be lowered, see dotnet/fsharp#2501

[TheAngryByrd]

Well if we can't target a lower netstandard, how about targeting net451 as well like Kestrel?

[davidfowl]

Meh, might not be worth it at this point. Kestrel has also changed to target net46

[dustinmoris]

ok thanks everyone, I will close this issue then.