[GH-ISSUE #34] Caching problem #28

New issue

Closed

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

kerem commented

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

Owner

Originally created by @GieltjE on GitHub (Apr 28, 2017).
Original GitHub issue: https://github.com/brutaldev/StrongNameSigner/issues/34

Originally assigned to: @brutaldev on GitHub.

When getting the AssemblyInfo for a file the result is somehow cached.

Reproduce, start with a signed assembly, run the code below, replace with unsigned assembly run code again (without closing the application):
AssemblyInfo assemblyInfo = SigningHelper.GetAssemblyInfo(file);
if (assemblyInfo.IsSigned) { MessageBox.Show("signed"); }
else { SigningHelper.SignAssembly(....); }

Originally created by @GieltjE on GitHub (Apr 28, 2017). Original GitHub issue: https://github.com/brutaldev/StrongNameSigner/issues/34 Originally assigned to: @brutaldev on GitHub. When getting the AssemblyInfo for a file the result is somehow cached. Reproduce, start with a signed assembly, run the code below, replace with unsigned assembly run code again (without closing the application): AssemblyInfo assemblyInfo = SigningHelper.GetAssemblyInfo(file); if (assemblyInfo.IsSigned) { MessageBox.Show("signed"); } else { SigningHelper.SignAssembly(....); }

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 (Apr 29, 2017):

The assembly details are indeed cached, but it should really be cleared if you run the process from the beginning again. Will make this update and release a new version over the weekend.

@brutaldev commented on GitHub (Apr 29, 2017): The assembly details are indeed cached, but it should really be cleared if you run the process from the beginning again. Will make this update and release a new version over the weekend.

kerem commented

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

Author

Owner

@GieltjE commented on GitHub (Apr 29, 2017):

The problem is that our process remains running for weeks at a time (custom build & release tool).

Good to hear there is a patch inbound 👍

@GieltjE commented on GitHub (Apr 29, 2017): The problem is that our process remains running for weeks at a time (custom build & release tool). Good to hear there is a patch inbound 👍

kerem commented

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

Author

Owner

@brutaldev commented on GitHub (Apr 30, 2017):

This should be fixed up in release 2.1.2.

The file is hash checked first to ensure the cached version is still pointing to the same file.

@brutaldev commented on GitHub (Apr 30, 2017): This should be fixed up in release [2.1.2](https://github.com/brutaldev/StrongNameSigner/releases/tag/v2.1.2). The file is hash checked first to ensure the cached version is still pointing to the same file.