All geek questions in one place

Clickonce (in .NETv3.5) - does it support work through a proxy server with a username and password?

Does ClickOnce (in VS2008, .NETv3.5) support work through a proxy server with a username and password?

thanks

PS. Just tried it and it seems like not? I got the following errors:

(a) Under firefox:

URLDownloadToCacheFile failed with HRESULT '-2147024891'

(b) with IE

System.Deployment.Application.DeploymentDownloadException (Unknown subtype)

  --- Inner Exception --- System.Net.WebException - The remote server returned an error: (407) Proxy Authentication Required. - Source: System - Stack trace: at System.Net.HttpWebRequest.GetResponse() at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)

PS. Information in the link does not support the proposal completely and reliably - link text

+4
source share
2 answers

The longer answer is no, but there is a workaround for it. It was authorized by C / O PM at MSFT.

http://social.msdn.microsoft.com/Forums/en/winformssetup/thread/3e9cebad-9630-4bbc-a0ca-0d2f20335454

+1
source

The short answer is no, it is not. This was a problem for me back in October (I even left a comment on the Microsoft Connect page that you linked to above).

My problem is that my company has an application that is used both within our intranet and externally for users outside our office. Since there are users outside our office, I had to publish the application on the Internet (i.e., on non-intranet).

When the corporation changed several parameters of the proxy server, the application violated the ability of our internal users to install and update the application, because their proxy server credentials are invalid every 5 minutes. They can download the application as long as the first open IE and cannot load any external web page - something that would seem to automatically re-verify their credentials.

The best solution I could find was to publish the application twice - first on an external site. Secondly, to a friendly place on the intranet that has not been verified through a proxy.

This solution, of course, is not elegant, but it worked for us.

0
source

Source: https://habr.com/ru/post/1302952/

More articles:


All Articles