I think that bibliography like in our HSDK project (http:// hyperionsdk.codeplex.com) could be useful to understand why a problem is solved in a certain way.
Also a solution with multiple projects and tests (to explain use cases) could be very useful. Every "How To" that you propose could be related to a sample project in this "all in one solution" organized using "a lot" of solution folders :), to divide arguments. My 2 cents. -- Matteo Migliore Blog http://blogs.ugidotnet.org/matteomigliore Twitter http://twitter.com/matteomigliore CodePlex http://hyperionsdk.codeplex.com On Oct 25, 2:35 pm, Fabio Maulo <[email protected]> wrote: > 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 ? > > more images ? > step by step example about some general mapping task ? > specific "How to" ? about what ? > more details about extensions points ? which one ? > .... > .... > .... > > Please collaborate with some ideas and will try to find a solution. > We will use this thread to find better ideas and apply it. > > Thanks. > -- > Fabio Maulo > > P.S. try to avoid to transform this thread in personal discussion, each one > has an opinion and opinions, in this case ( ;-) ), are welcome. -- 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.
