POSSIBLE CAUSE
When the 3.5SP1 structure is installed and the ClickOnce storage is used for the first cdf ms files maybe deleted time. This can be caused by deleting the HKEY_CURRENT_USER \ Software \ Classes \ Software \ Microsoft \ Windows \ CurrentVersion \ Deployment \ ClickOnce35SP1Update registry key. Missing files from the ms cdf will cause the ClickOnce to erroneously share strong named assembly with the same version but the different file hash.
SOLUTION
To avoid the problem before it happens Make sure that all the shared assemblies that you are using in your updated ClickOnce application have a new version of the assembly.
If the problem has already occurred, you must clear the online cache by running "mage.exe - cc", uninstall all versions of installed applications that may have a strong named set of the same version, and then reinstall the application .
Mage.exe is available in several places, including the following:
• The .NET Framework 2.0 SDK. The .NET Framework 2.0 SDK is available as a component of Visual Studio 2005 Setup or can be downloaded from the Microsoft Download Center.
· The Windows SDK for Windows Vista. The Windows SDK for Windows Vista can be downloaded from the Microsoft Download Center.
Visual Studio 2008. More recent versions of Mage.exe and MageUI.exe are included as a component of the Visual Studio 2008 installation.
TO KNOW MORE: link