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.
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
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:
So does that mean that one of the most common scenarios (Windows server + ISA Server) in companies doesnt work with ClickOnce??
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