WebProxy.GetDefaultProxy

[Phil]

According to the help this method is obsolete, but there is no hint as to
what to use now instead.
It does seem to work for me, although I get a warning error from the
compiler.
The warning message contains a link to the microsoft website, but this link
just takes you to the .Net framework home page:
http://go.microsoft.com/fwlink/?linkid=14202
Can anyone provide the correct link and/or please explain what should now be
used instead of GetDefaultProxy .

TIA
Phil.

[Steven Cheng [MSFT]]

RE: WebProxy.GetDef aultProxy

Hi Phil,

As for the proxy setting support in .net framework 2.0, it's greatly
enhanced. The following article is a very good one which almost convers all
the proxy related features in .net framework:

#Proxy Detection Take the Burden Off Users with Automatic Configuration in
..NET
http://msdn.microsoft.com/en-us/magazine/cc300743.aspx

for the default proxy, in .net framework 2.0, it expose this via the
"WebRequest.Def aultWebProxy" property:

#WebRequest..:: .DefaultWebProx y Property
http://msdn.microsoft.com/en-us/libr...defaultwebprox
y.aspx

Hope this helps.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@microsof t.com.

=============== =============== =============== =====
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
=============== =============== =============== =====
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------

>NNTP-Posting-Date: Thu, 17 Jul 2008 06:26:09 -0500
>From: "Phil" <N/A>
>Newsgroups: microsoft.publi c.dotnet.langua ges.vb
>Subject: WebProxy.GetDef aultProxy
>Date: Thu, 17 Jul 2008 12:26:05 +0100

>
>According to the help this method is obsolete, but there is no hint as to
>what to use now instead.
>It does seem to work for me, although I get a warning error from the
>compiler.
>The warning message contains a link to the microsoft website, but this link
>just takes you to the .Net framework home page:
>http://go.microsoft.com/fwlink/?linkid=14202
>Can anyone provide the correct link and/or please explain what should now

be

>used instead of GetDefaultProxy .
>
>TIA
>Phil.
>
>
>
>

[Phil]

Re: WebProxy.GetDef aultProxy


"Steven Cheng [MSFT]" <stcheng@online .microsoft.comw rote in message
news:PZAuIDI6IH A.4972@TK2MSFTN GHUB02.phx.gbl. ..

Hi Phil,
>
As for the proxy setting support in .net framework 2.0, it's greatly
enhanced. The following article is a very good one which almost convers
all
the proxy related features in .net framework:
>
#Proxy Detection Take the Burden Off Users with Automatic Configuration in
NET
http://msdn.microsoft.com/en-us/magazine/cc300743.aspx
>
for the default proxy, in .net framework 2.0, it expose this via the
"WebRequest.Def aultWebProxy" property:
>
#WebRequest..:: .DefaultWebProx y Property
http://msdn.microsoft.com/en-us/libr...defaultwebprox
y.aspx
>

Thanks,

I'll take a look at this when I get a chance.

Cheers,
Phil.

[Steven Cheng [MSFT]]

Re: WebProxy.GetDef aultProxy

Thanks for your reply Phil,

No problem. If you have any further questions on this later, please feel
free to post here at your convenience.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@microsof t.com.

=============== =============== =============== =====
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.
=============== =============== =============== =====
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------

>Newsgroups: microsoft.publi c.dotnet.langua ges.vb
>References: <Vr-dnbEK17bMseLVnZ 2dneKdnZydnZ2d@ posted.plusnet>

<PZAuIDI6IHA.49 72@TK2MSFTNGHUB 02.phx.gbl>

>Subject: Re: WebProxy.GetDef aultProxy
>Date: Mon, 21 Jul 2008 17:19:28 +0100

>
>
>"Steven Cheng [MSFT]" <stcheng@online .microsoft.comw rote in message
>news:PZAuIDI6I HA.4972@TK2MSFT NGHUB02.phx.gbl ...

>Hi Phil,
>>
>As for the proxy setting support in .net framework 2.0, it's greatly
>enhanced. The following article is a very good one which almost convers
>all
>the proxy related features in .net framework:
>>
>#Proxy Detection Take the Burden Off Users with Automatic Configuration

in

>NET
>http://msdn.microsoft.com/en-us/magazine/cc300743.aspx
>>
>for the default proxy, in .net framework 2.0, it expose this via the
>"WebRequest.De faultWebProxy" property:
>>
>#WebRequest..: :.DefaultWebPro xy Property
>>

http://msdn.microsoft.com/en-us/libr...defaultwebprox

>y.aspx
>>

>Thanks,
>
>I'll take a look at this when I get a chance.
>
>Cheers,
>Phil.
>
>
>

[Phil]

Re: WebProxy.GetDef aultProxy

>

No problem. If you have any further questions on this later, please feel
free to post here at your convenience.
>

