The truth is, we receive almost no support inquiries for Twirl... The people who use it seem to understand quite well what it does and how to use it.

Q: I'm developing a TWAIN DataSource (DS), and I am using Twirl to test and debug it. But when there is an exception in my DS, Twirl intercepts it and reports it, so Visual Studio never sees it. This makes it harder to debug my DS - Is there anything I can do about this?

A: Twirl version 1.36 is smart about this. When running under a debugger, including Visual Studio, Twirl steps aside and allows exceptions to propagate to the debugger.