[GH-ISSUE #4] Fix references when alternative output directory is provided. #3

Closed
opened 2026-02-25 21:30:26 +03:00 by kerem · 2 comments
Owner

Originally created by @bentayloruk on GitHub (Jan 19, 2014).
Original GitHub issue: https://github.com/brutaldev/StrongNameSigner/issues/4

Originally assigned to: @brutaldev on GitHub.

If you select an alternative output directory for the signed assemblies, then references are not fixed up (as the method looks at the previous unsigned version in the source path and considers it a no-op).

I was going to submit a PR, but don't have time right now, so logged this here.

Originally created by @bentayloruk on GitHub (Jan 19, 2014). Original GitHub issue: https://github.com/brutaldev/StrongNameSigner/issues/4 Originally assigned to: @brutaldev on GitHub. If you select an alternative output directory for the signed assemblies, then references are not fixed up (as the method looks at the previous unsigned version in the source path and considers it a no-op). _I was going to submit a PR, but don't have time right now, so logged this here._
kerem 2026-02-25 21:30:26 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@brutaldev commented on GitHub (Jan 19, 2014):

Thanks for reporting this, it's been fixed up in v1.3.0.0.

<!-- gh-comment-id:32714072 --> @brutaldev commented on GitHub (Jan 19, 2014): Thanks for reporting this, it's been fixed up in v1.3.0.0.
Author
Owner

@bentayloruk commented on GitHub (Jan 21, 2014):

Thanks!

<!-- gh-comment-id:32899707 --> @bentayloruk commented on GitHub (Jan 21, 2014): Thanks!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/StrongNameSigner#3
No description provided.