At the moment GetDefaultProxy seems to work fine here (we have ISA server on
our LAN). Am I likely to have any issues/problems with other proxies when we
start shipping the software out to other companies? At the moment I am
tempted to leave it as it is, and worry about it if/when users begin
reporting problems.

Cheers,
Phil.

[Steven Cheng [MSFT]]

Re: WebProxy.GetDef aultProxy

Thanks for your reply Phil,

The DefaultProxy you get is the existing one on the machine(for the user
context), if your target deployment environment also has such a default
proxy exists, that will also work well. If you fear that the environment
may be different, you may consider add a global configuration setting in
your application so that the use can manually specify a proxy address. And
in your application's startup code, you can assign this address to the
"WebRequest.Def aultWebProxy"
How do you think?

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@microsof t.com.

=============== =============== =============== =====
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

=============== =============== =============== =====
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------

>References: <Vr-dnbEK17bMseLVnZ 2dneKdnZydnZ2d@ posted.plusnet>

<PZAuIDI6IHA.49 72@TK2MSFTNGHUB 02.phx.gbl>
<1oCdnQ1eBOqNKh nVnZ2dnUVZ8qXin Z2d@posted.plus net>
<NS8Ryx56IHA.16 24@TK2MSFTNGHUB 02.phx.gbl>

>Subject: Re: WebProxy.GetDef aultProxy
>Date: Tue, 22 Jul 2008 14:09:49 +0100

>

>>
>No problem. If you have any further questions on this later, please feel
>free to post here at your convenience.
>>

>At the moment GetDefaultProxy seems to work fine here (we have ISA server

on

>our LAN). Am I likely to have any issues/problems with other proxies when

we

>start shipping the software out to other companies? At the moment I am
>tempted to leave it as it is, and worry about it if/when users begin
>reporting problems.
>
>Cheers,
>Phil.
>
>
>

[Steven Cheng [MSFT]]

Re: WebProxy.GetDef aultProxy

Hi Phil,

Do you still have any questions on this issue or is everything going well?

Sincerely,

Steven Cheng
Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@microsof t.com.

=============== =============== =============== =====
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

=============== =============== =============== =====
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------

>Content-Transfer-Encoding: 7bit
>From: stcheng@online. microsoft.com (Steven Cheng [MSFT])
>Organization : Microsoft
>Date: Wed, 23 Jul 2008 02:10:57 GMT
>Subject: Re: WebProxy.GetDef aultProxy

>
>Thanks for your reply Phil,
>
>The DefaultProxy you get is the existing one on the machine(for the user
>context), if your target deployment environment also has such a default
>proxy exists, that will also work well. If you fear that the environment
>may be different, you may consider add a global configuration setting in
>your application so that the use can manually specify a proxy address. And
>in your application's startup code, you can assign this address to the
>"WebRequest.De faultWebProxy"
>How do you think?
>
>Sincerely,
>
>Steven Cheng
>
>Microsoft MSDN Online Support Lead
>
>
>Delighting our customers is our #1 priority. We welcome your comments and
>suggestions about how we can improve the support we provide to you. Please
>feel free to let my manager know what you think of the level of service
>provided. You can send feedback directly to my manager at:
>msdnmg@microso ft.com.
>
>============== =============== =============== ======
>Get notification to my posts through email? Please refer to
>http://msdn.microsoft.com/subscripti...ault.aspx#noti

f

>ications.
>
>============== =============== =============== ======
>This posting is provided "AS IS" with no warranties, and confers no rights.
>--------------------

>>References: <Vr-dnbEK17bMseLVnZ 2dneKdnZydnZ2d@ posted.plusnet>

><PZAuIDI6IHA.4 972@TK2MSFTNGHU B02.phx.gbl>
><1oCdnQ1eBOqNK hnVnZ2dnUVZ8qXi nZ2d@posted.plu snet>
><NS8Ryx56IHA.1 624@TK2MSFTNGHU B02.phx.gbl>

>>Subject: Re: WebProxy.GetDef aultProxy
>>Date: Tue, 22 Jul 2008 14:09:49 +0100

>

>>

>>>
>>No problem. If you have any further questions on this later, please feel
>>free to post here at your convenience.
>>>

>>At the moment GetDefaultProxy seems to work fine here (we have ISA server

>on

>>our LAN). Am I likely to have any issues/problems with other proxies when

>we

>>start shipping the software out to other companies? At the moment I am
>>tempted to leave it as it is, and worry about it if/when users begin
>>reporting problems.
>>
>>Cheers,
>>Phil.
>>
>>
>>

>
>

[Phil]

Re: WebProxy.GetDef aultProxy

Do you still have any questions on this issue or is everything going well?
I think I now have enough information about where to look if/when it becomes
an issue, so I'm fine for now.
Thanks,
Phil.