[[ Strong name validation failed for assembly ]]
First of all, I am sorry for posting this two times. I have posted this inMSDN ForumsVisual C#Visual C# General but it seems that no body is interested in this subject or i have posted in the wrong forum.
I have used ExeShield to protect my application. (http://www.exeshield.com/)
- There isno problem when i try to protect Application writen in C# .NET1.1
- But when i try to protect Application writen in C# .NET2.0i get this error
Strong name validation failed for assembly 'c:\lab\xshld875.tmp'. The file may have been tampered with or it was partially signed but not fully signed with the correct private key.
Any help on how to disable the Strong Name Validation ?
Kind Regards
 Lucian Bargaoanu wrote: |
| You can do this using sn.exe -Vr. But it would be better to check if that tool can work with the CLR 2.0. | Caution |
|---|
Use this option only during development. Adding an assembly to the skip verification list creates a security vulnerability. A malicious assembly could use the fully specified assembly name (assembly name, version, culture, and public key token) of the assembly added to the skip verification list to fake its identity. This would allow the malicious assembly to also skip verification. |
|
|
Finally some body replied to my post 
Thanks Lucian.
Would you please give me more explanation.
Shall i do it (sn.exe -Vr) after using the ExeShield or before i build my application.
Suppose this is my output MyApp.exe and i want to disable Strong name validation.
Thanks
| Lucian Bargaoanu wrote: |
| Sorry, but I don't know anything about ExeShield. Using sn you can tell the CLR (at runtime) not to verify the signature on your assembly. |
|
Ok Thanks again.
But how can i tell the CLR (at runtime) not to verify the signature? Is there any option to check on VS
BTY: i am using Visual Studio 2005 Team Edition for Software Developers
