部署解决方案更新文档级别VSTO插件（包括文档） [英] Solution for Deploying & Updating Document Level VSTO Addin Including the Document

问题描述

请您对部署Office VSTO加载项（尤其是Excel）的方法有何建议，以便于更新和部署文档以及加载项。

Do any of you have advice on methods for deploying an office VSTO addin, especially Excel, that makes it easy to update and deploy the document as well as the addin.

我有一个使用VSTO创建的Excel 2010文档级加载项。我目前使用单击一次部署它。但是，这有一些问题。第一个问题是我将其发布到ftp，然后用户从我的网站上安装了它。由于文档和加载项是从Internet下载的，因此我显然很难获得运行该加载项和受信任文档的适当权限。目前，在安装解决方案时，我只是让用户手动调整权限并授予访问权限。该部分可以正常工作，但是，如果您有任何关于如何使此过程自动化的建议，那将很棒。

I have a document level addin for Excel 2010 that I created using VSTO. I currently deploy it using click once. However, this has a few problems. The first problem is that I publish it to ftp then users install it from my website. Since the document and addin are downloaded from the internet, I obviously have trouble getting proper permission for the addin to run and the document to be trusted. Currently I just have users manually adjust permissions and grant access when the solution is installed. That part works and is fine, but if any of you have suggestions on how to automate this that would be great.

第二个问题是我希望在本文中获得帮助的主要问题是部署更新。我一般喜欢使用clickonce，因为它易于安装和具有自动更新功能。我开发的解决方案用于快速增长的快速变化的公司，这意味着我经常进行更新。单击一次即可轻松轻松地更新代码或插件本身。我只是让它在启动时自动检查更新，如果有更新，它将提示用户下载它们。但是文件呢？我的解决方案不仅包含代码。它还包括高度定制的Excel工作簿。

The second problem, the main one I am wanting help with in this post, is deploying updates. I generally like using clickonce because of its ease of installation and automatic update features. The solutions I develop are used in rapidly growing fast changing companies, which means I am often making updates. Click once makes it easy enough to update the "code" or addin itself. I just have it automatically check for updates when it is started, and if there are updates it will prompt the user to download them. But what about the document? My solution doesn't only include the code. It also includes the highly customized Excel workbook.

在最初安装解决方案时，该工作簿的副本刚刚下载到本地计算机上。但是，将其部署到数十台计算机之后呢？文档级别的更改（例如，添加一列）是否意味着要进入每台计算机并手动下载更新的工作簿？

When the solution is initially installed a copy of the workbook is just downloaded to the local computer. But what about after it is deployed to dozens of computers? Does a document level change (adding a column for example) mean going to each computer and downloading the updated workbook manually?

当然，有更好的方法可以自动部署工作簿的更新版本。有什么建议吗？

Surely there is a better way to automatically deploy updated versions of the workbook. Any suggestions?

以下是我想到的一些想法：

Here are a few ideas I thought of:

• 使用除clickonce以外的一些安装程序。有什么建议可以轻松自动更新吗？


• 以某种方式将工作簿打包为应用程序资源。实际上，在某些情况下我已经这样做了，但是在文档本身包含VSTO插件的情况下却没有这样做。


• 与先前的想法有关。制作一个包含工作簿&的包装器项目。 VSTO插件。然后，通过单击桌面上的常规图标来启动加载项，该图标将下载工作簿（如果需要更新），然后在Excel中打开它。我宁愿使用那种启动方法而不是简单地打开工作簿。

注意：当用户数据不需要保留在工作簿中时更新完成。旧版本可以简单地被新版本覆盖。该工作簿从SQL服务器获取所有数据。

Note: No user data needs to be preserved in the Workbook when an update is done. The old version could simply be overwritten by the new one. The workbook gets all its data from an SQL server.

推荐答案

您可以使用 Visual Studio安装项目，该项目利用了 Windows安装程序。 请参阅此部署演练指南有关使用VSTO 4.0的信息。

You could use a Visual Studio Setup Project which leverages Windows Installer. See this deployment walkthrough guide on using VSTO 4.0.

在Visual Studio 2012中，已弃用对安装项目的支持，而推荐使用 InstallShield LE ，这是另一种选择。

In Visual Studio 2012, support for Setup Projects is being deprecated in favor of InstallShield LE which is another alternative.

这篇关于部署解决方案更新文档级别VSTO插件（包括文档）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！