MSDN Documentation - Love it? Hate it?
-
Done - maybe this will result in MSDN search actually being fixed. Ha! Who am I kidding!
¡El diablo está en mis pantalones! ¡Mire, mire! Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! VCF Blog
Totally with you. MSDN was, is (and have little hope for the future), just not usable or digestibale at all...even by a veteran amateur like me... BUT, unless you are a board pensioner, or do not have a job, with loads of time to read a load of incoherent, not applicable, and seriously bordering on corporate marketing style bla bla (no content, just useless techno c..p), to realize that either they also have no idea what the document but do t because it is a requirement, or we are definately using the wrong system to find solutions to our engineering questions. Goolge, developemnt comunities and forums RULES ...thanks CodeProject, and thanks to the developers that share their experiences, tips, ideas and findings. :-O:cool: Zeeker
-
Cool it! This isn't a survey being done here in the forums. Microsoft is conducting a survery though, here[^]. Take it out on them!
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007I loved MSDN back in the Visual Studio 6.0 days. I didn't have an Internet Connection back then, but the organization, the overall quality of the information, and primarily, the quality of the sample code was often more than enough. Back then instead of silly snippets of code showing no more than the calling syntax, several really useful examples were provided. I often focused first on the example than on the explanation. One precious gem that sadly was removed in later renditons of MSDN was "Hardcore Visual Basic". I was a C++/Delphi programmer reluctantly forced to code in VB6. :wtf: It surely was fun unlocking "the power" and begin using lower level stuff such as pointers, memory allocation, threading, etc. One thing I'm certainly not proud of (in retrospective) is that parts of my VB code usually were totally indigestible for the rest of the team, which was the primary reason why I was forced to use Visual Basic in the first place. Shame on me... :~ Ger
An interesting form of object-oriented programming: You suggest a novel algorithm, and watch as the rest of your team objects! ;)