1-click应用验证失败：Mono.Cecil.dll强名称签名无效问题求助

Let’s work through this problem systematically—since you’re dealing with legacy code and mixed user results, we need to address both the signature validation error and the broken functionality for some users.

1. First, Figure Out Why Mono.Cecil.dll Is in Your Project #

Since you inherited this code and don’t know its purpose, start by tracking down where it’s used:

• Check project references & NuGet packages: Look for any packages that list Mono.Cecil as a dependency—common culprits are code analysis tools, AOP frameworks (like PostSharp), or build tasks that inspect/modify assemblies during compilation.
• Search your codebase: Do a full search for using Mono.Cecil; or calls to Cecil’s core APIs (like AssemblyDefinition.Load or ModuleDefinition). This will tell you if the app uses it at runtime, not just during builds.
• Dig into build logs: Check your post-build steps or MSBuild scripts—sometimes Cecil is used in build-time tasks even if it’s not referenced directly in your code.

2. Fix the Strong Name Signature Error #

The root issue here is the invalid strong name on Mono.Cecil.dll, which triggers the InvalidDeploymentException. Here are actionable fixes:

• Re-sign the assembly: If you have your application’s strong name key (.snk file), use the sn.exe tool to re-sign Mono.Cecil.dll to match your app’s signature:

  sn -R Mono.Cecil.dll YourAppStrongNameKey.snk
  

  Update your project reference to use this re-signed DLL afterward.
• Temporarily skip validation for affected users: For users still hitting the error, you can have them run this admin command to disable strong name checks for Mono.Cecil (replace the token with the actual one from your DLL—get it via sn -T Mono.Cecil.dll):

  sn -Vr *,<MonoCecilPublicKeyToken>
  

  Note this is a machine-wide setting, so it’s a workaround, not a permanent fix.
• Switch to an official signed package: If you’re using an unsigned copy of Mono.Cecil, replace it with the official signed NuGet package. The official Mono.Cecil package is properly signed, which should eliminate the validation error.

3. Restore Broken Functionality for Affected Users #

Excluding Mono.Cecil.dll fixed the validation error for most users, but broke features for others because those features depend on it. Here’s how to fix that:

• Include the validly signed DLL in deployment: Go back to Visual Studio’s Properties > Publish > Application Files, set Mono.Cecil.dll to Include (Auto) instead of Exclude. Make sure you’re using the re-signed or official signed version so the validation passes.
• Pinpoint dependent features: Work with the affected users to identify exactly which features are broken. Cross-reference that with your code search results for Mono.Cecil—this will tell you exactly what functionality relies on the DLL (e.g., runtime plugin loading, dynamic code generation).
• Last resort: Replace Cecil functionality: If you can’t resolve the signature issue, look for alternative libraries or rewrite the code that uses Mono.Cecil. But this is only recommended if all other options fail, since it involves modifying legacy code.

4. Avoid This Issue in the Future #

• Document the dependency: Once you figure out why Mono.Cecil is included, add comments to your project or internal docs so future maintainers don’t face the same confusion.
• Add build-time checks: Set up a step in your build process to verify that all referenced assemblies have valid strong names matching your app’s signing requirements. This will catch issues before you deploy.

内容的提问来源于stack exchange，提问作者dome_engineer