Damn, I started replying to this yesterday morning and got distracted.

Anyway, if you're still having trouble, you can load the control's source code in one instance of Visual Studio, then use the Debug -> Attach to process dialog to attach to another instance of Visual Studio. Then when the exception is thrown in the designer in the second instance, you should get the full exception debug experience in the first.