It would be me that happens to make the Visual Basic compiler crash!
As I’ve mentioned in the Rhino Mocks group, the crash appears to be caused by an interesting combination of a generic interface, another interface that inherits from the generic one, and a mock object that implements that interface. When you then try to use the new void method handling code (a new feature of Rhino Mocks 3.3) the compiler barfs (that’s a compiler technical term).
I’ve attached a simple project to the MS bug report that reproduces the crash. Please contact me if you are interested in the code.
The workaround is to revert to the pre-3.3 way of handing void method expectations:
eg. instead of this: