ClickOnce deployment gets messed up after going from 2.0 to 3.5   

Hi yall!

I got a locally published website and client (deployed by ClickOnce) that I 
install on several servers. I'm using mage.exe to update and re-sign the 
application and deployment manifests. Everything worked like a charm when 
using 2.0
Now we moved to 3.5 and I updated mage.exe and added the now necessary 
Microsoft.Build... assembly. The whole resigning process worked fine, but 
when I try to install the client on a fresh machine, I get the following 
following error:

Code:
ERROR DETAILS
   Following errors were detected during this operation.
   * [07.07.2008 13:52:14] 
System.Deployment.Application.InvalidDeploymentException 
(ManifestSemanticValidation)
      - Application contains an assembly with the same identity as the 
application or deployment: PcVclient.application, Version=1.2.99.0, 
Culture=neutral, PublicKeyToken=b2cb5e85fcd37978, processorArchitecture=msil.
      - 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)
         at 
System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

Any ideas, hints, tipps much appreciated. Thanks for reading tat far.

Cheers,
Nessi

date: Mon, 7 Jul 2008 05:33:04 -0700   author:   Nessi

Re: ClickOnce deployment gets messed up after going from 2.0 to 3.5   

Are you still looking for an answer to this?

RobinS.
GoldMail.com


"Nessi"  wrote in message 
news:7AB7C267-37E5-4B6D-8134-69E2AE5C63BB@microsoft.com...
> Hi yall!
>
> I got a locally published website and client (deployed by ClickOnce) that 
> I
> install on several servers. I'm using mage.exe to update and re-sign the
> application and deployment manifests. Everything worked like a charm when
> using 2.0
> Now we moved to 3.5 and I updated mage.exe and added the now necessary
> Microsoft.Build... assembly. The whole resigning process worked fine, but
> when I try to install the client on a fresh machine, I get the following
> following error:
>
> Code:
> ERROR DETAILS
>   Following errors were detected during this operation.
>   * [07.07.2008 13:52:14]
> System.Deployment.Application.InvalidDeploymentException
> (ManifestSemanticValidation)
>      - Application contains an assembly with the same identity as the
> application or deployment: PcVclient.application, Version=1.2.99.0,
> Culture=neutral, PublicKeyToken=b2cb5e85fcd37978, 
> processorArchitecture=msil.
>      - 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)
>         at
> System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object 
> state)
>
> Any ideas, hints, tipps much appreciated. Thanks for reading tat far.
>
> Cheers,
> Nessi

date: Tue, 26 Aug 2008 22:50:21 -0700   author:   RobinS

Re: ClickOnce deployment gets messed up after going from 2.0 to 3.5   

RobinS said:
> Are you still looking for an answer to this?

Yes.

Cheers,
Udo

date: Wed, 27 Aug 2008 08:27:31 +0200   author:   Udo Nesshoever