[GH-ISSUE #35] 2.1.1 SignAssembly Keeps files locked #32

New issue

Closed

opened 2026-02-25 21:30:30 +03:00 by kerem · 1 comment

kerem commented

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

Owner

Originally created by @GieltjE on GitHub (May 1, 2017).
Original GitHub issue: https://github.com/brutaldev/StrongNameSigner/issues/35

Originally assigned to: @brutaldev on GitHub.

2.1.0 works great, but in 2.1.1 after calling SignAssembly(....) the file remains locked untill the application is closed.

E.g. we use a temporary directory to sign files, signing the same dll for multiple DotNet versions causes problems as we cannot delete them after signing.

Originally created by @GieltjE on GitHub (May 1, 2017). Original GitHub issue: https://github.com/brutaldev/StrongNameSigner/issues/35 Originally assigned to: @brutaldev on GitHub. 2.1.0 works great, but in 2.1.1 after calling SignAssembly(....) the file remains locked untill the application is closed. E.g. we use a temporary directory to sign files, signing the same dll for multiple DotNet versions causes problems as we cannot delete them after signing.

kerem

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

closed this issue
added the
bug
label

kerem commented

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

Author

Owner

@brutaldev commented on GitHub (May 1, 2017):

Fixed up in release 2.1.2. Updated to a new version of Mono.Cecil which seems to hold file locks so this release just reverts back to the trusty stable release.

@brutaldev commented on GitHub (May 1, 2017): Fixed up in release [2.1.2](https://github.com/brutaldev/StrongNameSigner/releases/tag/v2.1.2). Updated to a new version of Mono.Cecil which seems to hold file locks so this release just reverts back to the trusty stable release.

kerem referenced this issue

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

[GH-ISSUE #40] Operation is not valid due to the current state of the object. #35