Create packages with multiple RuntimeIdentifiers cross-platform build

livarcocc commented 6 years ago

From @xen2 on March 1, 2018 2:9

Using <TargetFrameworks> results in multiple builds and is properly supported by NuGet pack (lib/<tfm>) and Visual Studio.

However, <RuntimeIdentifiers> doesn't seem to have much impact except for package consumption. I was expecting to also be able to create such NuGet packages, with runtimes/<runtime>/lib/<tfm> folders.

For the use case, I would like to develop a library that support this kind of combination of TFM/Runtime identifiers:

monoandroid50 (no runtime identifier)
net461 (windows)
net461 (unix)
net461 (macos)
xamarinios10
uap10.0

Note that runtime identifiers are different for each TFM.

Is the only choice to develop custom cross-targeting targets myself, or will it be supported in nuget/dotnet/vs at some point?

Copied from original issue: dotnet/sdk#2009

livarcocc commented 6 years ago

pack is actually maintained by NuGet. I will move this to nuget/home to see if we can get a better answer regarding when this can be supported.

nkolev92 commented 6 years ago

@rohit21agrawal Thoughts?

rohit21agrawal commented 6 years ago

would definitely love to design this scenario. so far there hasn't been much need for this, but looks like that's changed now. Let's schedule some time to discuss and design this.

xen2 commented 6 years ago

Thanks for considering it!

I have a bunch of other issues/use cases I would need solved before we could switch our custom build system to vanilla NuGet. I will open a meta issue regrouping them.

clairernovotny commented 6 years ago

I've implemented this with my Extras here: https://github.com/onovotny/MSBuildSdkExtras#creating-per-runtimeidentifier-packages

NuGet / Home

Create packages with multiple RuntimeIdentifiers cross-platform build #6633