I think it's useful advice, and good to see an example of the Do() method.

I think it was perhaps a bit too detailed at times. I would almost go as far
as saying the sections below could be cut out to make it more readable:

"What is going on is that deep in the bowels of RhinoMocks
...
...
in this case it help (as I see it often pop up on the mailing list)."


I guess that ignores the point of the series "explain the inner workings",
but I must admit the first time through I just completely skipped over most
of that. The subject of this post is perhaps a bit basic to warrant looking
at the inner workings? maybe a more complicated/advanced topic would lend
itself better to needing an in-depth look at the inner workings?

2009/8/23 Tim Barcz <[email protected]>

> Any other feedback? positive or negative...just want to take something
> away...good post, bad post, keep trying?
>
>
> On Sat, Aug 22, 2009 at 7:03 AM, Tim Barcz <[email protected]> wrote:
>
>> I may, or just link to them...
>>
>> On 8/22/09, Iain Waddell <[email protected]> wrote:
>> >>
>> >> Just posted the first post (of hopefully many) about exploring
>> RhinoMocks.
>> >> Am interested in your feedback http://bit.ly/id9X6 (either here or in
>> the
>> >> comments section if others will benefit).
>> >>
>> >
>> > Very interesting. Are these articles also going to appear in the wiki?
>> >
>> > Iain
>> >
>> > >
>> >
>>
>> --
>> Sent from my mobile device
>>
>> Tim Barcz
>> ASPInsider
>> http://timbarcz.devlicio.us
>> http://www.twitter.com/timbarcz
>>
>
>
>
> --
> Tim Barcz
> ASPInsider
> http://timbarcz.devlicio.us
> http://www.twitter.com/timbarcz
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to