Yes, everything is virtual/abstract/interface methods, and everything was working fine until I changed the access modifiers from public(MonoDevelop's default) to internal.
On Mon, Jul 12, 2010 at 9:03 AM, Alex McMahon <[email protected]> wrote: > Is the method/property you're trying to mock virtual/abstract or on an > interface? If not, Rhino Mocks can't mock it. > > On 12 July 2010 13:00, Thiago Padilha <[email protected]> wrote: >> >> Is there any way to allow this? I use some internal types on my >> tested assembly just to better separate concerns, but theres no point >> in making them public. I've already placed [assembly: >> InternalsVisibleTo("Rhino.Mocks")] but it stills complain about types >> not being public. >> >> -- >> 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. >> > > -- > 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. > -- 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.
