Paket.pack: add support for nuget dependencies conditional on target framework

[eiriktsarpalis]

As of Nuget 2.0, support for package dependencies that that are bound to specific target frameworks has been included. For instance:

<dependencies> 
   <group>
      <dependency id="RouteMagic" version="1.1.0" />
   </group>

   <group targetFramework="net40">
      <dependency id="jQuery" />
      <dependency id="WebActivator" />
   </group>

   <group targetFramework="sl30">
   </group>
</dependencies>

I'm not entirely sure how this feature would fit in with the design philosophy of paket, but I'd be interested to see having something like this added to the paket.template syntax.

[forki]

First question: how could this look in our current paket.template syntax?

/cc @mavnn

[eiriktsarpalis]

I guess it could be worked out like this:

dependencies
    RouteMagic 1.1.0
dependencies targetFramework=net40
    jQuery
    WebActivator

I have a few misgivings on the compatibility of this feature with the overall paket design philosophy. For example:

dependencies targetFramework=net35
    Newtonsoft.Json ~> 4.0
dependencies targetFramework=net40
    Newtonsoft.Json ~> 5.0

requires that two separate versions of the same package be present in one environment, which AFAIK is not supported by paket.

[forki]

yes.

dependencies targetFramework=net35
    Newtonsoft.Json ~> 4.0
dependencies targetFramework=net40
    Newtonsoft.Json ~> 5.0

would be problematic, but only if your app uses both targetFrameworks. If not you can resolve the conflict with paket.

[enricosada]

with new TFM (target framework monikers) and .NET Core that's going to be really useful (needed?) because for some frameworks the library/app depends on different packages.

Some examples:

• some bcl assemblies are split in multiple assemblies/packages. So in .net 4.5 is a package, in .net core multiple packages
• FSharp.Core for .NET Core in a different package ( Microsoft.FSharp.Core.netcore ) instead of FSharp.Core package (but that should be temporary i hope)

for example Chessie fsprojects/Chessie#43 ( .NET 4.6 and .NET Core with dnxcore50 atm but i am going to move it to netstandard asap )

[davidschwegler]

We can't use paket to make nuget packages without this, since we have Xamarin packages (which of course use multiple frameworks, and our iOS frameworks obviously can't depend on Android dependencies).

[cdrnet]

I have a need for this as well. But I'll also have to specify empty groups to be able to end up with the following:

<dependencies>
    <group targetFramework=".NETFramework3.5">
        <dependency id="TaskParallelLibrary" version="1.0.2856" />
    </group>
    <group targetFramework=".NETFramework4.0" />
</dependencies>

Maybe this could then become:

dependencies targetFramework=net35
    TaskParallelLibrary >= 1.0.2856
dependencies targetFramework=net40

[Thorium]

Type OptionalPackagingInfo at TemplateFile.fs has Dependencies and FrameworkAssemblyReferences, instead of having a list, they should have a map or tuple of groupname*list pairs.

The framework assemblies also have this targetFramework:

<frameworkAssemblies>
  <frameworkAssembly assemblyName="mscorlib" targetFramework=".NETFramework4.6.3" />
  <frameworkAssembly assemblyName="System.Core" targetFramework=".NETFramework4.5" />
  <frameworkAssembly assemblyName="System.Core" targetFramework=".NETFramework4.6.3" />
</frameworkAssemblies>

[seanamosw]

I see #2428 was merged, I haven't been able to figure out a way to generate:

<group targetFramework="net451" />

Basically specify no dependencies for a target framework.

[matthid]

@seanamosw Please open a new issue if this is still the case.