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:
To be fair to the Sunday Mail, they are being pretty open about the fact that they were the ones handing out the badges, and I think I’ve been quoted accurately, which is reassuring.
(Photo from Sunday Mail, 4th November 2007)
Today at Blackwood Train station, I was interviewed by a Sunday Mail journalist.
Apparently they are running a campaign to encourage more investment in public transport, particularly after the problems the trains had yesterday with the computer system failing completely.
I didn’t make the copy in the final article - oh well.
Looks like I will need to get Owen’s autograph after all (he’s the guy on the left). I was sitting just out of shot behind the guy standing up near the door on the right :-)