Installation Error: Application validation did not succeed. Unable to continue

[Josef Brunner]

Hi,

I published my application (VS 2005) and am now trying to install it when I
get this error message. It worked before...even on a different machine.
Here is the detailed description:


PLATFORM VERSION INFO
Windows : 5.1.2600.131072 (Win32NT)
Common Language Runtime : 2.0.50727.42
System.Deployment.dll : 2.0.50727.42 (RTM.050727-4200)
mscorwks.dll : 2.0.50727.42 (RTM.050727-4200)
dfdll.dll : 2.0.50727.42 (RTM.050727-4200)
dfshim.dll : 2.0.50727.42 (RTM.050727-4200)

SOURCES
Deployment url :
file:///C:/Dokumente%20und%20Einstellungen/Josef/Eigene%20Dateien/ApplicationName/Publish/ApplicationName.application
Application url :
file:///C:/Dokumente%20und%20Einstellungen/Josef/Eigene%20Dateien/ApplicationName/Publish/ApplicationName_1_0_0_31/ApplicationName.exe.manifest

IDENTITIES
Deployment Identity : ApplicationName.application, Version=1.0.0.31,
Culture=neutral, PublicKeyToken=a96ee49b104cf321, processorArchitecture=msil
Application Identity : ApplicationName.exe, Version=1.0.0.31,
Culture=neutral, PublicKeyToken=a96ee49b104cf321,
processorArchitecture=msil, type=win32

APPLICATION SUMMARY
* Installable application.

ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later
in the log.
* Activation of C:\Dokumente und Einstellungen\Josef\Eigene
Dateien\ApplicationName\Publish\ApplicationName.application resulted in
exception. Following failure messages were detected:
+ Reference in the manifest does not match the identity of the downloaded
assembly ApplicationName.exe.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [23.03.2006 17:08:17] : Activation of C:\Dokumente und
Einstellungen\Josef\Eigene
Dateien\ApplicationName\Publish\ApplicationName.application has started.
* [23.03.2006 17:08:17] : Processing of deployment manifest has
successfully completed.
* [23.03.2006 17:08:17] : Installation of the application has started.
* [23.03.2006 17:08:18] : Processing of application manifest has
successfully completed.
* [23.03.2006 17:08:20] : Request of trust and detection of platform is
complete.

ERROR DETAILS
Following errors were detected during this operation.
* [23.03.2006 17:08:20]
System.Deployment.Application.InvalidDeploymentException (RefDefValidation)
- Reference in the manifest does not match the identity of the downloaded
assembly ApplicationName.exe.
- Source: System.Deployment
- Stack trace:
at
System.Deployment.Application.DownloadManager.ProcessDownloadedFile(Object
sender, DownloadEventArgs e)
at
System.Deployment.Application.FileDownloader.DownloadModifiedEventHandler.Invoke(Object
sender, DownloadEventArgs e)
at System.Deployment.Application.FileDownloader.OnModified()
at
System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem
next)
at System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()
at
System.Deployment.Application.FileDownloader.Download(SubscriptionState
subState)
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)
at
System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object
state)

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.



Thanks for any advice,
Josef

 

[Gary Chang[MSFT]]

Hi Josef,

I published my application (VS 2005) and am now trying
to install it when I get this error message
...

Have you obfuscated the assembly which you want to install with the
ClickOnce deployment?

The ClickOnce in Visual Studio 2005 is unable to work with obfuscated
assemblies. If you have obfuscated assemblies in your ClickOnce deployment
package, then they will be the problem.

In such a scenario, I suggest you try the following use post-build steps to
workaround the problem:

1. Build your project.
2. Do the obfuscation.
3. Use Mage.exe or MageUI.exe in the .NET Frameworks SDK to generate the
ClickOnce manifests and sign them.
4. Manually publish the files to your deployment source (web server, unc
share, CD, etc...)


Thanks!

Best regards,

Gary Chang
Microsoft Community Support
======================================================
PLEASE NOTE the newsgroup SECURE CODE and PASSWORD will be updated at 9:00
AM PST, February 14, 2006. Please complete a re-registration process by
entering the secure code mmpng06 when prompted. Once you have entered the
secure code mmpng06, you will be able to update your profile and access the
partner newsgroups.
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Josef Brunner]

