I would like know... are the folks at MSDN professional programmers who thus know how to organize, explain and present MSDN library topics in useful easy
to find and understand format or are they just technical writers who do not
understand the real programming world and thus can't crank "who cares what"
detail. Why is MSDN so full of "Hello World" kind of samples and less of the
type real programmers really need to understand the topic. Ahhhhhh... I know
it... it's me after all.
Re: Just Curious ... Chris Hanscom - Microsoft MVP... explain and present MSDN library topics in useful ... > understand the real programming world and thus can't crank "who cares ... (microsoft.public.vb.general.discussion)
Re: Just Curious ... explain and present MSDN library topics in useful ... > understand the real programming world and thus can't crank "who cares ... > type real programmers really need to understand the topic. ... (microsoft.public.vb.general.discussion)
Re: DllMain vs. DllMain ... obey the MSDN page that says what the API itself is? ... contains instructions for VC++6 programmers or descriptions of the APIs ... work this morning and fail this afternoon because undocumented behaviour is ... (microsoft.public.win32.programmer.kernel)
Re: Asynchronous Programming Patterns and Techniques - No Concensus? ...Recommendations usually come with explanation. ... I would definitely agree that there are numerous examples in MSDN of recommended practices that don't do a good job of justifying those practices. ... If you must expose both the event-based pattern and IAsyncResult pattern on a single calss, use the EditorBrowsableAttribute set to Advanced to mark the IAsyncResult pattern implementation as an advanced feature... ... That line of thinking would support an argument that the IAsyncResult model is actually better, because it imposes a slightly higher barrier, which should hopefully reduce the number of unqualified programmers attempting to use it. ... (microsoft.public.dotnet.languages.csharp)
Re: Registry VB question ... >> -Harry Bates... > Sheesh......MSDN code...... no wonder VB programmers are considered ... (microsoft.public.vb.enterprise)
