Hi Tim,

>This doesn't seem like the best idea to place a lock in a method that doesn't also unlock it.

That's true.

> Essentially, I need to queue the commands up in the command processor itself so it receives the responses in the same order.

Can't you create a command collection that is processed instead of separate commands? Then the event could initiate the next command when the first one has completed until the entire collection has been processed.