Skip to main content

I'm playing with the client API, and I'm finding that most exception types are really not helpfull to ensure clean design in my client application

First, I didn't have the exact reason, but I was getting object null reference exception when fiddling with the connection string, which is all but helpfull to diagnostic the problem.

Second, when I'm openingĀ  a worklist item with an unauthorized user, I'm getting System.Exception which give me no way to handle that properly.

When looking up the class library reference chm, there is nothing telling me what are the exceptions I could get etc.

I'm just begining to dive into the client API but theses findings leave a lot to be enhanced.

Please do not use base exception for such common case, also please check argument and throw according exceptions rather than getting null reference exception from within the API which has no meaning to API client

Be the first to reply!

Reply