How can I find out what kind of exceptions can be thrown by a method?

Question

I'm writing code that calls the following method that exists in Windows.Networking.PushNotifications

// Summary:
//     Creates objects that you use to retrieve push notification channels from
//     the Windows Push Notification Services (WNS). These channels are bound to
//     an app or secondary tile.
[Threading(ThreadingModel.MTA)]
[Version(100794368)]
public static class PushNotificationChannelManager
{
    // Summary:
    //     Creates an object, bound to the calling app, through which you retrieve a
    //     push notification channel from Windows Push Notification Services (WNS).
    //
    // Returns:
    //     The object, bound to the calling app, that is used to request a PushNotificationChannel
    //     from the Windows Push Notification Services (WNS).
    [Overload("CreatePushNotificationChannelForApplicationAsync")]
    public static IAsyncOperation<PushNotificationChannel> CreatePushNotificationChannelForApplicationAsync();

}

I want to be sure to cover all cases where exceptions can be thrown and deal with each appropriately. Is it possible for me to get a list of the different types of exceptions this can throw and different circumstances which could cause them?

I don't want to just have a catch-all

catch(Exception ex) { }    

This MSDN article states that "An exception is thrown if you attempt to register a WNS push notification channel when there is no data connection". However it doesn't state what type of exception or if there are other cases when an exception can be thrown.

How can I find out if there are other possible exception types?

Answer 1

The only way is documentation and source code, although notice that so many other exceptions might be thrown like OutOfMemoryException, TypeLoadException, ThreadAbortException and ... so the right approach in my opinion is catch the exceptions you can do something about them and let others bubble up the call stack.

also read this Vexing exceptions

Answer 2

If you can simulate one of the error conditions mentioned in that link, you should be able to use a generic exception catch to see the type that's thrown.

I think it's going to throw a System.Runtime.InteropServices.COMException though based on the error codes mentioned in the article though.