凭借 ClickOnce 的所有优点，我们希望使用它作为我们应用程序的部署机制。
但是我在 Microsoft Connect 中发现了此消息，其中显示 ClickOnce 因代理身份验证失败。
https://connect.microsoft.com/ VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=115468&wa=wsignin1.0
那么这是否意味着公司中最常见的场景之一（Windows 服务器 + ISA 服务器）无法使用 ClickOnce？
“解决方案”是修改每个客户端的 machine.config！。 这对我们来说绝对是不可接受的（此外，ClickOnce 的目的是什么？？）
我们的应用程序使用 3.5，我想知道这个问题是否仍然存在。 或者如果有人成功地完成了这项工作。
（我知道有 v2 的补丁，但是 v3> 呢？）
谢谢
With all the advantages of ClickOnce, we would like to use it as the deployment mechanism for our App.
However i have found this message in Microsoft Connect where it says that ClickOnce fails with proxy authentication.
https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=115468&wa=wsignin1.0
So does that mean that one of the most common scenarios (Windows server + ISA Server) in companies doesnt work with ClickOnce??
The "solution" is to modify machine.config for every client!. That is absolutely unnaceptable for us (Besides, what would be the purpose of ClickOnce??)
Our application uses 3.5 and i would like to know if that problems still exists. Or if someone has managed to make this work.
(I know that there is a patch for v2 but what about v3> ?)
Thanks
发布评论
评论（3）
没有回答您关于该问题是否在 3.5 中仍然存在的确切问题，因为我仍在 2.0 代码库上。 不过，我希望以下内容对您有用，具体取决于部署环境中的可用选项：
UNC 部署是我在部署 ClickOnce（2.0 中）应用程序时遇到此代理身份验证问题时多次使用的解决方法。 在企业环境中，共享上的 NTFS 权限可以提供所需的安全级别
Doesn't answer your exact question regarding if the issue is still existant in 3.5, as I'm still on a 2.0 codebase. However I hope the following is of use to you, depending on what available options in the deployment environment is:
UNC deployment is the workaround that I have used several times when encountering this proxy authentication issue when deploying a ClickOnce (in 2.0) app. In a corporate environment, the NTFS permissions on the share can provide the required level of security
我的回答可能有点题外话，但我认为你不应该担心这一点：
个人用户和小公司没有带身份验证的代理
大公司确实有专门的 IT 人员来解决此类问题。 他们要么找到一种方法让 ClickOnce 工作（包括在每个客户端上部署本地 machine.conf），要么关闭整个应用程序，因为使用 ClickOnce 违反了他们的政策（IT 安全部门不喜欢拥有可执行文件的想法）代码通过互联网自动更新到他们的安全网络中，我知道这一点）
My answer may be a bit off-topic, but I think you shouldn't concern about this :
Individual users and small corporations don't have proxy with authentication
Big corporations do have dedicated IT people to solve this kind of things. They will either find a way to get ClickOnce to work (including deploying a local machine.conf on every client), or turn your whole application down because using ClickOnce is against their policy (IT security departments don't like the idea of having executable code automatically updated over the internet into their safe network, I know that first hand)
对于使用 .NET Framework 2.0 的客户，Microsoft 针对此问题提供了一个修补程序，可以在 此处。
请注意，此问题受到客户运行的 .NET 版本（而不是您运行的版本）的影响。 如果您的客户需要 .NET 3.5 来安装/运行您的 ClickOnce 应用程序，则该版本已修复此问题。
For customers with the .NET framework 2.0, Microsoft has a hot-fix for this issue which can be found here.
Note that this issue is affected by the version of .NET that your customers are running (not the version that you're running). If your clients need to have .NET 3.5 to install/run your ClickOnce app, that version has already fixed this issue.