Thanks Ayende for a response,
1.) I mentioned before that I have InternalsVisibleTo attribute
properly set in my assembly under test. And it works, I can access
internal methods and constructors from testing assembly. It's just the
creation of mocks that does not seem to respect it. No matter if I try
MockRepository.GenerateStub<T>, MockRepository.GenerateMock<T> or
their equivalents (Partial, Dynamic, Strict) - It does not see that
internal (but theoretically "visible") constructor.
2). "But probably it will not work because the code assumes that you
are trying
to call a public ctor. "
Yes, indeed. When changing the access modifier to public that works,
but the problem is that I do not want to make it public.
However now I see that I can't do anything about it with Rhino so I
should better change a bit my design to ease testing it.
But maybe is it possible to change RM to support this in future
releases?:)
Thanks for explanation.
Łukasz Podolak
On 13 Sie, 16:34, "Ayende Rahien" <
aye...@ayende.com> wrote:
> You need to use InternalsVisibleTo, IIRC.
> But probably it will not work because the code assumes that you are trying
> to call a public ctor.
>
> 2008/8/13 Łukasz Podolak <
lukasz.podo...@gmail.com>