RE: ClickOnce error
- From: v-garych@xxxxxxxxxxxxxxxxxxxx ("Gary Chang[MSFT]")
- Date: Fri, 17 Mar 2006 03:10:32 GMT
Hi Bruce,
The only other variable I can think of is we have a proxy server,
but the error message does not indicate that this is the problem.
In this regard, this problem may be caused by a known issue of Whidbey. It
is because that .Net deployment APIs do not use the default proxy and
credentials to access the remote ClickOnce files.
I suggest you set useDefaultCredentials to true as the followings in the
machine.config to workaround this issue:
<defaultProxy enabled="true" useDefaultCredentials="true">
This could get net classes to apply default domain credentials on the proxy
automatically.
Please refer to our corresponding MSDN bug link is for the detailed
information:
"Bug Details: click once fails with proxy authentication"
http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=0
a5f94d6-592e-4a3b-9c35-879a1ecdba57
Thanks!
Best regards,
Gary Chang
Microsoft Community Support
======================================================
PLEASE NOTE the newsgroup SECURE CODE and PASSWORD will be updated at 9:00
AM PST, February 14, 2006. Please complete a re-registration process by
entering the secure code mmpng06 when prompted. Once you have entered the
secure code mmpng06, you will be able to update your profile and access the
partner newsgroups.
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================
.
- References:
- ClickOnce error
- From: Bruce Parker
- ClickOnce error
- Prev by Date: Re: Using Reflection with nested DLLs
- Next by Date: Re: VB.net Purchase??
- Previous by thread: ClickOnce error
- Next by thread: RE: ClickOnce error
- Index(es):
Relevant Pages
|