Um, that was pretty rude. Based on the very small example you gave and the problems you described, his reply was spot-on: If you need an XElement as part of your unit test, you don't need to mock it. Just instantiate one and use it in your test.
Mocking is usually used to mock out dependent objects. Also, as noted in my follow-up reply, most (if not all) of XElement's members are non-virtual so they can't be used with Rhino.Mocks anyway. Please try and keep the conversations on a positive tone. :) --- Patrick Steele http://weblogs.asp.net/psteele On Tue, May 10, 2011 at 7:45 AM, Gary <[email protected]> wrote: > bill richards wrote: > >> There is no need to mock XElement at all > > That isn't your decision and you do not have all the facts to make that > decision. Kindly keep your opinions to yourself about how others do > their development. > > -- > Gary Please do NOT send me 'courtesy' replies off-list. > > -- > 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.
