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 On Oct 17, 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 -~----------~----~----~----~------~----~------~--~---
