ref keyword in interface method declaration causes exception about moq4 HOT 4 CLOSED

yuck, could you also post that question to the Castle DynamicProxy guys?

/kzu

Daniel Cazzulino

On Tue, Apr 9, 2013 at 2:54 PM, Pier Janssen [email protected]:

I'm writing unittests for an application which makes use of a third party
API, with some generated interfaces. I was getting some strange exceptions
trying to create a mock object for a complex interface. After much digging,
I found that one of these interfaces it extends has a declaration with a
ref keyword in it:

public interface IReferenceMaker{
RefResult NotifyRefChanged(ref UIntPtr partID, RefMessage message);}

When trying to create a mock object for this interface, an exception is
thrown when accessing the Object property: ArgumentException: Type
System.UIntPtr could not be converted to a OpCode.

Mock mockRefMaker = new Mock();IReferenceMaker refMaker = mockRefMaker.Object;

Unfortunately I can't change the interface in any way, so I'm looking for
a way to work around the issue on the Moq side.
Any ideas?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/42
.

from moq4.

Done: http://issues.castleproject.org/issue/DYNPROXY-188

from moq4.

It appears this was fix when upgrading to Castle 3.3.3 #204.

from moq4.

@dtuchlinsky: Thanks for the hint. This was fixed back in version 4.2.1510.2205 (which was the first version based on Castle 3.3.3).

from moq4.