469,955 Members | 1,402 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,955 developers. It's quick & easy.

WebProxy.GetDefaultProxy

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.

Jul 17 '08 #1
7 2808
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.DefaultWebProxy" property:

#WebRequest..::.DefaultWebProxy 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:
ms****@microsoft.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.public.dotnet.languages.vb
Subject: WebProxy.GetDefaultProxy
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.

Jul 18 '08 #2

"Steven Cheng [MSFT]" <st*****@online.microsoft.comwrote in message
news:PZ**************@TK2MSFTNGHUB02.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.DefaultWebProxy" property:

#WebRequest..::.DefaultWebProxy 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.
Jul 21 '08 #3
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:
ms****@microsoft.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.public.dotnet.languages.vb
References: <Vr******************************@posted.plusnet >
<PZ**************@TK2MSFTNGHUB02.phx.gbl>
>Subject: Re: WebProxy.GetDefaultProxy
Date: Mon, 21 Jul 2008 17:19:28 +0100
>

"Steven Cheng [MSFT]" <st*****@online.microsoft.comwrote in message
news:PZ**************@TK2MSFTNGHUB02.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.DefaultWebProxy" property:

#WebRequest..::.DefaultWebProxy 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.
Jul 22 '08 #4
>
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.
Jul 22 '08 #5
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.DefaultWebProxy"
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:
ms****@microsoft.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******************************@posted.plusnet >
<PZ**************@TK2MSFTNGHUB02.phx.gbl>
<1o******************************@posted.plusnet >
<NS**************@TK2MSFTNGHUB02.phx.gbl>
>Subject: Re: WebProxy.GetDefaultProxy
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.
Jul 23 '08 #6
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:
ms****@microsoft.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: st*****@online.microsoft.com (Steven Cheng [MSFT])
Organization: Microsoft
Date: Wed, 23 Jul 2008 02:10:57 GMT
Subject: Re: WebProxy.GetDefaultProxy
>
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.DefaultWebProxy"
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:
ms****@microsoft.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******************************@posted.plusnet >
<PZ**************@TK2MSFTNGHUB02.phx.gbl>
<1o******************************@posted.plusne t>
<NS**************@TK2MSFTNGHUB02.phx.gbl>
>>Subject: Re: WebProxy.GetDefaultProxy
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.

Jul 25 '08 #7
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.
Jul 28 '08 #8

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by Jamie Laundon | last post: by
1 post views Thread by Jim Douglas | last post: by
2 posts views Thread by Ricardo Luceac | last post: by
4 posts views Thread by vooose | last post: by
2 posts views Thread by Sam Santiago | last post: by
reply views Thread by Michael S. Scherotter | last post: by
4 posts views Thread by Andrew | last post: by
3 posts views Thread by =?Utf-8?B?TXJOb2JvZHk=?= | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.