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

NuGet should add support for /runtimes/{rid}/nativeassets/{txm}/ #2782

Closed
ericstj opened this Issue May 13, 2016 · 4 comments

Comments

Projects
None yet
3 participants
@ericstj

ericstj commented May 13, 2016

When we initially added the runtimes support this was excluded because corefx didn't have any scenarios for it. There are folks that need this. Native binaries can take a dependency on aspects of the {txm}, like WinRT surface area in the case of uap10.x, hosting-APIs/runtimes in the case of net4x.

We've discussed using/mis-using runtimes/{rid}/lib/{txm} for this but that won't work in all cases because the CLI treats native assets differently than lib and any native asset applicable for a core app must be in the native folder.

See dotnet/corefx#8478.

@ericstj

This comment has been minimized.

Show comment
Hide comment

ericstj commented May 13, 2016

/cc @emgarten

@rrelyea rrelyea added this to the 3.5 RC milestone May 16, 2016

@rrelyea rrelyea modified the milestones: 3.5 Beta2, 3.5 RC May 31, 2016

@rrelyea rrelyea changed the title from NuGet should add support for /runtimes/{rid}/native/{txm}/ to NuGet should add support for /runtimes/{rid}/nativeassets/{txm}/ Jun 6, 2016

@rrelyea

This comment has been minimized.

Show comment
Hide comment
@rrelyea

rrelyea Jun 6, 2016

Contributor

@ericstj - after talking with @emgarten, we are leaning towards: "nativeassets".
We also discussed that /runtimes/{rid}/native/ would be treated as the "any" folder that we discussed on Friday.
Make sense?

Contributor

rrelyea commented Jun 6, 2016

@ericstj - after talking with @emgarten, we are leaning towards: "nativeassets".
We also discussed that /runtimes/{rid}/native/ would be treated as the "any" folder that we discussed on Friday.
Make sense?

@ericstj

This comment has been minimized.

Show comment
Hide comment
@ericstj

ericstj Jun 7, 2016

It's ok, the reason we said "assets" in the meeting was that folks in practice were using this folder for anything that they wanted to be RID specific but not have the lib extension filter applied. I'm ok with nativeassets.

ericstj commented Jun 7, 2016

It's ok, the reason we said "assets" in the meeting was that folks in practice were using this folder for anything that they wanted to be RID specific but not have the lib extension filter applied. I'm ok with nativeassets.

@emgarten

This comment has been minimized.

Show comment
Hide comment
Contributor

emgarten commented Jun 11, 2016

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