ankitsrist Ответов: 2

Победить проблему с развертыванием форма: "проверки приложения не увенчались успехом можете продолжить"


Привет,
Я создал приложение windows, которое хочу развернуть. Я опубликовал его, но когда я нажимаю на файл. exe, он выдает ошибку "проверка приложения не удалась, невозможно продолжить".
при нажатии кнопки Подробнее я получил следующее окно ошибки

PLATFORM VERSION INFO
	Windows 			: 6.1.7601.65536 (Win32NT)
	Common Language Runtime 	: 4.0.30319.18444
	System.Deployment.dll 		: 4.0.30319.18408 built by: FX451RTMGREL
	clr.dll 			: 4.0.30319.18444 built by: FX451RTMGDR
	dfdll.dll 			: 4.0.30319.18408 built by: FX451RTMGREL
	dfshim.dll 			: 4.0.41209.0 (Main.041209-0000)

SOURCES
	Deployment url			: file:///D:/ankit%20mpscdrc%20dektop/MPSCDRC_DesktopAPP.application
	Application url			: file:///D:/ankit%20mpscdrc%20dektop/Application%20Files/MPSCDRC_DesktopAPP_1_0_0_5/MPSCDRC_DesktopAPP.exe.manifest

IDENTITIES
	Deployment Identity		: MPSCDRC_DesktopAPP.application, Version=1.0.0.5, Culture=neutral, PublicKeyToken=b291923a92b58760, processorArchitecture=x86
	Application Identity		: MPSCDRC_DesktopAPP.exe, Version=1.0.0.5, Culture=neutral, PublicKeyToken=b291923a92b58760, processorArchitecture=x86, 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 D:\ankit mpscdrc dektop\MPSCDRC_DesktopAPP.application resulted in exception. Following failure messages were detected:
		+ File, MPSCDRC_DesktopAPP.exe, has a different computed hash than specified in manifest.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
	No transaction error was detected.

WARNINGS
	There were no warnings during this operation.

OPERATION PROGRESS STATUS
	* [1/9/2014 3:35:19 PM] : Activation of D:\ankit mpscdrc dektop\MPSCDRC_DesktopAPP.application has started.
	* [1/9/2014 3:35:19 PM] : Processing of deployment manifest has successfully completed.
	* [1/9/2014 3:35:19 PM] : Installation of the application has started.
	* [1/9/2014 3:35:19 PM] : Processing of application manifest has successfully completed.
	* [1/9/2014 3:35:21 PM] : Found compatible runtime version 4.0.30319.
	* [1/9/2014 3:35:21 PM] : Detecting dependent assembly Microsoft.Synchronization.Data.Server, Version=2.0.0.0, Culture=neutral, PublicKeyToken=89845DCD8080CC91, processorArchitecture=msil using Microsoft.Synchronization.Data.Server, Version=2.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91, processorArchitecture=msil.
	* [1/9/2014 3:35:21 PM] : Detecting dependent assembly Microsoft.Synchronization, Version=1.0.0.0, Culture=neutral, PublicKeyToken=89845DCD8080CC91, processorArchitecture=msil using Microsoft.Synchronization, Version=1.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91, processorArchitecture=msil.
	* [1/9/2014 3:35:21 PM] : Detecting dependent assembly Microsoft.Synchronization.Data.SqlServerCe, Version=2.0.0.0, Culture=neutral, PublicKeyToken=89845DCD8080CC91, processorArchitecture=msil using Microsoft.Synchronization.Data.SqlServerCe, Version=2.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91, processorArchitecture=msil.
	* [1/9/2014 3:35:21 PM] : Detecting dependent assembly System.Data.SqlServerCe, Version=3.5.1.0, Culture=neutral, PublicKeyToken=89845DCD8080CC91, processorArchitecture=msil using System.Data.SqlServerCe, Version=3.5.1.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91, processorArchitecture=msil.
	* [1/9/2014 3:35:21 PM] : Detecting dependent assembly Microsoft.Synchronization.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=89845DCD8080CC91, processorArchitecture=msil using Microsoft.Synchronization.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91, processorArchitecture=msil.
	* [1/9/2014 3:35:21 PM] : Request of trust and detection of platform is complete.

ERROR DETAILS
	Following errors were detected during this operation.
	* [1/9/2014 3:35:21 PM] System.Deployment.Application.InvalidDeploymentException (HashValidation)
		- File, MPSCDRC_DesktopAPP.exe, has a different computed hash than specified in manifest.
		- Source: System.Deployment
		- Stack trace:
			at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, Hash hash)
			at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, HashCollection hashCollection)
			at System.Deployment.Application.ComponentVerifier.VerifyComponents()
			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, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
			at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

COMPONENT STORE TRANSACTION DETAILS
	No transaction information is available.

перепробовал много вещей, но ничего не получилось, пожалуйста, помогите..

Sergey Alexandrovich Kryukov

Недостаточно информации. Никаких примеров кода, никаких шагов для воспроизведения проблемы, ничего.
—СА

ankitsrist

Здравствуйте Сергей на самом деле проблема не в коде а в самом коде deployment...it выдает ошибку ""проверка приложения не удалась не удалось продолжить "" во время установки

Sergey Alexandrovich Kryukov

Вот как я понял это в первую очередь, но все же, как исправить то, на что я не могу смотреть?
—СА