Skip to content

Conversation

@Onzi12
Copy link

@Onzi12 Onzi12 commented Oct 15, 2021

The pull request adds an explanation on:

  1. Where one should add the StrongNamer package, especially in a multi-project Solution.
  2. How one can successfully release his package with "new" tools (dotnet pack or MSBuild option -t:pack)

I have both of these scenarios, and solving the problem was not trivial, primarily due to the nature of the failures to be raised only at specific scenarios at runtime (when the unsigned code runs for the first time)

@Onzi12
Copy link
Author

Onzi12 commented Oct 15, 2021

The pipeline failure is not related to my change.
I only changed the README.md file and the failure is on the Build process.

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

Successfully merging this pull request may close these issues.

1 participant