Rhino Mocks V3.5 for 2.0 isn't for 2.0

[Marcus Eklund]

Hi,

I noticed yesterday when downloading Rhino Mocks V3.5 for 2.0 that it
isn't working for the .NET 2.0 framework but requires 3.5.

I redownloaded it a few times to be sure but still the same.

Rhino Mocks V3.4 works right, so anyone else had the same problem?

/Marcus

[jasonm...@gmail.com]

3.5 supports the AAA syntax which relies heavily on lamdas and
extension methods. If you download Rhino.Mocks from the trunk and
compile it will work for 2.0.

[Ayende Rahien]

What are the issues that you are seeing?

[Greg Nagel]

I just ran into this, too. There's a dependency on System.Core, but
only for ExtensionAttribute (Extension methods. There's a hack that
you can use to get around it:

http://www.danielmoth.com/Blog/2007/05/using-extension-methods-in-fx-20.html

Basically, just define ExtensionAttribute yourself.

On Oct 17, 4:08 am, "Ayende Rahien" <aye...@ayende.com> wrote:
> What are the issues that you are seeing?
>

[naraga]

Hi Marcus,

maybe very stupid and unaplicable idea but from my experience there
are not much constraints on which tools developer uses but there are
real constraints on what is deployed to customer. We have customers
that demands.net2 applications and that's it. you cannot do anything
about it. but i see unit tests as developer tool and there is nothing
that could stop me from using latest and hotest :) stuff. ok, there
might be company policies in place but most of the times these can be
"bend" so i can use my favorite shell enviroment or testing tools.
so if there are no licensing issues in your case (like old visual
studio or some other tool that is not aware of .net3.5) maybe you
should think about building your unit tests in with .net 3.5 in
separate project while having assemblies that are deployed to customer
in .net 2.0.
again, maybe unaplicable for you - just my 2 cents.

bye,
naraga

[Ayende Rahien]

That is a byproduct of compiling using the csc 3.5.
I tested this on VS 2005, and it worked just fine.

A simple solution is to have the test project as 3.5, but I'll try to fix this with 3.5.1