.NET 部署到网络共享
我有一个 .NET 3.5 应用程序，希望将其安装在客户端服务器上，并让工作站直接从网络共享运行它。 我读过一些内容，似乎表明这并不像简单地将应用程序复制到网络共享那样简单，就像我对本机 exe 所做的那样。 不幸的是，似乎缺乏关于正确/最佳方法（通过 ClickOnce 或其他方式）的文档。
那么，我该如何进行这种类型的部署呢？ 我只复制程序集吗？ ClickOnce 有什么东西可以让我的生活更轻松并促进未来的更新吗？ （请记住，每个客户端在其本地服务器上都有不同的安装点。）
到目前为止我所知道的：
显然，.NET 框架必须安装在每个工作站上； 我认为通过组策略安装它是正确的方法。
我还读过一些关于从需要完全信任的网络共享运行的内容，但后来我读到这在 3.5 中可能不是问题。 有谁知道这里的最终答案吗？
I have a .NET 3.5 application that I wish to install on the client's server and have workstations run it directly from the network share. I've read a bit that seems to suggest this isn't as easy as simply copying the application to the network share like I would for a native exe. Unfortunately, there seems to be a lack of documentation on the correct/best way to do this (via ClickOnce or otherwise).
So, how would I go about this type of deployment? Do I just copy the assemblies? Is there something with ClickOnce that can make my life easier and facilitate future updates? (Bear in mind, each client will have a different install point on their local server.)
What I know so far:
Obviously, the .NET framework has to be installed on each workstation; I'm thinking that installing it via a Group Policy is the way to go here.
I've also read a bit about running from a network share requiring full trust, but then I read this may not be an issue in 3.5. Does anyone know the definitive answer here?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
从 3.5 SP1 开始，从网络共享运行应用程序不再是问题。 默认情况下，它们将以完全信任的方式运行。
万斯的帖子：http://blogs.msdn.com/vancem/archive/2008/08/13/net-framework-3-5-sp1-allows-management -code-to-be-launched-from-a-network-share.aspx
我相信实际的更改是在 CLR 2.0 SP2 中，您可以通过 3.5 SP1 获得该更改，但我还没有找到有关该主题的任何具体文档。
Starting with 3.5 SP1 it is no longer an issue to run applications from a network share. They will run with full trust by default.
Vance's Post: http://blogs.msdn.com/vancem/archive/2008/08/13/net-framework-3-5-sp1-allows-managed-code-to-be-launched-from-a-network-share.aspx
I believe the actual change is in CLR 2.0 SP2 which you get with 3.5 SP1 but I haven't found any concrete documentation on the subject.
您还可以使用 ClickOnce 部署来允许普通受限用户在本地安装应用程序。 此部署仍然允许您将更新发布到网络共享并让用户自动获取它们。 如果您坚持使用 3.5sp1 之前的 .Net 版本，它也可以工作。
它还回避了其他一些问题。 例如，如果您需要部署更新，并且用户当前在其本地计算机上运行该应用程序，则文件系统可能已锁定您需要更改的文件。 ClickOnce 会跳过该操作。
You can also use ClickOnce deployment to allow normal restricted users to install the app locally. This deployment still allows you to publish updates to your network share and have users automatically grab them. And it will work if you're stuck with a .Net version prior to 3.5sp1.
It also side steps some other issues. For example, if you need to deploy an update and a user currently has the app running on their local machine the file system may have locked a file you need to change. ClickOnce skips that.