I work on a project that supports "FSharp.Core" Version="3.1.2.5" in its net461 variant and makes use of this in samples; relaxing the constraints as this PR does means I can compile those without warnings. I have a similar need/desire to include this in a dotnet new template and having maximal reach is critical in that context.
[x] reduce .NET Core target to netcoreapp2.1 in order to verify current LTS version works correctly
[x] add net461 multitargeting to tests - I'm fine with this being removed or changed to net45 if it proves problematic; IME net461 targeting is commonly with default SDK/VS installs
[x] reduce FSharp.Core version requirement for net45 to Version="3.1.2.5"
[x] increase FSharp.Core version requirement for netstandard2.0 to Version="4.3.4" (was 4.1.17) - happy to remove this change as TBH I'm not sure how enricosada landed on this
I work on a project that supports
"FSharp.Core" Version="3.1.2.5"in itsnet461variant and makes use of this in samples; relaxing the constraints as this PR does means I can compile those without warnings. I have a similar need/desire to include this in adotnet newtemplate and having maximal reach is critical in that context.netcoreapp2.1in order to verify current LTS version works correctlynet461multitargeting to tests - I'm fine with this being removed or changed tonet45if it proves problematic; IMEnet461targeting is commonly with default SDK/VS installsFSharp.Coreversion requirement fornet45toVersion="3.1.2.5"FSharp.Coreversion requirement fornetstandard2.0toVersion="4.3.4"(was4.1.17) - happy to remove this change as TBH I'm not sure how enricosada landed on this