> Consider this thread as a poll to know what you would like to have in our > reference documentation. > We know that we have some obsolete info, some incomplete info and a lot of > info spanned in various blog posts. > > What you would like to have in our reference documentation ?
I think that a solution that contains projects to explain use cases would be a good starting point. Simple projects divided by argument and tests could be a way. I think also that the "bibliography" used by the team to project features, solve issues and apply a certain pattern could be useful, we do that in our project HSDK (http://hypersionsdk.codeplex.com), so users can walk along the road you've done and understand better why "something" is implemented in a way instead another. My 2 cents. -- You received this message because you are subscribed to the Google Groups "nhusers" 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/nhusers?hl=en.
