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 On Sat, Oct 18, 2008 at 4:50 AM, Greg Nagel <[EMAIL PROTECTED]> wrote: > > 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" <[EMAIL PROTECTED]> wrote: > > What are the issues that you are seeing? > > > > On Fri, Oct 17, 2008 at 5:38 AM, Marcus Eklund <[EMAIL PROTECTED]> > wrote: > > > > > 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 > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
