Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for target framework specific content #1300

Open
Haydabase opened this issue Dec 9, 2015 · 4 comments
Open

Support for target framework specific content #1300

Haydabase opened this issue Dec 9, 2015 · 4 comments

Comments

@Haydabase
Copy link
Contributor

NuGet allows packages to specify different content files for different frameworks: Grouping content files and PowerShell scripts by target framework

But Paket doesn't seem to support adding only the content files in a target framework dependant way. For example, when I install System.Data.SQLite.Core I get all content for all different frameworks added, which doesn't work:
image

I would expect to just have the x86 and x64 for the current target framework. Perhaps this can be done using the conditional method like target framework specific DLL references?

@tigerclawn82
Copy link

Hi,
Is there any update on this issue? I am using Paket and i need support for adding dependencies based upon CPU Architecture. I have project which uses HTTP dependencies and those need to be pulled based upon x64,x86, Any CPU. is there any way that can be done?
Thanks

@forki
Copy link
Member

forki commented Aug 30, 2016

I think this is possible with the file template mode.

@tigerclawn82
Copy link

There is support for Framework restrictions mentioned in the http://fsprojects.github.io/Paket/references-files.html.
Can that be extended to CPU Architecture? As it seems natural to restrict certain references there as it is already there to make these kind of stuff happen

@tigerclawn82
Copy link

I checked https://fsprojects.github.io/Paket/template-files.html, it states to be used for Nuget pkgs. Am i missing something?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants