Re: CreateProcess and Vista
- From: "Paul Baker [MVP, Windows - SDK]" <paulrichardbaker@xxxxxxxxxxxxxxxx>
- Date: Wed, 5 Sep 2007 17:32:31 -0400
Larry,
"Larry Smith" <no_spam@xxxxxxxxxxx> wrote in message
news:eSrMRs%237HHA.536@xxxxxxxxxxxxxxxxxxxxxxx
Documentation should not lag behind development, but it does. It always
does. Ever single software or hardware vendor I've ever needed
documentation from has this problem to some extent.
This is true but you make it sound as if everyone does it so we should
accept that it's normal and just live with it.
Yes, I do think that you should accept that documentation is out of date to
some extent. Anyone who has attempted to keep documentation up to date for
all but the simplest software knows that it is impossible. That is, unless
you hold up release for months or years contingent on the documentation
being perfect and reviewed in its entirety by developers. And I don't think
anyone has a legitimate reason for wanting that, do they? However, I do
agree that it should be as up to date as practical, and it may be that
Microsoft has not met your standards in that regard. In any event, I'm just
trying to discourage Microsoft bashing that I feel is unjustified, even if
it is not entirely mindless in this case ;)
It need not be however. No reasonable person would expect perfection but
MSFT in particular has the resources to ensure that documentation is
up-to-date and thorough.
Microsoft has a lot of resources, because they have a lot of products and
services and therefore they need a lot of resources. They have a lot of
resources, but not a lot of resources to spare. No business is going to
employ a lot of unecessary resources that are waiting to swoop on every
little detail of everything. They face the same challenges as everyone else,
so your singling them out ("MSFT in particular") is unfair.
[snip]
I've contacted MSFT on numerous occasions over the years but nothing is[snip]
usually done. Here's a .NET sample from last year:
https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=134349.
Microsoft can't fix anything if they don't know about it. That's how things
can go unresolved for years while people bash Microsoft over some issue in
random blogs and the like without actually telling Microsoft.
It is also true that Microsoft can't fix anything unless the right people
know about it. If *anyone* at Microsoft knows about it, as in this case,
they ought to redirect it to the right place. But in such a large company,
it is no suprise that things could go astray.
In this case, you appear to have submitted your feedback to the people
responsible for a Beta release of Visual Studio. They have a lot of things
to be working on, most of which are more important than your feedback. When
they do get around to it, they will have to pass it along to the people who
write the MSDN Library. They write the integration of the library into
Visual Studio, but they probably don't pay much attention to content itself
that they don't write. The chances are, if you had submitted it via the MSDN
Library web page, you would have gotten some action within a few days. In
fact, why don't you do that and see where it goes?
Anyway, it hasn't been that long, and the fact that it is entered in their
system means that they have acknowledged your feedback. I have the same
situation myself, as a developer - over 600 change requests logged and I can
guarantee you that about 400 people think I'm ignoring them. The truth is, I
am just one person.
Paul
.
- Follow-Ups:
- Re: CreateProcess and Vista
- From: Larry Smith
- Re: CreateProcess and Vista
- References:
- CreateProcess and Vista
- From: Aldo Marchioni
- Re: CreateProcess and Vista
- From: Paul Baker [MVP, Windows - SDK]
- Re: CreateProcess and Vista
- From: Paul Baker [MVP, Windows - SDK]
- Re: CreateProcess and Vista
- From: Larry Smith
- Re: CreateProcess and Vista
- From: Paul Baker [MVP, Windows - SDK]
- Re: CreateProcess and Vista
- From: Larry Smith
- CreateProcess and Vista
- Prev by Date: Mindriver and certificate enumeration (Vista)
- Next by Date: Re: CreateProcess and Vista
- Previous by thread: Re: CreateProcess and Vista
- Next by thread: Re: CreateProcess and Vista
- Index(es):
Relevant Pages
|