Hey mate, Nice work with the blog posts at the moment. I was just wondering if we should try and formulate a new solution for all of the samples. I know the source repository has MbUnit.Demo, could be good to go over this - update the sections which need it and blog/write/wiki the various sections as documentation. Instead of it just being code no-one? looks at. We could then release it as a separate zip file with the downloads.
I would be happy to work with you on this if you want. Could be good to release it before/with 2.4.1 as a complete release/package/final version before we move to 3.0. Bring up another important topic. Documentation. I'm not sure on the best way to document the framework, I was thinking Sandcastle to produce documentation on MbUnit.Framework and MbUnit.Core but I'm not sure how much has been documented, from the looks of it a lot, then placing that on the website / as a chm download. It looks good, plus is easy to manage I think (can be automated). This together with the samples write-up could be good and provide users with enough to get started/get the best out of the framework. With regard to version 3.0, how are we going to deal with documentation - maybe Sandcastle or something automated from the start would be good? What do you guys think? Ben On 27/05/07, Vadim <[EMAIL PROTECTED]> wrote: > > I'm sure that most people know that you can use arrays with RowTest > attribute. In case you don't know, read this: > > http://vkreynin.wordpress.com/2007/05/26/mbunit-arrays-with-rowtest/ > > Vadim > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MbUnit.User" 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/MbUnitUser?hl=en -~----------~----~----~----~------~----~------~--~---
