Repository navigation
Strong-name the assemblies - #72
David Federman (dfederm) wants to merge 4 commits into
Conversation
64e12a6 to
d72461f
Compare
d72461f to
6d37000
Compare
|
David Federman (@dfederm) Are we okay to still merge this, even if we're blocked with upstream dependencies? EDIT: Nope! Moving this to draft for now. |
|
I opened a PR upstream dotnet/Docker.DotNet#567 |
|
PR merged upstream. Waiting for a release now. |
|
Version |
|
See #453 |
|
David Federman (@dfederm) can you rebase this branch please? I don't have permissions to push to your fork, but I've created a branch you can reset to: We're getting closer, but the build still fails due to a lack of strong named assemblies for Tomlyn and Valleysoft.DockerfileModel. I've created issues upstream: I'll also create pull requests when I have time. |
d1bfe08 to
79dba66
Compare
|
Closing for now as unneeded, but we can revisit if there is more need for strong-naming in the future. |
This strong-names the assemblies so that applications which are themselves strong-named can use these libraries.
The snk file was generated by running:
sn -k StrongName.snk