http://blogs.msdn.com/goto100/archive/2009/06/12/introducing-code-obfuscation.aspxIf you recall from an earlier post, I said that the main reason for signing an assembly and giving it a strong name was to prevent it being tampered with. For example, many of the assemblies that make up the .NET framework itself are strong-named assembliesen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/goto100/archive/2009/06/12/introducing-code-obfuscation.aspx#9735473Fri, 12 Jun 2009 18:39:33 GMT91d46819-8472-40ad-a661-2c78acb4018c:9735473jerryford2009<P>This raises the issues of intellectual copyright and opens the potential for security breaches as unscrupulous developers can easily look for weaknesses in your application.</P>