Peter,
VBScript is not the intended client. It just happens that a legacy
application uses VB scripts to get things done in an area where rules change
almost everyday. VB scripts allows them to change that part of the
application to be very dynamic.
The application that uses these VB scripts are written in C++ (unmanaged).
VB scripts do not understand exceptions but the err object mostly gets all
exception information, I guess, through the GetLastError API. .NET runtime
sets the last error when exception occurs upon calls from a COM object.
Thanks.
James
[quoted text, click to view] "Peter Bradley" wrote:
> Does VBScript understand exceptions? I didn't think it did. Why are you
> using VBScript?
>
> However, since I'd rather have my hand cut off than "program" in VBScript, I
> could very well be totally incorrect about what VBScript can and can't do.
>
>
> Peter
>
> "James" <James@discussions.microsoft.com> wrote in message
> news:658F1ADD-688E-465B-9EE0-88350442EDFA@microsoft.com...
> >I have a remoting object hosted in a Windows Service. One of the clients is
> >a
> > VBScript that invokes a proxy CCW dll. The script gets all
> > ApplicationException details but no system exception
> > (Exception,SqlException
> > etc) details.
> >
> > An example error message displayed has:
> >
> > Error: System error.
> > Code: 80131904
> > Source: .Net SqlClient Data Provider.
> >
> > On the server I can see the correct information. A .net client gets the
> > correct information as well.
> >
> > If I wrap the exception in an Application Exception by
> > catch (Exception ex)
> > {
> > throw new ApplicationException(ex.Message, ex);
> > }
> > VBScript gets the error message correctly.
> >
> > How can I get the correct exception details in a VBScript?
>
>
Seems you've answered your own question, then, haven't you?
Cheers
Peter
[quoted text, click to view] "James" <James@discussions.microsoft.com> wrote in message
news:C394685B-9EFE-49EE-B497-A8F84BCF0465@microsoft.com...
> Peter,
>
> VBScript is not the intended client. It just happens that a legacy
> application uses VB scripts to get things done in an area where rules
> change
> almost everyday. VB scripts allows them to change that part of the
> application to be very dynamic.
>
> The application that uses these VB scripts are written in C++ (unmanaged).
>
> VB scripts do not understand exceptions but the err object mostly gets all
> exception information, I guess, through the GetLastError API. .NET runtime
> sets the last error when exception occurs upon calls from a COM object.
>
> Thanks.
> James
>
> "Peter Bradley" wrote:
>
>> Does VBScript understand exceptions? I didn't think it did. Why are you
>> using VBScript?
>>
>> However, since I'd rather have my hand cut off than "program" in
>> VBScript, I
>> could very well be totally incorrect about what VBScript can and can't
>> do.
>>
>>
>> Peter
>>
>> "James" <James@discussions.microsoft.com> wrote in message
>> news:658F1ADD-688E-465B-9EE0-88350442EDFA@microsoft.com...
>> >I have a remoting object hosted in a Windows Service. One of the clients
>> >is
>> >a
>> > VBScript that invokes a proxy CCW dll. The script gets all
>> > ApplicationException details but no system exception
>> > (Exception,SqlException
>> > etc) details.
>> >
>> > An example error message displayed has:
>> >
>> > Error: System error.
>> > Code: 80131904
>> > Source: .Net SqlClient Data Provider.
>> >
>> > On the server I can see the correct information. A .net client gets the
>> > correct information as well.
>> >
>> > If I wrap the exception in an Application Exception by
>> > catch (Exception ex)
>> > {
>> > throw new ApplicationException(ex.Message, ex);
>> > }
>> > VBScript gets the error message correctly.
>> >
>> > How can I get the correct exception details in a VBScript?
>>
>>
>>
