We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy.
Unfortunately, activation email could not send to your email. Please try again.

strong name validation failed !!!!

Thread ID:





45015 Jun 8,2006 09:45 AM Jan 17,2008 10:41 AM General Discussion 6
Tags: General Discussion
Administrator [Syncfusion]
Asked On June 8, 2006 09:45 AM

im getting the message when im trying to run an application that uses Syncfusion controls. im trying to run the application on a customer computer. or when im deploying the application using clickOnce syncfusion started to be annoying!!!!!!!

Jayakumar Natarajan [Syncfusion]
Replied On June 13, 2006 11:35 AM

Hi Rotem, Sorry for the inconvenience. This happens only for the custom built assemblies. Please refer this KB for more details: http://www.syncfusion.com/support/kb/studio/Default.aspx?ToDo=view&questId=16 Thanks, Jay

Administrator [Syncfusion]
Replied On June 14, 2006 02:14 AM

Thanx alot, ill have a look

Administrator [Syncfusion]
Replied On June 14, 2006 04:30 AM

Hi, I did the exact as described in your reference and i get the same error strong key validation failed on syncfusion.shared.base am i missing something? Rotem,

Jayakumar Natarajan [Syncfusion]
Replied On June 14, 2006 05:11 PM

Hi Rotem, I need more details to analyze the issue: 1) Are you using the full version of the Essentail Studio? Or the eval version? Our records indicate that you have only an eval copy. 2) Normally ''strong name validaion'' error is thrown if you modify our library source code (C:\Program Files\Syncfusion\Essential Studio\\windows\Shared.Windows\Src) and deploy the custom libraries without signing with your own public/private key. Have you modified our src. code and built the libraries? Which dlls have you modified - like Syncfusion.Grid.Base.dll, Syncfusion.Grid.Windows.dll, Syncfusion.Shared.Base.dll and Syncfusion.Shared.Windows.dll? Have you signed them all? You may use the following command to verify the assembly for strong name signature self consistency. It should say "Assembly Syncfusion.Shared.Base.dll'' is valid". Sn -vf Syncfusion.Shared.Base.dll In the AssemblyInfo.cs, did you specify the AssemblyDelaySign attribute to "False"? Also refer this help on deploying application: http://www.syncfusion.com/library/startedbase/distributingessential__________.html Regards, Jay

Bharat Gohil
Replied On January 16, 2008 07:30 AM

I am not modifying your code, but still get the error for Syncfusion.Tool.Window.dll

In AssemblyInfo.cs I do not have AssemblyDelaySign attribute specified.

Nandakumar R [Syncfusion]
Replied On January 17, 2008 10:41 AM

Hi Bharat,

Thank you for your interest in Syncfusion Essential Studio. You can get the AssemblyInfo.cs file of the Tools.Windows source from the below location.

${install_drive}:\Program Files\Syncfusion\Essential Studio\\Windows\Tools.Windows\Src\assemblyinfo.cs

Please follow the below steps to build the source using the new private key.

1. Follow the instructions at: http://msdn2.microsoft.com/en-us/library/6f05ezxy.aspx to create your own private key
2. Copy the snk file created (for example eti.snk) to ${install_drive}:\Program Files\Syncfusion\Essential Studio\\Windows\Tools.Windows\
3. Change the AssemblyInfo.cs under ${install_drive}:\Program Files\Syncfusion\Essential Studio\\Windows\Tools.Windows\Src\ to point to this private key instead of the Syncfusion public key that it is pointing to by default:
[assembly: AssemblyDelaySign(true)]
[assembly: AssemblyKeyFile("../../../sf.publicsnk")]

Change above lines to
[assembly: AssemblyDelaySign(false)]
[assembly: AssemblyKeyFile("../../../eti.snk")]

4. Rebuild the Syncfusion.Tools.Windows.dll solution file Syncfusion.Tools.Windows_2005.sln in Release configuration. You will find the output at C:\Program Files\Syncfusion\Essential Studio\\Windows\Tools.Windows\bin\Release.

5. You need to do this for all the sources of Syncfusion which you are making modifications.

Please try this and let us know if you need further help.



This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.