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

StrongNamer doesn't work when used with Central Package management #68

Open
doxxx opened this issue Jan 3, 2025 · 0 comments
Open

StrongNamer doesn't work when used with Central Package management #68

doxxx opened this issue Jan 3, 2025 · 0 comments

Comments

@doxxx
Copy link

doxxx commented Jan 3, 2025

I have a solution that uses Central Package Management: project files have version-less PackageReference elements and the Directory.Package.props file defines PackageVersion elements for all references packages. If I add a StrongNamer package reference to one of the projects, that project fails to restore/build with the error error NU1008: Projects that use central package version management should not define the version on the PackageReference items but on the PackageVersion items.

I'm guessing that StrongNamer is modifying the PackageReference(s) for the package(s) it is adding strong names to, and add a Version attribute.

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

No branches or pull requests

1 participant