L
Laura Stern
Guest
I have to apologize that after all this error handling banter I really don't know what the issue is. As someone (Peter Judge?) had answered in the prior conversation (that I can't see here) you should make sure there is an error message in your AppErrors by passing 2 parameters to the constructor (message and #) or using the AddMessage method. Then you can always get the message with GetMessage. Why would you care about ReturnValue? That is only really there for backward compatibility with non-structured error handling. The Error interface will work for all error types, including .NET exceptions. You can have a single catch block or more than one. If you only have one you can always test the type of the actual error object you got if you need to get extra information from that specific type - like ReturnValue if you still want to use that. You can have both a ReturnValue and an error message in the same AppError. So what's the question/problem?
Continue reading...
Continue reading...