Originally I had written an application in Visual Studio 2005 Standard and deployed it with ClickOnce.  Both my partner and I were using Visual Studio 2005 Standard and he too could deploy my application since he had the key.

I upgraded my Visual Studio 2005 to Professional and now I any application I deploy generates a manifest error.  Here is an excerpt from the error details...

IDENTITIES
 Deployment Identity  : Transcript Generator.application, Version=1.0.0.4, Culture=neutral, PublicKeyToken=13d2dc8f2c66aa4f,

processorArchitecture=msil

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 http://10.16.56.9/qaweb/transcript/Transcript%20Generator.application resulted in exception. Following failure messages were

detected:
  + Exception reading manifest from http://10.16.56.9/qaweb/transcript/Transcript%20Generator_1_0_0_4/Transcript%20Generator.exe.manifest:

the manifest may not be valid or the file could not be opened.
  + Manifest XML signature is not valid.
  + No signature was present in the subject.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
 No transaction error was detected.

WARNINGS
 There were no warnings during this operation.

OPERATION PROGRESS STATUS
 * [1/24/2007 9:38:18 AM] : Activation of http://10.16.56.9/qaweb/transcript/Transcript%20Generator.application has started.
 * [1/24/2007 9:38:19 AM] : Processing of deployment manifest has successfully completed.
 * [1/24/2007 9:38:19 AM] : Installation of the application has started.

ERROR DETAILS
 Following errors were detected during this operation.
 * [1/24/2007 9:38:19 AM] System.Deployment.Application.InvalidDeploymentException (ManifestParse)
  - Exception reading manifest from http://10.16.56.9/qaweb/transcript/Transcript%20Generator_1_0_0_4/Transcript%20Generator.exe.manifest:

the manifest may not be valid or the file could not be opened.
  - Source: System.Deployment
  - Stack trace:
   at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
   at System.Deployment.Application.DownloadManager.DownloadApplicationManifest(AssemblyManifest deploymentManifest, String targetDir,

Uri deploymentUri, IDownloadNotification notification, DownloadOptions options, Uri& appSourceUri, String& appManifestPath)
   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)
  --- Inner Exception ---
  System.Deployment.Application.InvalidDeploymentException (SignatureValidation)
  - Manifest XML signature is not valid.
  - Source: System.Deployment
  - Stack trace:
   at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)
   at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
  --- Inner Exception ---
  System.Security.Cryptography.CryptographicException
  - No signature was present in the subject.

  - Source: System.Deployment
  - Stack trace:
   at System.Deployment.Internal.CodeSigning.SignedCmiManifest.Verify(CmiManifestVerifyFlags verifyFlags)
   at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)

This happens regardless if it was an exisiting application or a newly created application.

I know the manifest error is on my machince because my partner can take my flashdrive and publish all my applications without difficulty.

So my quesiton is WHAT did I do wrong?  If I uninstall Visual Studio 2005 Pro...and reinstall it...will that correct this manifest issue?

Ken