The first line is a constructor and that should always work because  you need to create a new object. This means that in the constructor there is no attempt of doing any remote connection. The second line throws the exception because that's where the API is trying to connect to the remote server.

To catch an exception in .net you need to use the try-catch statement. If you only want to catch SecurityAccessDeniedException then you need to specify this exception type in your catch block. This class is available in System.ServiceModel.Security namespace which is part of the System.ServiceModel.dll. You will need to add this as a reference to you project.

The first line is a constructor and that should always work because  you need to create a new object. This means that in the constructor there is no attempt of doing any remote connection. The second line throws the exception because that's where the API is trying to connect to the remote server.

To catch an exception in .net you need to use the try-catch statement. If you only want to catch SecurityAccessDeniedException then you need to specify this exception type in your catch block. This class is available in System.ServiceModel.Security namespace which is part of the System.ServiceModel.dll. You will need to add this as a reference to you project.

Hi Romulus,

Thanks for the answer, I was able to catch the exception after adding the System.ServiceModel.dll reference.

>The first line is a constructor and that should always work because  you need to create a new object.

Personally I disagree because I prefer "fail-fast" approach because the object is unusable,

but yes I understand now not everyone agrees on this design decision.

However, I should point out the constructor DOES throw a "EntryPointNotFoundException" if you pass an invalid Uri.