You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/Brutal.Dev.StrongNameSigner.Setup/StrongNameSigner.nuspec
+1-2Lines changed: 1 addition & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -20,8 +20,7 @@ The tool will also re-write the assembly references (as well as any InternalsVis
20
20
</description>
21
21
<summary>Automatic strong-name signing of referenced assemblies. Utility software to strong-name sign .NET assemblies, including assemblies you do not have the source code for.</summary>
22
22
<releaseNotes>
23
-
Update custom attribute fixing to include every custom attribute (PR #104).
24
-
Add more environment specific resolution paths to try and solve (Issue #103/105).
23
+
Fix issue #107 by handling custom attribute fixing for multiple versions of the same assembly with the same name.
Log($" Fixing {signedAssembly.Definition.Name.Name} reference in CustomAttribute in assembly '{tempFilePathToInputOutputFilePairMap[assembly.FilePath].InputFilePath}'.");
591
+
Log($" Fixing {signedAssembly.Name.Name} reference in CustomAttribute in assembly '{tempFilePathToInputOutputFilePairMap[assembly.FilePath].InputFilePath}'.");
// Import the type reference into the current module, so it gets the correct scope.
584
596
// Without this import, the type reference in the ILASM will only point to the type (like "Brutal.Dev.StrongNameSigner.TestAssembly.A.A")
585
597
// instead of the full assembly-qualified name (like "Brutal.Dev.StrongNameSigner.TestAssembly.A.A, Brutal.Dev.StrongNameSigner.TestAssembly.A, Version=1.0.0.0, PublicKeyToken=...").
0 commit comments