[GH-ISSUE #50] Any reason for clearing source linking information? #44

New issue

Closed

opened 2026-02-25 21:30:32 +03:00 by kerem · 3 comments

kerem commented

2026-02-25 21:30:32 +03:00

Owner

Originally created by @paulomorgado on GitHub (Sep 17, 2018).
Original GitHub issue: https://github.com/brutaldev/StrongNameSigner/issues/50

I'm trying to add source linking to a lib but the StrongNameSigner seems to be erasing the source linking information.

Originally created by @paulomorgado on GitHub (Sep 17, 2018). Original GitHub issue: https://github.com/brutaldev/StrongNameSigner/issues/50 I'm trying to add source linking to a lib but the StrongNameSigner seems to be erasing the source linking information.

kerem

2026-02-25 21:30:32 +03:00

closed this issue
added the
wontfix
label

kerem commented

2026-02-25 21:30:32 +03:00

Author

Owner

@brutaldev commented on GitHub (Sep 17, 2018):

Not by design, must be the way Mono.Cecil rewrites the assemblies/PDB files.

@brutaldev commented on GitHub (Sep 17, 2018): Not by design, must be the way Mono.Cecil rewrites the assemblies/PDB files.

kerem commented

2026-02-25 21:30:32 +03:00

Author

Owner

@paulomorgado commented on GitHub (Sep 17, 2018):

Looks like it was a problem, but has been solved.

@paulomorgado commented on GitHub (Sep 17, 2018): Looks like it was a [problem](https://github.com/jbevain/cecil/issues/412), but has been [solved](https://github.com/jbevain/cecil/pull/432).

kerem commented

2026-02-25 21:30:32 +03:00

Author

Owner

@brutaldev commented on GitHub (Sep 25, 2019):

This may have been fixed up now after adding the latest version of Mono.Cecil in v2.4

@brutaldev commented on GitHub (Sep 25, 2019): This may have been fixed up now after adding the latest version of Mono.Cecil in [v2.4](https://github.com/brutaldev/StrongNameSigner/releases/tag/2.4.0)