fix: disable strong naming for source generator assembly #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Source generators run in the compiler/IDE process and should not be strong-named. This fixes the Windows .NET Framework 4.7.2 test failures where the generator DLL was being signed with the same key as the main library, causing strong name verification errors. Co-authored-by: sensslen <[email protected]>
Copilot
AI
changed the title
[WIP] Fix strong naming issue in Windows test run
fix: disable strong naming for source generator assembly
Feb 5, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Source generators were inheriting
SignAssembly=truefromDirectory.Build.props, causing strong name verification failures on .NET Framework 4.7.2:Changes
SignAssemblytofalseinCommandLineUtils.Generators.csprojSource generators run in the compiler process and should not be strong-named. Only the runtime libraries (
McMaster.Extensions.CommandLineUtils,McMaster.Extensions.Hosting.CommandLine) need strong naming.Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.