Hi Gary,

thanks for your fast reply!

AFAIK, I don't use an obfuscator. Is there an option on the project page
that enable/disables this? How can I find out if I use an obfuscator without
knowing?

Like I sayed, publishing earlyer versions worked fine...

Any other ideas?

Regards,
Josef

Hi Josef,

I published my application (VS 2005) and am now trying
to install it when I get this error message
...

Have you obfuscated the assembly which you want to install with the
ClickOnce deployment?

The ClickOnce in Visual Studio 2005 is unable to work with obfuscated
assemblies. If you have obfuscated assemblies in your ClickOnce deployment
package, then they will be the problem.

In such a scenario, I suggest you try the following use post-build steps
to
workaround the problem:

1. Build your project.
2. Do the obfuscation.
3. Use Mage.exe or MageUI.exe in the .NET Frameworks SDK to generate the
ClickOnce manifests and sign them.
4. Manually publish the files to your deployment source (web server, unc
share, CD, etc...)


Thanks!

Best regards,

Gary Chang
Microsoft Community Support
======================================================
PLEASE NOTE the newsgroup SECURE CODE and PASSWORD will be updated at 9:00
AM PST, February 14, 2006. Please complete a re-registration process by
entering the secure code mmpng06 when prompted. Once you have entered the
secure code mmpng06, you will be able to update your profile and access
the
partner newsgroups.
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.

 

[Gary Chang[MSFT]]

Hi Josef,

AFAIK, I don't use an obfuscator. Is there an option on the
project page that enable/disables this? How can I find out
if I use an obfuscator without knowing?

There is no such an option in the Deployment property page about the
obfuscator.

Have you used any third-party assemblies in your project?

I suggest you can use the .NET Reflector to check whether an assembly has
been obfuscated, its reflected code would be unreadable if it is obfuscated.


Thanks!

Best regards,

Gary Chang
Microsoft Community Support
======================================================
PLEASE NOTE the newsgroup SECURE CODE and PASSWORD will be updated at 9:00
AM PST, February 14, 2006. Please complete a re-registration process by
entering the secure code mmpng06 when prompted. Once you have entered the
secure code mmpng06, you will be able to update your profile and access the
partner newsgroups.
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Josef Brunner]

Hi Gary,

Have you used any third-party assemblies in your project?

I suggest you can use the .NET Reflector to check whether an assembly has
been obfuscated, its reflected code would be unreadable if it is
obfuscated.

Yes, I use two third-library dll's called PieChart3D.dll and
BetterCheckedListBox.dll (this dll has a reference to Visual Basic 7). I
downloaded the .net reflector and could open my compiled .exe. there I could
find all references to my dll's and also could browse those dll's
successfully.

Maybe I'm doing something wrong while publishing the application. All I do
is to click the Publich button (ClickOnce) and publsh it to my local
harddrive. Then I run the setup.exe and it gives me the described error.
Wenn I zip all files and send it to my collegue he gets the same error.
Strange, since it worked before and I have no new dll references since
then...

I'm really stuck here...no clue what to check or do...

Thank you very much again,
Josef

 

[Josef Brunner]

Hi everybody,

I found a posting by someone who had the same problem and could publish his
ClickOnce application by publishing it twice after a code change. I tried it
and it magically works...why? Who knows

Greets,
Kurt

 

[Gary Chang[MSFT]]

Hi Kurt,

I found a posting by someone who had the same problem
and could publish his ClickOnce application by publishing
it twice after a code change. I tried it and it magically
works...why? Who knows

I am delighted to know you have already found a workaround to this issue.
For the issue about why publishing twice makes the difference, my idea is
the publish version's revision number will be incremented automatically(if
the corresponding option has been checked by default) while you publish the
application each time.

If you uncheck that option, does that workaround still work?


Thanks!

Best regards,

Gary Chang
Microsoft Community Support
======================================================
PLEASE NOTE the newsgroup SECURE CODE and PASSWORD will be updated at 9:00
AM PST, February 14, 2006. Please complete a re-registration process by
entering the secure code mmpng06 when prompted. Once you have entered the
secure code mmpng06, you will be able to update your profile and access the
partner newsgroups.
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.