Re: New help system


"Eric Grange" <egrangeNO@xxxxxxxxxxxxxxx> wrote in message
news:44f6ff49$1@xxxxxxxxxxxxxxxxxxxxxxxxx
these are often too simplistic or limited to really help that much

There is a pitfall to avoid however, which is to end up with too-complex
samples: a pitfall that most of the MSDN failed to avoid (many samples are
just so large you have to hunt through a lot of setup or UI code to get to
the useful bit)...
Another thing to avoid (that I find aggravating in most MSDN samples) is
that you often can't figure out what the sample is doing without having to
run it... Listing the sample code *and* the expected result is so much
more helpful.


Another problem with MSDN (and in a perverted way an advantage) is that for
searching the right article its ussually easier to use google.



.

Relevant Pages

  • Re: New help system
    ... There is a pitfall to avoid however, which is to end up with too-complex samples: a pitfall that most of the MSDN failed to avoid... ... Listing the sample code *and* the expected result is so much more helpful. ...
    (borland.public.delphi.non-technical)
  • avoid nested function
    ... I read on msdn that many blocks can slows page, ... processed like nested functions. ... Which of you have some tips to avoid using them? ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: How to Make Plugins
    ... and MSDN. ... You should avoid using MFC. ... ATL is one good way to do it. ...
    (microsoft.public.vc.mfc)