Link to home
Start Free TrialLog in
Avatar of pointeman
pointemanFlag for United States of America

asked on

Class Library Exception Passing To Other Class Library Or Executable?

I want to learn the absolute correct way to pass exceptions from Class Library .dll to other .dll or Executable (Form1). I don't receive the actual .dll exception, instead I receive a general try/catch exception from the Form1 attempt to use the .dll. Help!

[Example Summary]
Click a button on Form1 to clear the local Queue without first specifying the Queue name will cause an exception.
Seems to me the the .dll CreateQueue() exception should 'bubble-up' to Form1.

Does this make sense?

Q1. How do I pass the .dll exception to the .exe (MyForm1)?
Q2. How do I pass the .dll exception to another .dll then to .exe (MyForm1)?

public static void ClearQueue()
            msgQueue.QueueName = ""; //intentionally blank for testing purposes

[MyQueueManager.dll] (referenced by MyForm1.exe)
        public static void CreateQueue()
                if (MessageQueue.Exists(_queueName))
                    msgQueue = new MessageQueue(_queueName);
                    msgQueue = MessageQueue.Create(_queueName);
            catch (MessageQueueException ex)
                throw new Exception("MsmqManager.MSMQueue.CreateQueue() Exception: ", ex);

        public static void ClearQueue()

Avatar of Gary Davis
Gary Davis
Flag of United States of America image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of pointeman


Q. Do you think the .dll 'Catch' is correct or do you recommend another way?
The try/catch in the dll looks correct to me.
Q. Do you prefer throw ex; vs my code example?

I've also been working with throw ex.Innexcepion; as well.
I'm not sure I understand. Your example does issue a throw.