> I'm working on error handling in my program and need some input.
>
> Dim errorsFound As Boolean = False
> Dim respstr As String
> Try
>   respstr = proxy.validate(soapmesg)
> Catch ex As Exception
>   errorLabel.Text = ex.Message
>   errorsFound = True
> End Try
> If Not errorsFound .....
>
> I'd rather not use boolean errorsFound.  What I don't know is if an
> exception occured in respstr=proxy.validate(soapmesg) can I count on
> respstr being empty?  If so I'll just say If not respstr = ""

> Chris wrote:
>> Unless you wrote or have documenation to what returns during an error
>> you should not count on respstr being anything.  I would reset it any
>> time there is an error.
>>
>> Try
>>   respstr = proxy.validate(soapmesg)
>> Catch ex As Exception
>>   errorLabel.Text = ex.Message
>>   respstr = string.empty
>> End Try
>
> Or initialize respstr outside of the try block:
>
> respstr = string.empty
> Try
>   respstr = proxy.validate(soapmesg)
> Catch ex As Exception
>   errorLabel.Text = ex.Message
> End Try
>
> You could then use it (and therefore test if it is empty) outside of the try
> block.
>
>

> Oh Oh, in my haste to make an example I forgot to say Dim respstr As
> String = ""
>
> Sorry
>
> The point to the question is is could respstr=proxy.validate(soapmesg)
> set respstr to something if it generates an exception?
>
> You're indicating it would not.  I tend to agree.  But Chris said it
> might.  I don't know how firm each of you are in your beliefs.  Let's
> see what some others have to say.  And by all means feel free to reply
> again yourself.
>
>
> Leon Mayne wrote:
>> Chris wrote:
>>> Unless you wrote or have documenation to what returns during an error
>>> you should not count on respstr being anything.  I would reset it any
>>> time there is an error.
>>>
>>> Try
>>>   respstr = proxy.validate(soapmesg)
>>> Catch ex As Exception
>>>   errorLabel.Text = ex.Message
>>>   respstr = string.empty
>>> End Try
>>
>> Or initialize respstr outside of the try block:
>>
>> respstr = string.empty
>> Try
>>   respstr = proxy.validate(soapmesg)
>> Catch ex As Exception
>>   errorLabel.Text = ex.Message
>> End Try
>>
>> You could then use it (and therefore test if it is empty) outside of
>> the try block.
>>

> Hi,
>
> If the exception occured when we call the proxy.validate(soapmesg), then 
> respstr will be untouched.
>
> Also if you do not continue the process in the function, why not just
> return in the catch.
> If you have finally code, just put it in the Finally block.
>
> You may try to run the code below.
>
>         Try
>             Throw New Exception("Test")
>         Catch ex As Exception
>             MsgBox(ex.ToString())
>             Return
>         Finally
>             MsgBox("Finally called")
>         End Try
>
> If you still have any concern, please feel free to post here.
>
> Best regards,
>
> Peter Huang
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
> This posting is provided "AS IS" with no warranties, and confers no rights.
>

> Hi,
>
> If the exception occured when we call the proxy.validate(soapmesg), then 
> respstr will be untouched.
>
> Also if you do not continue the process in the function, why not just
> return in the catch.
> If you have finally code, just put it in the Finally block.
>
> You may try to run the code below.
>
>         Try
>             Throw New Exception("Test")
>         Catch ex As Exception
>             MsgBox(ex.ToString())
>             Return
>         Finally
>             MsgBox("Finally called")
>         End Try
>
> If you still have any concern, please feel free to post here.
>
> Best regards,
>
> Peter Huang
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
> This posting is provided "AS IS" with no warranties, and confers no rights.
>

