System.Net.WebC lient Best Practices

[jmhmaine]

I've used the WebClient class on a few projects but I wanted to know if
anyone could point to the good resource for Best Practices with this object.

The two things I haven't seen in sample code are:
1. How to retrieve connection error messages, such as a DNS resolution error
or connection dropped errors.
2. Should I use the Dispose or Finalize methods to destroy the object when I
done? I assume that the object uses unmanaged code at some point to connect
to another server. So do I need to use the Finalize method release those
other objects?

Here is a function from one of my projects:

Private Function getRemoteDat() As Boolean
Dim CCPostURL As String =
ConfigurationSe ttings.AppSetti ngs("https://www.remoteData. com/process.asp")

Dim Status As Boolean = False ' Assumes failure until set to True
Dim ResponseResults As String
Dim responseString As String
Dim myWebClient As New System.Net.WebC lient
Dim responseArray As Byte()
Dim myNameValueColl ection As New
System.Collecti ons.Specialized .NameValueColle ction
Dim ResultMsg As String
Dim splitResponse() As String

myNameValueColl ection.Add("fir st_name", txtBillFName.Te xt)
myNameValueColl ection.Add("las t_name", txtBillLName.Te xt)
myNameValueColl ection.Add("add ress", txtBillAdd1.Tex t)

Try
responseArray = myWebClient.Upl oadValues(CCPos tURL, "POST",
myNameValueColl ection) 'Sends request to Gateway
responseString = System.Text.Enc oding.ASCII.Get String(response Array)
'Converts bit array to string
splitResponse = Split(responseS tring, System.Environm ent.NewLine)
'Splits response into string array
ResultMsg = splitResponse(1 ).Remove(0, 19) 'Gets Result Message
Catch
Status = False 'Connection failed or response was corrupted
End Try

If ResultMsg = "APPROVED" Then
_GatewayApprova lString = splitResponse(2 ) & "|" & splitResponse(3 )
'Set string if successful
Status = True
Else
Status = False
End If

Return Status
End Function

[Steven Cheng[MSFT]]

Hi jmh,

Welcome to ASP.NET newsgroup.
Regarding on the "System.Net.Web Client Best Practices" you mentioned, here
are some of my suggestions:

The WebClient class in system.net namespace is a well-encapsulated class
which just simulate the IE browser's behavior. When we use it to post data
or retrieve response from remote url, it will help do the underlying
connection and transfering tasks for us(also some additinal works such as
cookie management). In fact, the WebClient class is using the
HttpWebRequest class internally when dealing with http... resource. So if
we need more detailed and
underlying control when doing such work, we can consider directly use the
HttpWebRequest class instead. This class can help us manually write binary
data into the http request's stream and customize the http Message's header
Also, we can get the http status code after we make request and retieve
response from the remote resource. For detailed reference on
HttpWebRequest , you can lookup the MSDN document on it(or the accessing
internet section in "programmin g with .net section).

In addition, since httpWebrequest have more underlying controls, it also
require us to do more works to properly handle the resource. for example,
we need to manually close the response stream after read it so as not to
occupy the connection. Here are some tech articles and former newsgroup
threads discussing on such problems, such as use httpwebrequest to post
data, upload file or upload files together with form datas:
#Send data from non browser client (using HttpWebRequest) that can be used
by access web page controls.
http://weblogs.asp.net/ngur/archive/...11/129951.aspx

#how to upload file via c# code
http://groups-beta.google.com/group/...nguages.csharp
/browse_thread/thread/eea92e16a26fbdc 0/474b6a3fcd63dd9 3?q=C%23+upload +file+s
teven+cheng&rnu m=1&hl=en#474b6 a3fcd63dd93

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)