"Cannot set parent to an interface" calling GeneratePartialMock()

[Luis Ferreira]

Calling GeneratePartialMock() on a complex generic type is giving me the error "Cannot set parent to an interface".

According to what I read in several places, the error originates at the DynamicProxy library and it was due to a bug that has already been corrected.

Any clue when a new Rhino Mocks build incorporating the latest Castle DynamicProxy version will be available?

Or is there a current workaround?

Thanks.

[Patrick Steele]

You could probably fork it (https://github.com/RhinoMocks/RhinoMocks) and update to the latest DP (and then send a pull request).

---
Patrick Steele
http://weblogs.asp.net/psteele

--
You received this message because you are subscribed to the Google Groups "Rhino.Mocks" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rhinomocks+...@googlegroups.com.
To post to this group, send email to rhino...@googlegroups.com.
Visit this group at http://groups.google.com/group/rhinomocks?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Luis Ferreira]

I don't really know how to use github for that purpose.

Anyway I'm following your suggestion in the sense that I downloaded the sources ZIP file and I'm gonna try to get my own custom build going.
If it solves my problem, I'll post the results here.

Thanks!

[haifisch]

Or you just try one of these
https://github.com/alaendle/rhino-mocks/downloads

I even thought that https://github.com/hibernating-rhinos/rhino-mocks/network/members is the "official" rhino-mocks tree :-(
Why is there a new tree!? (https://github.com/RhinoMocks/RhinoMocks/network/members)

Br,

Andreas

[Luis Ferreira]

Here is a quick update of what I've done so far:

1) I downloaded the ZIP source file (http://hibernatingrhinos.com/downloads/rhino-mocks/latest)
2) Tried to build it but couldn't since all the AssemblyInfo.cs files were missing.
3) Created an empty Assemblyinfo.cs files for all projects. Removed the options to storngly sign the assemblies.
4) Had to comment or change 3 test cases (Rhino.Mocks.Tests project) and 1 test-related file (Rhino.Mocks.Tests.Model) as a side-effect of not strongly signing the assemblies and conversion to .NET 4.0.

In the end, it worked, and the error I was getting is now gone. Hurray!

I suggest that someone really involved in the project moves ahead and does a proper strongly-signed build of it, since it's apparently not that difficult. And would reduce his karma. :-)