Support more target frameworks in DiffSharp.fsproj
See original GitHub issueRight now only the netstandard2.0 target framework is supported by the DiffSharp project file. This causes build failures in libraries that use DiffSharp and must support net45 and older .NET frameworks and toolchains. Both NET Standard 2.0 and other targets can be supported by using this line in DiffSharp.fsroj
<TargetFrameworks>netstandard2.0;netcoreapp2.0;net45</TargetFrameworks>
I built DiffSharp successfully for these targets without any changes to the source code and the tooling will take care of sorting out the dependencies and packaging the libraries correctly for NuGet.
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (2 by maintainers)
Top Results From Across the Web
Support multiple .NET Framework versions in your project file
Description of the various methods to target multiple .NET Framework versions from within a single NuGet package in your project file.
Read more >Target frameworks in SDK-style projects - .NET
The following table shows the target frameworks supported by the .NET SDK and the NuGet client. Equivalents are shown within brackets.
Read more >Multiple target framework project: different versions of the ...
A simple way to do it is to add the <PackageReference ...> nodes conditionally: <ItemGroup> <!-- .
Read more >Try infer current target framework, if multiple ...
If fsproj use netstandard1.6;net40 can build both target frameworks. But because fsc args (used to initialize FCS) are framework specific, ...
Read more >NuGet exception with TargetFrameworks set in f# proj ...
Yes we should definitely understand why the targets aren't imported when cross-targeting. That seems weird to me but I'm sure there's a logical ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@allisterb I see. Yes, that F# implementation in Azure Notebooks should really be updated…
Oh ok if I can restore it on Azure Notebooks then that’s all I need. I’ll close this for now. Thanks for the response.