Forum Discussion
Kevin_Davies_40
Aug 11, 2010Nacreous
In regards to the first issue this appears to be a dotNET 2.0 issue with ClickOnce as described below.
For this issue, it has been confirmed as a known issue of Whidbey. The root
cause is that .Net deployment API did not use the default proxy and
credentials to access the remote clickonce files.
To workaround this issue, we can set useDefaultCredentials to true in
machine.config, like this:
http://www.devnewsgroups.net/group/microsoft.public.dotnet.framework.windowsforms/topic31131.aspx
Regards
Jarvil