Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Support more target frameworks in DiffSharp.fsproj

See original GitHub issue

Right 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 GitHub Comments

2reactions

dsymecommented, Jul 8, 2019

@allisterb I see. Yes, that F# implementation in Azure Notebooks should really be updated…

0reactions

allisterbcommented, Aug 15, 2019

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.

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.

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.

Multiple target framework project: different versions of the ...

A simple way to do it is to add the <PackageReference ...> nodes conditionally: <ItemGroup> <!-- .

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, ...

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 ......