Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / VS Tools for Office / March 2007

Tip: Looking for answers? Try searching our database.

VSTO 2005 Excel Application & ClickOnce

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Michael Kalika - 26 Mar 2007 08:25 GMT
Hi,

We have developed a VSTO 2005 Excel application and we would like to
leverage ClickOnce deployment mechanism for distribution of this
application.
How can we do that? I was digging in MSDN for VSTO & ClickOnce documentation
and did not find anything. I've noticed that there is an option to
publish the project, but when I do that and then run the application from
Web it throws us security errors like:

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   : http://localhost/miniexcel/MiniExcel.application

ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later
in the log.
* Activation of http://localhost/miniexcel/MiniExcel.application resulted
in exception. Following failure messages were detected:
 + Exception reading manifest from
http://localhost/miniexcel/MiniExcel.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
* [25/02/2007 12:46:13] : Activation of
http://localhost/miniexcel/MiniExcel.application has started.

ERROR DETAILS
Following errors were detected during this operation.
* [25/02/2007 12:46:13]
System.Deployment.Application.InvalidDeploymentException (ManifestParse)
 - Exception reading manifest from
http://localhost/miniexcel/MiniExcel.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.

Is there another method we can use for automatic distribution of our
application if ClickOnes doesn't support VSTO?

Thank you very much for your help and support,

Best Regards,

Michael
XL-Dennis - 28 Mar 2007 02:45 GMT
Michael,

It's my understanding that VSTO does not work properly with ClickOnce.

---------------
With kind regards,
Dennis
Weekly Blog .NET & Excel: http://xldennis.wordpress.com/
My English site: http://www.excelkb.com/default.aspx
My Swedish site: http://www.xldennis.com/

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.