Last 15 Messages:
Ok will do. Thanks
15/03/2007 19:02:32
RhinoMocks@googlegroups.com
In version 2.6.6 I made a major performance improvement that would make this
optimization a no-op, basically.
I suggest that you would upgrade to version 2.9.6 at the moment.
15/03/2007 15:45:04
RhinoMocks@googlegroups.com
2.6.0.43183
Don't get me wrong the tests are still fast when creating the mocks in every
test. Its just super fast relatively if you create the mock in the
testfixture setup and just call BackToRecord in setup.
Is this approach supported?
15/03/2007 15:36:29
RhinoMocks@googlegroups.com
What version of rhino mocks are you using?
You definitely should not get a slow down because of Rhino Mocks.
How much mock setup do you have?
15/03/2007 06:39:44
RhinoMocks@googlegroups.com
Hi Ayende,
Attached is a sample project if you need to understand what i'm referring
to. The problem we are seeing using Rhino Mocks is that we call verifyall on
all our tests, what we are noticing is that if one test fails, all tests
that run after it fails if they use the same mock even though running
15/03/2007 04:34:07
RhinoMocks@googlegroups.com
Fixed, thanks.
14/03/2007 21:08:49
RhinoMocks@googlegroups.com
That is because NoExpectations are handled in the interceptor level, not in
the mock state layer, thanks for finding it out.
12/03/2007 21:59:08
RhinoMocks@googlegroups.com
Hi Ayende,
Thanks for fixing this. This is definitely helpful to us.
When I tested the new implementation of CallOriginalMethod I went
across the following:
public class TestClass
{
public virtual void Method () { }
}
[Test]
public void TestName ()
{
MockRepository repository = new MockRepository ();
12/03/2007 21:45:34
RhinoMocks@googlegroups.com
Sorry for the long time it took.
Just run the tests on Mono Win32, and it certainly failed.
I pinged the mono group, we will see what they have to say about it.
12/03/2007 06:13:29
RhinoMocks@googlegroups.com
fixed.
10/03/2007 10:43:53
RhinoMocks@googlegroups.com
Yes, this is a Dynamic Proxy 2 bug.
09/03/2007 15:09:06
RhinoMocks@googlegroups.com
Fixed, thanks.
FYI, your code broke VS:
[link]
09/03/2007 14:53:03
RhinoMocks@googlegroups.com
Hello Ayende,
The problem definitely exists in Beta 4.
Regards, Michael
06/03/2007 15:53:55
RhinoMocks@googlegroups.com
Please try with the Beta 4 version.
I run into an issue committing the latest changes, so it is about a day old
in the repository.
06/03/2007 15:34:23
RhinoMocks@googlegroups.com
Hi,
Another issue with the current RhinoMocks revision from SVN:
System.TypeLoadException: The generic type 'InvocationMethod_11' was
used with the wrong number of generic arguments in assembly
'DynamicProxyGenAssembly2, Version=0.0.0.0, Culture
=neutral, PublicKeyToken=null'.
at IDoubleGeneric`1Proxy309f413fe bfc481095f519d1eb1df17e.Method [T]
06/03/2007 15:23:19
RhinoMocks@googlegroups.com