Strong name signature not valid for this assembly FontAwesome.Sharp.dll
Pherax opened this issue · comments
Describe the bug
I am trying to build my first application in visual studio 2022 using c# .net framework. The program runs fine in the IDE but when I publish it to run the .exe i get the following error.
ERROR DETAILS
Following errors were detected during this operation.
* [19/01/2022 17:07:04] System.Deployment.Application.InvalidDeploymentException (SignatureValidation)
- Strong name signature not valid for this assembly FontAwesome.Sharp.dll.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.ComponentVerifier.VerifyStrongNameAssembly(String filePath, AssemblyManifest assemblyManifest)
at System.Deployment.Application.ComponentVerifier.VerifyComponents()
at System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl, Uri& deploymentUri)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivationWithRetry(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivationWithRetry(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
Desktop (please complete the following information):
- OS: W10
PLATFORM VERSION INFO
Windows : 10.0.19044.0 (Win32NT)
Common Language Runtime : 4.0.30319.42000
System.Deployment.dll : 4.8.4270.0 built by: NET48REL1LAST_C
clr.dll : 4.8.4420.0 built by: NET48REL1LAST_C
dfdll.dll : 4.8.4270.0 built by: NET48REL1LAST_C
dfshim.dll : 10.0.19041.1 (WinBuild.160101.0800)
I got the same issue suddenly.
The way to fix is to uninstall FontAwesome.Sharp and install FontAwesome.Sharp.StrongName
Hi @Pherax and @TapusAggarwal ,
Thanks for pointing that out. Strong naming should already have been addressed in
Let's have a look about what is missing.
Verified current build. Strong name key present & valid
Verified against the latest package, net48-runtime. Looks good to me as well
Could you verify using the methods described in
- https://blog.codingoutloud.com/2010/03/13/three-ways-to-tell-whether-an-assembly-dl-is-strong-named/
Is it that in your deployment scenario you probably need a digitally verified signature using
Hi. I got the same issue.
We will add strong name signing in v6+
Fixed in 6