Read MSDN !
-
Here is a quote from a reply (someone post a question about an FTP client extended error into an article about... default mail client). I don't feel stressed when people asks me questions - I do this often myself - but this guy obviously didn't perform a basic MSDN search. And I dislike this... Suggestion: search, then search, then search again. Meanwhile, trace and debug. Is nasty, but definitely worth it. * * * "[...]You may also want to do your own search using the preferred search engine, as well as to sign-up to wininet-related newsgroups on Microsoft (or anything else) and look for similar problems and solutions or ideas. The power of MSDN is often misused and underrealized. Search extensively, debug better (if breakpoints introduces timeouts, use a verbose logfile to trace everything interesting and read it to understand what happens). Although it may look primitive and require a lot of typing, write some short macros, printf-like trace __cdecl functions with variable arguments - it definitely pays the price. Not only you'll be able to get a clear picture of error point(s) and cause, but also you can reuse them in further projects. [...]"
-
Here is a quote from a reply (someone post a question about an FTP client extended error into an article about... default mail client). I don't feel stressed when people asks me questions - I do this often myself - but this guy obviously didn't perform a basic MSDN search. And I dislike this... Suggestion: search, then search, then search again. Meanwhile, trace and debug. Is nasty, but definitely worth it. * * * "[...]You may also want to do your own search using the preferred search engine, as well as to sign-up to wininet-related newsgroups on Microsoft (or anything else) and look for similar problems and solutions or ideas. The power of MSDN is often misused and underrealized. Search extensively, debug better (if breakpoints introduces timeouts, use a verbose logfile to trace everything interesting and read it to understand what happens). Although it may look primitive and require a lot of typing, write some short macros, printf-like trace __cdecl functions with variable arguments - it definitely pays the price. Not only you'll be able to get a clear picture of error point(s) and cause, but also you can reuse them in further projects. [...]"
Sardaukar wrote: Suggestion: search, then search, then search again. Meanwhile, trace and debug. Is nasty, but definitely worth it. The search I like, unsure about the tracing bit. :-) But I have found after practice at searching you begin to get an ability to find stuff so much faster. One of my gripes is the number of times the same Qu is asked on the forums here. Regardz Colin J Davies
*** WARNING *
This could be addictive
**The minion's version of "Catch :bob: "It's a real shame that people as stupid as you can work out how to use a computer. said by Christian Graus in the Soapbox