[PR #111] [CLOSED] Fix failure to save assembly #110

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

📋 Pull Request Information

Original PR: https://github.com/brutaldev/StrongNameSigner/pull/111
Author: @vitaly-cyberhaven
Created: 2/17/2026
Status: Closed

Base: masterHead: issue/110-fix-file-in-use


📝 Commits (2)

  • 5019401 Fix #110: Added caching assembly resolver
  • 13daeb9 Fix #110: SigningHelper: register assembly with the caching resolver

📊 Changes

3 files changed (+54 additions, -32 deletions)

View changed files

📝 src/Brutal.Dev.StrongNameSigner/AssemblyInfo.cs (+31 -31)
src/Brutal.Dev.StrongNameSigner/CachingAssemblyResolver.cs (+12 -0)
📝 src/Brutal.Dev.StrongNameSigner/SigningHelper.cs (+11 -1)

📄 Description

This fixes the issue https://github.com/brutaldev/StrongNameSigner/issues/110

The following project should demonstrate the issue:

StrongNameSignerTest.zip


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/brutaldev/StrongNameSigner/pull/111 **Author:** [@vitaly-cyberhaven](https://github.com/vitaly-cyberhaven) **Created:** 2/17/2026 **Status:** ❌ Closed **Base:** `master` ← **Head:** `issue/110-fix-file-in-use` --- ### 📝 Commits (2) - [`5019401`](https://github.com/brutaldev/StrongNameSigner/commit/5019401dd1cd74fead257bbe2701e081226d5ff8) Fix #110: Added caching assembly resolver - [`13daeb9`](https://github.com/brutaldev/StrongNameSigner/commit/13daeb9ebe5f3ede0c7c0721c27ffc72747626ec) Fix #110: SigningHelper: register assembly with the caching resolver ### 📊 Changes **3 files changed** (+54 additions, -32 deletions) <details> <summary>View changed files</summary> 📝 `src/Brutal.Dev.StrongNameSigner/AssemblyInfo.cs` (+31 -31) ➕ `src/Brutal.Dev.StrongNameSigner/CachingAssemblyResolver.cs` (+12 -0) 📝 `src/Brutal.Dev.StrongNameSigner/SigningHelper.cs` (+11 -1) </details> ### 📄 Description This fixes the issue https://github.com/brutaldev/StrongNameSigner/issues/110 The following project should demonstrate the issue: [StrongNameSignerTest.zip](https://github.com/user-attachments/files/25368241/StrongNameSignerTest.zip) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-02-25 21:30:44 +03:00
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#110
No description provided.