Since we updated our version of Visual Studio for Mac to 7.2 (including an update to Mono 5.4.0.201) all of our tests that stubs a virtual property fails when we extract the object out of the Mock.

Here is the stacktrace :
https://gist.github.com/gabsima-nexapp/f405c0ecde752fc578d57c6dcff72401
Line 32 of the stack trace corresponds to the last line of my screenshot.
Thanks for the report. May I ask, what is the actual exception thrown, and the exception message?
I'm affraid i don't have more information than the stack trace... It seems that Mono is having a SIGABRT when Moq tries to create a proxy.
What version of Moq are you using? Have you tried any other (older) versions? If not, could you please try to find the first version of Moq that breaks your tests in the way you reported?
We have Moq version 4.7.137.
The only version i found where the problem is unexistant is with 3.1.416.3. Every version after this one seems to have the same behavior with my tests so from 4.0.10827 and upward.
We've been able to use a previous version of the Mono framework (5.2.0) and our tests are now working like before the update. It seems to be a compatibility problem between Moq and the latest version of Mono.
The only version i found where the problem is unexistant is with 3.1.416.3.
(I am going to assume that you didn't artificially pin Castle Core to version 4.2.0 while you ran your Moq downgrade experiment.)
That version is several years old. If there were such an grave problem in Moq such that it could no longer deal with virtual methods, then that would've been discovered long, long ago. I hate to tell you the obvious, but I am reasonably sure the problem is in your environment, not Moq.
Since we updated our version of Visual Studio for Mac to 7.2 (including an update to Mono 5.4.0.201) all of our tests that stubs a virtual property fails when we extract the object out of the Mock.
Is it possible for you to install the version of Mono you used previously, then run your tests using it? (You posted seconds before I did, so apparently you've already tried that successfully.)
@gabsima-nexapp - I suppose it would be good if you checked whether this problem has already been reported with Mono; and if not, I'm sure they would appreciate your bug report.
Is there anything else that you feel should be done from Moq's side, or can we close this issue?
Thank you, it seems it has already been logged in mono's bugzilla. Thanks for the support!
@gabsima-nexapp Could you link to that issue in mono's bugzilla? I can't seem to find it and I'd like to follow it.
Sure, here it is https://bugzilla.xamarin.com/show_bug.cgi?id=29953
Most helpful comment
Sure, here it is https://bugzilla.xamarin.com/show_bug.cgi?id=29953