NewsBot
1
I’m beginning work on a re-write of one of our major VB6 programs.* This program uses several COM+ components, also written in VB6, which I am going to re-write (and re-architect while I’m at it) into C# using VS 2008.* Several of the methods I used in the COM+ components returned various information, like ADO Recordset, etc.* However, I also wanted to return any error information that might have occurred on the server while it was executing, to the client application.* Since I didn’t think I could return the VB6 Err object to the calling client application I instead would return the Err.Source, Err.Number and Err.Description as parameters in the COM+ method’s signature to the client application.* I would assume that the same thing would hold true for any Exception object in .NET; specifically that the Exception object would be a part of the process under which the WCF service runs and so it could not be sent to the calling application.
So, I want to do basically the same thing that I did with the COM+ components, but use WCF instead.* Of course I can return the Exception object’s Message property*and possibly InnerMessage property in the service’s parameter list, but I would like to know if there is anything else analogous to the Err.Number and Err.Source properties in VB6?
More...
View All Our Microsoft Related Feeds
So, I want to do basically the same thing that I did with the COM+ components, but use WCF instead.* Of course I can return the Exception object’s Message property*and possibly InnerMessage property in the service’s parameter list, but I would like to know if there is anything else analogous to the Err.Number and Err.Source properties in VB6?
More...
View All Our Microsoft Related Feeds