| To the guy that said "RTFM", what is the purpose of that? OF COURSE 99%
| of the answers are in the documentation... but.... the documentation is
| sometimes 1) hard to find the right info, 2) is not always
| understandable based on skill or talent of coding, 3) for some things
| it takes someone to explain it for it to click! That is WHAT THIS FORM
| IS FOR. And yes I often yell RTFM to my peers in our coding shop...
| BUT I always make sure they FIND IT and UNDERSTAND IT. What good if
| RTFM, if they do not improve over time? Just a thought.
if you have a "coding shop" and you have to "often" yell rtfm, you need to
rehire.
as for the help files, that's only one stop in the search for an answer.
canceling a form's closing event is BASIC functionality...and is WIDELY
covered not only in help but also in the sample applications installed with
visual studio .net and extensively prevalent on the web.
how hard is it to google:
"vb.net cancel form close"
wow, the first link shows how...and the second, and third, and...ad-nausium.
i DON'T often yell rtfm...but certainly DO when ABSOLUTELY warranted!!!
and btw, 99% of what NEW developers want is in the help files while 99% of
mid and senior-level developers quandries will NOT be found therein. imho, i
think this forum would better be served by addressing THOSE questions by
people who have figured out the answers...as most have been discovered and
solved through inference and experience - which is something manuals cannot
provide. this is not something that CAN improve with time. it is just the
nature of documentation...just a thought.
imo, it is a diservice to ask questions that obviously show a lack of effort
in finding answers that are easily found and readily available. you and i
simply have differing perspectives. i haven't railed you for yours...perhaps
you should revisit understanding mine.