There is one bug to do with mocking generic methods that can be easily fixed by updating castle to a newer version. A while after doing this I noticed on GitHub that at least a few other people have done the same. For my own purposes I've not bothered fixing up the unit tests and although if I get time sometime I'll do that it'd be nice if someone familiar with the source code and/or castle dynamic proxy would get an "official" 3.7 version out.
On 14 March 2011 14:14, haifisch <[email protected]> wrote: > In other words. The product is major and stable - there was no need to > release an update ;-) > > On 14 Mrz., 14:38, Tilman <[email protected]> wrote: >> Is Rhino Mocks dead? It seems there hasn't been an update for well >> over a year. > > -- > 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. > > -- 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.
