-
-
Notifications
You must be signed in to change notification settings - Fork 798
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ref keyword in interface method declaration causes exception #42
Comments
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 notifications@git.luolix.topwrote:
|
It appears this was fix when upgrading to Castle 3.3.3 #204. |
@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). |
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:
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.
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?
edit: I noticed in the stacktrace that the exception is thrown in Castle, so I submitted an issue report there too.
The text was updated successfully, but these errors were encountered: