@ Head

Hi Dave,

Yes, it's only designed for DXCore 2.0.  that's a major version upgrade, so I went with supporting jsut the one flavour.  It was originally written against 1.2, so should probably work there, except you'd have ot manually install.
The new version of Refactor for VB (that uses DXCore) should be available very soon :)  The Pro version has already been released.

Thanks Alex :)

Hi Michael,

the concept of using static code analysis was considered.  It does however get very complex as you need to walk down every method call, determine what exceptions can be raised, what are handled, and whether or not any handling is conditional.  It's a lot of work, and would most likely end in false positives. (at least that'd be better than omitting exceptions <g>)

But even if we did that, and we then got a list of exceptions, you really have to ask what value is that to the user if there is no documentation as to why those exceptions might be raised.  

For example, let's say you call method
Foo(a,b,c,d)
Which we determine somehwere in the code graph throws an ArguementNullException.  how much use to you is that, unless we tell you whether it's a, b, c and/or d that applies to ?  and what if the ArguementNullException is thrown by a method that Foo calls, and is not directly linked to a, b, c or d.

So at the end of the day, I think what you really need is the documentation.  so that's why we went the easy route of using the XML documentation, as it is also really the best route ;)