的ClickOnce /智能客户端部署在.NET中的缺陷/陷阱 [英] Pitfalls/gotchas of ClickOnce/smart-client deployment in .NET
问题描述
我有几个.NET 我是preparing转换成Windows窗体应用程序成的ClickOnce /智能客户端部署方案。我读过的isn't，这个伟大的教程，但是否有缺陷或陷阱，我应该知道？
I have several .NET Windows Forms applications that I'm preparing to convert into a ClickOnce/smart-client deployment scenario. I've read the isn't-this-great tutorials, but are there pitfalls or "gotchas" that I should be aware of?
有使用和关闭一些小的应用程序，但主要应用在C＃中，运行24/7，是相当大的，但只有改变每隔几个星期。它也写入locallly日志文件和会谈本地硬件设备。
There are several minor applications used off and on, but the main application is in C#, runs 24/7, is quite large, but only changes every few weeks. It also writes to a log file locallly and talks to local hardware devices.
推荐答案
下面是一些我所知道的。
Here are a few that I am aware of.
-
<打击>不能把桌面上的图标。您现在可以。
我无法安装为所有用户。
I can't install for all users.
我需要通过箍跳转到部署移动到另一台服务器。这不是一个问题，如果你在内部开发，并且用户可以看到您发布或如果要部署到公共的Web服务器，但它也不是很大，如果你需要独立推出多个客户站点。
I need to jump through hoops to move the deployment to a different server. It is not a problem if you are developing internally, and the users can see the server that you are publishing to or if you are deploying to the public web, but it is not great if you need to roll out to multiple customer sites independently.
由于 .NET 3.5 SP1您不必签署部署清单再这使得它更容易移动部署到新的服务器。
Since .NET 3.5 SP1 you do not need to sign the deployment manifest anymore which makes it much easier to move deployments to new servers.
我无法安装在 GAC 组件。您可以通过创建常规安装包为pre必备ClickOnce应用程序的解决这个问题。
I can't install assemblies in the GAC. You can get around this by creating regular install packages that are pre-requisites of the ClickOnce application.
这篇关于的ClickOnce /智能客户端部署在.NET中的缺陷/陷阱的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