> Hi
>
> I think you may take a look at the code below for your reference.
>
> I can not test based on all the possibility, but commonly if the 
> request.GetResponse(); throw exception, the response will be null;
>
>         static void Main(string[] args)
>         {
>
>                 // Create a request for the URL.
>                 WebRequest request = WebRequest.Create(
>                   "http://localhost");
>                 // If required by the server, set the credentials.
>                // request.Credentials = CredentialCache.DefaultCredentials;
>                 WebResponse response = null;
>                 try
>                 {
>                     // Get the response.
>                     response = request.GetResponse();
>                     // Display the status.
>                 }
>                 catch (Exception ex)
>                 {
>                     Console.WriteLine(ex.ToString());
>                 }
>                 if (response != null)
>                 {
>                    
> Console.WriteLine(((HttpWebResponse)response).StatusDescription);
>                     // Get the stream containing content returned by the
> server.
>                     Stream dataStream = response.GetResponseStream();
>                     // Open the stream using a StreamReader for easy access.
>                     StreamReader reader = new StreamReader(dataStream);
>                     // Read the content.
>                     string responseFromServer = reader.ReadToEnd();
>                     // Display the content.
>                     Console.WriteLine(responseFromServer);
>                     // Clean up the streams and the response.
>                     reader.Close();
>                     response.Close();
>                 }
>        
>         }
>
> Also from VB.NET 2005, we have a continue keyword, which can be used to go
> the next iteration of the loop without go through the all the following
> code.
>
> Best regards,
>
> Peter Huang
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
> This posting is provided "AS IS" with no warranties, and confers no rights.
>

> cj wrote:
>> Oh Oh, in my haste to make an example I forgot to say Dim respstr As
>> String = ""
>>
>> Sorry
>>
>> The point to the question is is could respstr=proxy.validate(soapmesg)
>> set respstr to something if it generates an exception?
>>
>> You're indicating it would not.  I tend to agree.  But Chris said it
>> might.  I don't know how firm each of you are in your beliefs.  Let's
>> see what some others have to say.  And by all means feel free to reply
>> again yourself.
>>
>>
>> Leon Mayne wrote:
>>> Chris wrote:
>>>> Unless you wrote or have documenation to what returns during an error
>>>> you should not count on respstr being anything.  I would reset it any
>>>> time there is an error.
>>>>
>>>> Try
>>>>   respstr = proxy.validate(soapmesg)
>>>> Catch ex As Exception
>>>>   errorLabel.Text = ex.Message
>>>>   respstr = string.empty
>>>> End Try
>>>
>>> Or initialize respstr outside of the try block:
>>>
>>> respstr = string.empty
>>> Try
>>>   respstr = proxy.validate(soapmesg)
>>> Catch ex As Exception
>>>   errorLabel.Text = ex.Message
>>> End Try
>>>
>>> You could then use it (and therefore test if it is empty) outside of
>>> the try block.
>>>
>
>
> I'm not sure if it will or not, but my theory is, why should I risk it?
>
> Chris

> cj wrote:
>> I'm working on error handling in my program and need some input.
>>
>> Dim errorsFound As Boolean = False
>> Dim respstr As String
>> Try
>>   respstr = proxy.validate(soapmesg)
>> Catch ex As Exception
>>   errorLabel.Text = ex.Message
>>   errorsFound = True
>> End Try
>> If Not errorsFound .....
>>
>> I'd rather not use boolean errorsFound.  What I don't know is if an
>> exception occured in respstr=proxy.validate(soapmesg) can I count on
>> respstr being empty?  If so I'll just say If not respstr = ""
>
> Unless you wrote or have documenation to what returns during an error
> you should not count on respstr being anything.  I would reset it any
> time there is an error.
>
> Try
>   respstr = proxy.validate(soapmesg)
> Catch ex As Exception
>   errorLabel.Text = ex.Message
>   respstr = string.empty
> End Try
>
> Another thought would be to leave the funtion if there is an error.

> cj wrote:
>> Good idea.  Are you sure it's necessary?  Leon seems to think that if
>> that line throws and exception it would not have changed the value of
>> respstr.  Take a look at my response to his message.  Thanks!
>
> Ah right, I see what you're saying now. In theory respstr should be empty if
> the function call threw an exception, as there would not have been a return
> value. So you should be able to rely on respstr being empty, yes.
>
>