D
Dean Slindee
I am using ClickOnce to deploy a solution written in VB using Visual Studio
2008, .NetFramework 3.5SP1:
Problem: VS2008/ClickOnce fails to deploy a solution with references to
..exe's referenced from other solution(s).
Here is the cause of the problem:
"a new feature of Visual Studio 2008 was causing problems. Basically, VS
2008 can embed a manifest inside of an assembly. Mage was somehow using
this manifest in it's manifest generation, resulting in a duplicate manifest
being created. As soon as we changed the build to no longer embed the
manifest, it worked fine!" This quote is from the link below:
For C# developers, here is the solution:
http://geekswithblogs.net/rakker/archive/2007/12/06/117449.aspx
OK, so what is the fix in VB?
For a further description of the problem, read on:
My solution has References to 5 (other VB solutions) .exe's also compiled in
VS2008 .NetFramework 3.5SP1. ClickOnce succeeds with the publishing step,
but does not launch an application installation window. When I manually
double-click the ClickOnce produced "setup.exe" file, this error message
appears in the "details": "Reference in the manifest does not match the
identity of the downloaded assembly" and names one of those 5 .exe's as the
problem.
To debug, I have gone to this solution's Properties, and on the Publish tab,
"Application Files." button, displayed the solution's .exe files, and
removed them one at a time. For each .exe that I remove, the problem just
moves on to the next external solution .exe, so it's not a problem with the
first external .exe specifically. If I remove all of the .exe's then
ClickOnce completes, installs this solution, but displays a
"FileNotFoundException" messagebox complaining that one of the 5 removed
..exe's (file or assembly) is not present.
I have been reading other posts with the same error message, and it is not
clear whether ClickOnce deployment of a VS2008(VB) solution actually
supports deploying a solution where .exe's are referenced from other
solutions.
Turning off ClickOnce security does not help. None my code is obfuscated.
Does anyone know for sure, or found a remedy to this problem in a
VisualBasic ClickOnce deployment?
I did not have this problem in VB with VS2005, .NetFramework 2.0.
Error Message from ClickOnce setup.exe follows:
PLATFORM VERSION INFO
Windows : 6.0.6001.65536
(Win32NT)
Common Language Runtime : 2.0.50727.3053
System.Deployment.dll : 2.0.50727.3053
(netfxsp.050727-3000)
mscorwks.dll : 2.0.50727.3053
(netfxsp.050727-3000)
dfdll.dll : 2.0.50727.3053
(netfxsp.050727-3000)
dfshim.dll : 2.0.50727.3053
(netfxsp.050727-3000)
SOURCES
Deployment url :
file://laxstage/Inetpub/wwwroot/ClickOnce/Provider/Provider.application
Application url :
file://laxstage/Inetpub/wwwroot/ClickOnce/Provider/Application%20Files/Provider_1_2008_11_22/Provider.exe.manifest
IDENTITIES
Deployment Identity : Provider.application,
Version=1.2008.11.22, Culture=neutral, PublicKeyToken=ca89459ce5aec206,
processorArchitecture=msil
Application Identity : Provider.exe,
Version=1.2008.11.22, Culture=neutral, PublicKeyToken=ca89459ce5aec206,
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
\\laxstage\Inetpub\wwwroot\ClickOnce\Provider\Provider.application resulted
in exception. Following failure messages were detected:
+ Reference in the manifest does not match the
identity of the downloaded assembly ClientScan.exe.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [11/26/2008 1:22:55 PM] : Activation of
\\laxstage\Inetpub\wwwroot\ClickOnce\Provider\Provider.application has
started.
* [11/26/2008 1:22:56 PM] : Processing of deployment manifest
has successfully completed.
* [11/26/2008 1:22:56 PM] : Installation of the application has
started.
* [11/26/2008 1:22:56 PM] : Processing of application manifest
has successfully completed.
* [11/26/2008 1:23:00 PM] : Request of trust and detection of
platform is complete.
ERROR DETAILS
Following errors were detected during this operation.
* [11/26/2008 1:23:00 PM]
System.Deployment.Application.InvalidDeploymentException (RefDefValidation)
- Reference in the manifest does not match the
identity of the downloaded assembly ClientScan.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, 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.
Thanks in advance,
Dean Slindee
2008, .NetFramework 3.5SP1:
Problem: VS2008/ClickOnce fails to deploy a solution with references to
..exe's referenced from other solution(s).
Here is the cause of the problem:
"a new feature of Visual Studio 2008 was causing problems. Basically, VS
2008 can embed a manifest inside of an assembly. Mage was somehow using
this manifest in it's manifest generation, resulting in a duplicate manifest
being created. As soon as we changed the build to no longer embed the
manifest, it worked fine!" This quote is from the link below:
For C# developers, here is the solution:
http://geekswithblogs.net/rakker/archive/2007/12/06/117449.aspx
OK, so what is the fix in VB?
For a further description of the problem, read on:
My solution has References to 5 (other VB solutions) .exe's also compiled in
VS2008 .NetFramework 3.5SP1. ClickOnce succeeds with the publishing step,
but does not launch an application installation window. When I manually
double-click the ClickOnce produced "setup.exe" file, this error message
appears in the "details": "Reference in the manifest does not match the
identity of the downloaded assembly" and names one of those 5 .exe's as the
problem.
To debug, I have gone to this solution's Properties, and on the Publish tab,
"Application Files." button, displayed the solution's .exe files, and
removed them one at a time. For each .exe that I remove, the problem just
moves on to the next external solution .exe, so it's not a problem with the
first external .exe specifically. If I remove all of the .exe's then
ClickOnce completes, installs this solution, but displays a
"FileNotFoundException" messagebox complaining that one of the 5 removed
..exe's (file or assembly) is not present.
I have been reading other posts with the same error message, and it is not
clear whether ClickOnce deployment of a VS2008(VB) solution actually
supports deploying a solution where .exe's are referenced from other
solutions.
Turning off ClickOnce security does not help. None my code is obfuscated.
Does anyone know for sure, or found a remedy to this problem in a
VisualBasic ClickOnce deployment?
I did not have this problem in VB with VS2005, .NetFramework 2.0.
Error Message from ClickOnce setup.exe follows:
PLATFORM VERSION INFO
Windows : 6.0.6001.65536
(Win32NT)
Common Language Runtime : 2.0.50727.3053
System.Deployment.dll : 2.0.50727.3053
(netfxsp.050727-3000)
mscorwks.dll : 2.0.50727.3053
(netfxsp.050727-3000)
dfdll.dll : 2.0.50727.3053
(netfxsp.050727-3000)
dfshim.dll : 2.0.50727.3053
(netfxsp.050727-3000)
SOURCES
Deployment url :
file://laxstage/Inetpub/wwwroot/ClickOnce/Provider/Provider.application
Application url :
file://laxstage/Inetpub/wwwroot/ClickOnce/Provider/Application%20Files/Provider_1_2008_11_22/Provider.exe.manifest
IDENTITIES
Deployment Identity : Provider.application,
Version=1.2008.11.22, Culture=neutral, PublicKeyToken=ca89459ce5aec206,
processorArchitecture=msil
Application Identity : Provider.exe,
Version=1.2008.11.22, Culture=neutral, PublicKeyToken=ca89459ce5aec206,
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
\\laxstage\Inetpub\wwwroot\ClickOnce\Provider\Provider.application resulted
in exception. Following failure messages were detected:
+ Reference in the manifest does not match the
identity of the downloaded assembly ClientScan.exe.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [11/26/2008 1:22:55 PM] : Activation of
\\laxstage\Inetpub\wwwroot\ClickOnce\Provider\Provider.application has
started.
* [11/26/2008 1:22:56 PM] : Processing of deployment manifest
has successfully completed.
* [11/26/2008 1:22:56 PM] : Installation of the application has
started.
* [11/26/2008 1:22:56 PM] : Processing of application manifest
has successfully completed.
* [11/26/2008 1:23:00 PM] : Request of trust and detection of
platform is complete.
ERROR DETAILS
Following errors were detected during this operation.
* [11/26/2008 1:23:00 PM]
System.Deployment.Application.InvalidDeploymentException (RefDefValidation)
- Reference in the manifest does not match the
identity of the downloaded assembly ClientScan.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, 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.
Thanks in advance,
Dean Slindee