Good point. I can think of two reasons: 1. Theoretically, by targeting test to 2.0 we ensure the production code was tested under framework 2.0 instead of 3.5. Hence, it is guaranteed to work in a system without 3.5 installed. Practically, how real is this? I don't know but I doubt.
2. Leaving aside the dispute of using LinqBridge, but if you use it in the production code, you cannot target the test to 3.5. Cheers, Kenneth On Mon, Jul 6, 2009 at 10:56 AM, Tim Barcz<[email protected]> wrote: > In other words you production code can target 2.0 but your tests do not need > to be bound by the same restriction. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
