uma

uma

  • NA
  • 42.5k
  • 0

Deployment of VSTO 2005 excel application

Jan 17 2007 12:16 AM

Hi
Im using VSTO 2005 excel application(using C#).When i deploy the application using publish wizard.
It publishes successfully.

But when i click on .APPLICATION file,it says Cannot continue.The application is improperly formatted.Contact the application vendor for assitance.

-and the details of the error message is as follows:

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:///D:/xlsws/cuma/ExcelCommandBars.application

ERROR SUMMARY
 Below is a summary of the errors, details of these errors are listed later in the log.
 * Activation of D:\xlsws\cuma\ExcelCommandBars.application resulted in exception. Following failure messages were detected:
  + Exception reading manifest from file:///D:/xlsws/cuma/ExcelCommandBars.application: the manifest may not be valid or the file could not be opened.
  + Deployment manifest is not semantically valid.
  + Application reference identity must be strongly named.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
 No transaction error was detected.

WARNINGS
 There were no warnings during this operation.

OPERATION PROGRESS STATUS
 * [1/17/2007 10:48:18 AM] : Activation of D:\xlsws\cuma\ExcelCommandBars.application has started.

ERROR DETAILS
 Following errors were detected during this operation.
 * [1/17/2007 10:48:18 AM] System.Deployment.Application.InvalidDeploymentException (ManifestParse)
  - Exception reading manifest from file:///D:/xlsws/cuma/ExcelCommandBars.application: 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.DownloadDeploymentManifestDirectBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
   at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)
   at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)
   at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
  --- Inner Exception ---
  System.Deployment.Application.InvalidDeploymentException (ManifestSemanticValidation)
  - Deployment manifest is not semantically valid.
  - Source: System.Deployment
  - Stack trace:
   at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSemanticsForDeploymentRole()
   at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSemantics(ManifestType manifestType)
   at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
  --- Inner Exception ---
  System.Deployment.Application.InvalidDeploymentException (ManifestComponentSemanticValidation)
  - Application reference identity must be strongly named.
  - Source: System.Deployment
  - Stack trace:
   at System.Deployment.Application.Manifest.AssemblyManifest.ValidateApplicationDependency(DependentAssembly da)
   at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSemanticsForDeploymentRole()

COMPONENT STORE TRANSACTION DETAILS
 No transaction information is available.

Regards
uma