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

Update packaging (probably release as strong-name only) #18

Closed
reisenberger opened this issue May 2, 2018 · 3 comments
Closed

Update packaging (probably release as strong-name only) #18

reisenberger opened this issue May 2, 2018 · 3 comments
Labels
packaging / dependencies An issue affecting packaging or dependencies
Milestone

Comments

@reisenberger
Copy link
Member

reisenberger commented May 2, 2018

In line with App-vNext/Polly#442

EDIT: Now addressed by #19, #21, #22

@reisenberger reisenberger added the packaging / dependencies An issue affecting packaging or dependencies label May 2, 2018
@reisenberger reisenberger added this to the v2.0.0 milestone May 29, 2018
@af4jm
Copy link

af4jm commented Jun 5, 2018

Microsoft.Extensions.Http.Polly references Polly 6.0.1 which is signed while this package references Polly 5.9 which is unsigned, making it impossible for a project to reference both NuGet packages.

@reisenberger
Copy link
Member Author

We are hoping to release the updated package in the next few days. Pending that, you can build against a version of the new package immediately by running the build locally from the v20dev branch. This will create a .nupkg in the \artifacts\nuget-package folder which is expected to be identical to the released package, except in naming/numbering.

@reisenberger
Copy link
Member Author

Closed by #22 . The new package is released on nuget

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
packaging / dependencies An issue affecting packaging or dependencies
Projects
None yet
Development

No branches or pull requests

2 participants