I just upgraded my Rhino Mocks library and started getting the
compiler errors with Expect.Call. I found a couple others that had the
same issue when using VB.Net but didn't see anyone talking about the
problem other than to say that it doesn't work under VB anymore.

I did some testing and I think I found an explanation that I am able
to reproduce.

The issue is basically because VB treats static classes as modules and
because the extended class is a generic (and because the extension
method shares the same name as a class in the same namespace).

I wrote up all the details here:
http://chrismay.org/2010/07/05/Rhino+Mocks+VBNET+Extension+Methods+And+Expect+Compiler+Problems.aspx

I believe that this could be resolved just by changing the namespace
of the RhinoMocksExtensions class to anything other than Rhino.Mocks,
and I'm not sure but I think that change wouldn't require any other
changes to the Rhino Mocks codebase.

-- 
You received this message because you are subscribed to the Google Groups 
"Rhino.Mocks" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/rhinomocks?hl=en.

Reply via email to