Vista WDK documentation

Yup. Same here. DE takes forever to launch. Once it is up and running
I’ll use its index for quickly getting function prototypes to paste into
code, but I hardly ever bother with the search engine.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Thursday, May 31, 2007 1:07 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Vista WDK documentation

Hagen Patzke wrote:

  • A local search/browse is usually faster than using the online MSDN,

For me, this is provably untrue. I can do a Google search, pick the
first (MSDN) link, and have that page displayed in Firefox before
Document Explorer even launches.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

> ----------

From: xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com] on behalf of Bob Kjelgaard[SMTP:xxxxx@microsoft.com]
Reply To: Windows System Software Devs Interest List
Sent: Thursday, May 31, 2007 6:12 PM
To: Windows System Software Devs Interest List
Subject: RE: Re:[ntdev] Re:Vista WDK documentation

Oh, I’d rather it was much bigger and easier to find (and I spent quite some time not being able to find it even after I knew it was there). I just make do with what I’ve got, and this is it, and that’s how it works. Eventually I adapt my methods to whatever my tool set is, and that’s where I am with doc explorer these days.

It is hard to adapt to something like this :-/ I use this button but always have to find it again. It is counter-intuitive.

IMO, good tools, say programmer’s editors- are elusive- everyone knows what the perfect one looks like, and (generally) no two of these perfect examples are exactly alike. So I use the closest and most convenient and learn to live with it.

The problem is MS had a good tool (HTML Help) and replaced it with bad one.


I guess this “learn to live with it” attitude is what MS expects from customers and one of reasons which makes MS so hatred company. Customers, and I hope we’re the customers, should have a choice and don’t need to use what somebody who’s probably living in different reality where wheels and square "invented’.

(nothing against you, Bob, it is general comment)

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]

I agree with most people. I prefer the old help system every day.

But I’m not sure this is the right place to talk about this. This is not a WDK specific issue. It is generic to the whole MSDN library. So I don’t think the WDK team had much choice.

xxxxx@rahul.net wrote:

I agree with most people. I prefer the old help system every day.

But I’m not sure this is the right place to talk about this. This is not a WDK specific issue. It is generic to the whole MSDN library. So I don’t think the WDK team had much choice.

I disagree. I suspect (without any specific knowledge) that the help
information is all written generically, and is then post-processed to
produce an end-product. Run tool 1, and you get a .chm. Run tool 2,
and you get a Document Explorer collection. Run tool 3, and you get an
.rtf ready to turn into a physical book. Run tool 4, and you get a
.aspx suitable for MSDN online. I would be very surprised if the
decision on which form to ship with the WDK was made outside of the DDK
group.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

Tim,

Regardless of the tool, the WDK doc team did not have a choice.
Document Explorer 8 has been set as a corporate standard. Part of the
reason, I started this thread, is because Doc Explorer is so bad, but
without public comments to that effect, there will be no chance of a change
(note I have to wonder if there will be a change even with the comments).

I’ve captured some of my complaints about the tool in my latest blog
posting.


Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

“Tim Roberts” wrote in message news:xxxxx@ntdev…
> xxxxx@rahul.net wrote:
>> I agree with most people. I prefer the old help system every day.
>>
>> But I’m not sure this is the right place to talk about this. This is not
>> a WDK specific issue. It is generic to the whole MSDN library. So I
>> don’t think the WDK team had much choice.
>>
>
> I disagree. I suspect (without any specific knowledge) that the help
> information is all written generically, and is then post-processed to
> produce an end-product. Run tool 1, and you get a .chm. Run tool 2,
> and you get a Document Explorer collection. Run tool 3, and you get an
> .rtf ready to turn into a physical book. Run tool 4, and you get a
> .aspx suitable for MSDN online. I would be very surprised if the
> decision on which form to ship with the WDK was made outside of the DDK
> group.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>

> ----------

From: xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com] on behalf of xxxxx@rahul.net[SMTP:xxxxx@rahul.net]
Reply To: Windows System Software Devs Interest List
Sent: Thursday, May 31, 2007 8:38 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Vista WDK documentation

But I’m not sure this is the right place to talk about this. This is not a WDK specific issue. It is generic to the whole MSDN library. So I don’t think the WDK team had much choice.

WDK team is in better positions than we are and at least can inform responsible people/team about general dissatisfaction. And why should we care about MSDN? We’re using WDK docs and it is right place to discuss it here.

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]

Sorry, I didn’t mean we *can’t* talk about this here, or that we can’t express our dissatisfaction. I hate the newer system as much as you do.

What I meant is Don’s last comment. It is more than likely a corporate decision. And even if the WDK manager is listening here, I doubt he could do much. So may be this should be raised as well in other forums/newsgroups. If there is a massive complain, including Visual Studio and Office users, then it might have more chances to change the corporate decision.

Michal, just a couple of additional thoughts (this is a bit OT).

I don’t think we have the “learn to live with it” philosophy as a company (or nobody would even be bothering with a survey), although there are may be individual cases where that’s happened.

That’s just my personal philosophy for dealing with things I don’t feel I have much control over, and which aren’t totally killing my ability to get the job done.

I’m probably not any more enthralled by this change than you were. I’m also fine with the complaints a flyin’- I’m just not inclined to do it myself.

Look, I’m responsible for a WDK tool (WdfVerifier). I definitely want the feedback- I solicit it (almost to the point of pestering) from the KMDF and UMDF teams each time I add features to it. As a result, the next version (which has been my main distraction the last couple of weeks) does nice things like automatically launch debuggers for UMDF drivers and disable and re-enable device stacks so verification-related changes that require this can take effect [yes those are *options* for usage]. I’m hoping eventually to go after things like making setup of debugger extensions or problems like Gadi’s with the autologging for a boot driver easier.

In that respect (appreciating feedback), I don’t think I’m atypical for a “softie” (where I’m probably atypical is in not being interested in ranting on some of the other issues I alluded to- I’ve endured many lengthy discussions on the best name for a variable, and I’m a very laissez-faire code reviewer as a result of them).

But I can’t speak to this product or why it changed as I have no involvement with it.

Seriously, I think it was a good idea of Don’s to start this thread, and I do hope the appropriate people consider the resulting input.

I certainly consider you (the developer community) my customers, and I try to do right by my customers just as I did when I owned my own business. I may be deluded, but I believe there’s somebody here somewhere with similar motivations trying to figure out what to do about these issues.

Unfortunately the online MDSN is more up-to-date than the WDK Help.

For example, the kernel-mode IP Helper API “SetIpForwardEntry2” (Note the
“2”) is not described in the WDK Help, but can be found on the MSDN Online.

Google finds the MSDN page on this API much faster than the WDK Online Help
Search facility.

Thomas F. Divine

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-288538-
xxxxx@lists.osr.com] On Behalf Of Gianluca Varenni
Sent: Thursday, May 31, 2007 11:42 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Vista WDK documentation

----- Original Message -----
From: “Don Burn”
> Newsgroups: ntdev
> To: “Windows System Software Devs Interest List”
> Sent: Wednesday, May 30, 2007 9:58 AM
> Subject: [ntdev] Vista WDK documentation
>
>
> >I was at the WinHEC WDK feedback sessions a couple of weeks ago, and
> one of
> >the things Microsoft was asking was about the documentation. Since
> there
> >were only a few people in the room, I figured I would see if the
> discussion
> >could be continued here.
> >
> > Some of the questions from WinHEC:
> >
> > 1. Do people use the online MSDN documentation for the WDK or the
> > documentation that comes with the WDK?
>
> Mostly the local WDK documentation. And actually the 3790.1830DDK one.
> As
> many others already pointed out, the WDK6000 documentation is 1) slow,
> 2)
> not easily browsable (I simply cannot get used to it, maybe i’m dumb).
>
> >
> > 2. Are people aware of the WIKI feature of the MSDN documentation?
> Do
> > you use it?
>
> Yes, and no.
>
> >
> > 3. What do people think of “document explorer” the tool that
> presents the
> > WDK documentation? Is it better or worse than previous versions? Do
> you
> > use the search from it?
>
> As i said in 1., it’s slow and less immediate to use that the previous
> CHM.
> I don’t use the search feature much (I usually know exactly where to
> find
> the info I’m looking for), but it looks like even the search feature is
> worse in the document explorer.
>
> >
> > 4. Would you like to see samples in the documentation? Should they
> be
> > like:
> >
> > a. Visual studio’s complete programs:
> > http://msdn2.microsoft.com/en-us/library/f1byzb6d(VS.80).aspx
> > b. Platform SDK’s samples functions:
> > http://msdn2.microsoft.com/en-us/library/aa365160.aspx
> > c. Platform SDK’s code fragments:
> > http://msdn2.microsoft.com/en-us/library/aa363874.aspx
> >
>
> Personally I don’t care about samples in the documentation. I normally
> go
> directly to the samples folder of the DDK/WDK to find what i need.
> Maybe it
> would be useful to have more links to the various samples in the
> functions
> documentation. But code snippets in the documentation would definitely
> be
> useful.
>
>
> Just my two cents
> GV
>
>
> >
> > I’m sure there are enough Microsoft folks to relay the discussion
> back to
> > right people, and those of us who were at the sessions have the
> emails to
> > send stuff to encourage reading this.
> >
> >
> > –
> > Don Burn (MVP, Windows DDK)
> > Windows 2k/XP/2k3 Filesystem and Driver Consulting
> > Website: http://www.windrvr.com
> > Blog: http://msmvps.com/blogs/WinDrvr
> > Remove StopSpam to reply
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> > http://www.osronline.com/article.cfm?id=256
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> > http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer

Thomas,

This is actually one of the pieces of news from WinHEC. The WDK
documentation has been being bug fixed on MSDN, and shortly there will be
downloads available from the WHDC site to capture the bug fixes and other
improvements for the local copy. The plan is for every few months to
provide a update.


Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

“Thomas F. Divine” wrote in message
news:xxxxx@ntdev…
> Unfortunately the online MDSN is more up-to-date than the WDK Help.
>
> For example, the kernel-mode IP Helper API “SetIpForwardEntry2” (Note the
> “2”) is not described in the WDK Help, but can be found on the MSDN
> Online.
>
> Google finds the MSDN page on this API much faster than the WDK Online
> Help
> Search facility.
>
> Thomas F. Divine
>
>
>> -----Original Message-----
>> From: xxxxx@lists.osr.com [mailto:bounce-288538-
>> xxxxx@lists.osr.com] On Behalf Of Gianluca Varenni
>> Sent: Thursday, May 31, 2007 11:42 AM
>> To: Windows System Software Devs Interest List
>> Subject: Re: [ntdev] Vista WDK documentation
>>
>>
>> ----- Original Message -----
>> From: “Don Burn”
>> Newsgroups: ntdev
>> To: “Windows System Software Devs Interest List”
>> Sent: Wednesday, May 30, 2007 9:58 AM
>> Subject: [ntdev] Vista WDK documentation
>>
>>
>> >I was at the WinHEC WDK feedback sessions a couple of weeks ago, and
>> one of
>> >the things Microsoft was asking was about the documentation. Since
>> there
>> >were only a few people in the room, I figured I would see if the
>> discussion
>> >could be continued here.
>> >
>> > Some of the questions from WinHEC:
>> >
>> > 1. Do people use the online MSDN documentation for the WDK or the
>> > documentation that comes with the WDK?
>>
>> Mostly the local WDK documentation. And actually the 3790.1830DDK one.
>> As
>> many others already pointed out, the WDK6000 documentation is 1) slow,
>> 2)
>> not easily browsable (I simply cannot get used to it, maybe i’m dumb).
>>
>> >
>> > 2. Are people aware of the WIKI feature of the MSDN documentation?
>> Do
>> > you use it?
>>
>> Yes, and no.
>>
>> >
>> > 3. What do people think of “document explorer” the tool that
>> presents the
>> > WDK documentation? Is it better or worse than previous versions? Do
>> you
>> > use the search from it?
>>
>> As i said in 1., it’s slow and less immediate to use that the previous
>> CHM.
>> I don’t use the search feature much (I usually know exactly where to
>> find
>> the info I’m looking for), but it looks like even the search feature is
>> worse in the document explorer.
>>
>> >
>> > 4. Would you like to see samples in the documentation? Should they
>> be
>> > like:
>> >
>> > a. Visual studio’s complete programs:
>> > http://msdn2.microsoft.com/en-us/library/f1byzb6d(VS.80).aspx
>> > b. Platform SDK’s samples functions:
>> > http://msdn2.microsoft.com/en-us/library/aa365160.aspx
>> > c. Platform SDK’s code fragments:
>> > http://msdn2.microsoft.com/en-us/library/aa363874.aspx
>> >
>>
>> Personally I don’t care about samples in the documentation. I normally
>> go
>> directly to the samples folder of the DDK/WDK to find what i need.
>> Maybe it
>> would be useful to have more links to the various samples in the
>> functions
>> documentation. But code snippets in the documentation would definitely
>> be
>> useful.
>>
>>
>> Just my two cents
>> GV
>>
>>
>> >
>> > I’m sure there are enough Microsoft folks to relay the discussion
>> back to
>> > right people, and those of us who were at the sessions have the
>> emails to
>> > send stuff to encourage reading this.
>> >
>> >
>> > –
>> > Don Burn (MVP, Windows DDK)
>> > Windows 2k/XP/2k3 Filesystem and Driver Consulting
>> > Website: http://www.windrvr.com
>> > Blog: http://msmvps.com/blogs/WinDrvr
>> > Remove StopSpam to reply
>> >
>> >
>> > —
>> > Questions? First check the Kernel Driver FAQ at
>> > http://www.osronline.com/article.cfm?id=256
>> >
>> > To unsubscribe, visit the List Server section of OSR Online at
>> > http://www.osronline.com/page.cfm?name=ListServer
>>
>>
>> —
>> Questions? First check the Kernel Driver FAQ at
>> http://www.osronline.com/article.cfm?id=256
>>
>> To unsubscribe, visit the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer
>
>

*I* think this is the right place to discuss this :slight_smile:

Document explorer sucks ass. And I’m being most charitable with that comment. This will be obvious to ANYbody who spends 20 seconds trying to use it.

Look what you get under the various search choices (Language, Technology, Content Type). This doesn’t pass the giggle test.

We went from the lousy help system we had before in the DDK, to a torturously terrible help system in the WDK.

In terms of general WDK Documentaiton improvements and problems, I’ve talked to the WDK doc and PM teams until I’m hoarse about the problems. I’ve spent DAYs in meetings discussing this. Literally. They’re all nice folks, and I know they mean well, but EXCEPT FOR A FEW ISOLATED AREAS I don’t see much significant change. Oh, the stories I could tell…

Peter
OSR

> 1. Do people use the online MSDN documentation for the WDK or the
documentation that comes with the WDK?

50/50, prefer online MSDN when am on a fast network.
When on slow network, prefer Google :slight_smile:
Keep the 1830 .chm handy.

  1. Are people aware of the WIKI feature of the MSDN documentation? Do you use it?

Love the wiki - but would not use it for DDK/WDK docum.
We have the feedback email and these forums, this is enough IMHO.
Also, the MSDN wiki still has IMHO quite beta look and feel.

  1. What do people think of “document explorer”

Oh. next question, please…

  1. Would you like to see samples in the documentation? Should they be like: a. Visual studio’s complete programs:

Short code fragment(s) in the topic text.

Complete sample projects are very important - but, as we’ve seen,
they do not fit well into the MSDN help update schedule.

IMHO, mature samples for released OSes can be moved out of
the WDK and converted to community-supported projects, like
kernel examples on SF, or Coding For Fun:

http://blogs.msdn.com/coding4fun/archive/2006/10/31/912422.aspx

Regards,
–PA

This is good idea, Don.

  1. I use the DVD version of MSDN/WDK, mostly because I’m impatient and
    find he transitions kind of disorienting. The MSDN DVDs are also pretty
    much the only thing in MSDN that I use that I don’t have to download. I
    realize the last reason is pretty stupid, and it isn’t the major one,
    but it really pisses me off that basically everything else I use from
    MSDN I have to download. I don’t really care about most of it being
    free, as I don’t really pay for my MSDN personally, but the combination
    of having to pay for what is frequently free and not even getting on
    disc (at least in any sort of reasonable time frame) sucks. It makes me
    want to switch back to CD and get all possible languages just to make a
    totally meaningless statement to no one but myself.

  2. Had no idea. I would certainly check it out; it seems like it has
    the potential to be either a fabulous feature or an endless, useless
    stream. Just have to see how it turns out.

  3. Not a big fan. I much preferred the CHM version (truth be told, I
    liked the really old TechNet/NT4 version). I just find the CHM version
    more responsive, and I like being able to just move files around,
    possibly with FAR coming in to play, without having to change registry
    settings. Also, it’s nice to be able double click and start from the
    command line. Overall, dexplorer would fall in to the category of
    software that I have in mind when I get on my soapbox about reallocating
    trivial amounts of resources in order to improve the WinDbg
    documentation, not that the two really have much to do with each other.

I would have a very hard time understanding why anyone would use the
search. I don’t mean to get in to conspiracy theories, but the
combination of paying for what is otherwise free stuff that you have to
download anyway, combined with the worst possible search ever kind of
looks bad. I’m, of course, not serious, and I’m sure that is not it,
and even if it is, so what, but it sucks to such an unreasonable degree
for a new feature that my mind wanders sometimes while I wait.

  1. Absolutely. I’m partial to (b), but I also like (c). Pretty much
    anything as long as they documentation and code are integrated, don’t
    require clicking on anything other than perhaps one thing to expand it,
    and, for those that support multiple languages, default to C.

mm

>> xxxxx@acm.org 2007-05-30 12:58 >>>
I was at the WinHEC WDK feedback sessions a couple of weeks ago, and
one of
the things Microsoft was asking was about the documentation. Since
there
were only a few people in the room, I figured I would see if the
discussion
could be continued here.

Some of the questions from WinHEC:

  1. Do people use the online MSDN documentation for the WDK or the
    documentation that comes with the WDK?

  2. Are people aware of the WIKI feature of the MSDN documentation? Do
    you
    use it?

  3. What do people think of “document explorer” the tool that presents
    the
    WDK documentation? Is it better or worse than previous versions? Do
    you
    use the search from it?

  4. Would you like to see samples in the documentation? Should they
    be
    like:

a. Visual studio’s complete programs:
http://msdn2.microsoft.com/en-us/library/f1byzb6d(VS.80).aspx
b. Platform SDK’s samples functions:
http://msdn2.microsoft.com/en-us/library/aa365160.aspx
c. Platform SDK’s code fragments:
http://msdn2.microsoft.com/en-us/library/aa363874.aspx

I’m sure there are enough Microsoft folks to relay the discussion back
to
right people, and those of us who were at the sessions have the emails
to
send stuff to encourage reading this.


Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

and it’s not even close…

>> xxxxx@probo.com 2007-05-31 13:06 >>>
Hagen Patzke wrote:

  • A local search/browse is usually faster than using the online
    MSDN,

For me, this is provably untrue. I can do a Google search, pick the
first (MSDN) link, and have that page displayed in Firefox before
Document Explorer even launches.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

>[There is a “Sync with TOC” button in Document Explorer]

Great! Bob, thank you very much for the helpful hint! :slight_smile:

I actually did look for an option to sync the TOC to the section
displayed, but found nothing. Probably I am too menu-centric - expecting
all functions to be available via menu entry (and - if reasonable -
accelerator key, as proposed by the MS style guides), with only
shortcuts as additional optional symbols in the toolbar.


Did anybody actually try to invoke the Document Explorer online help?
Go ahead… try it! :slight_smile:

My suggestion to whoever programmed the MS Doc Explorer would be

  • to synchronize TOC with the displayed section by_default,
  • and let ppl. switch this behaviour off (via the option menu)
    – with an explanation for the manual sync button popping up when they
    switch it actually off.

Thanks,
-Hagen

I did a test this morning on looking up things with the last DDK, the WDK
and Google.

Last DDK was fastest assmuing it was running
If IE is running going to Google and then the subject was about 10 times
slower than using the DDK search
With the WDK running the search time for was 10 times slower than using
Google or roughly 100 times slower than the last DDK.

The two orders of magnitude slow down in searching is something I
complained about in the beta, and was told get a newer system. Turns out
the performance does not improve going from an old system with SCSI-2 with
1GB and dual PII 450MHz to SATA-2 with 3.25GB and a dual core high end
Athlon, I saw no speed increase in the search based on wall time.


Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply

“Roddy, Mark” wrote in message news:xxxxx@ntdev…
Yup. Same here. DE takes forever to launch. Once it is up and running
I’ll use its index for quickly getting function prototypes to paste into
code, but I hardly ever bother with the search engine.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Thursday, May 31, 2007 1:07 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Vista WDK documentation

Hagen Patzke wrote:
>
> - A local search/browse is usually faster than using the online MSDN,

For me, this is provably untrue. I can do a Google search, pick the
first (MSDN) link, and have that page displayed in Firefox before
Document Explorer even launches.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

Martin O’Brien wrote:

and it’s not even close…

>>> xxxxx@probo.com 2007-05-31 13:06 >>>
Hagen Patzke wrote:
> - A local search/browse is usually faster than using the online
MSDN,

For me, this is provably untrue. I can do a Google search, pick the
first (MSDN) link, and have that page displayed in Firefox before
Document Explorer even launches.

…which (in my humble option) is not “using the online MSDN”.

It is, however, a good example of how excellent Google search has
become. (And luckily they index the MSDN, too.)

My comparison was “MSDN online”, and there for search I use “MSDN
search” or “search.microsoft.com”.
Compared to these, the WDK local search is actually way faster/better,
at least on my system with my internet connection.

2c. for clarification. :slight_smile:
-H

I just want to make sure that you know how to shut off the default online searches that Doc Explorer does whenever you search the WDK docs.

Go to Tools->Options. In the left-hand pane, under “Help”, click “Online”. To the right, under “Search these providers”, unclick everything except “Local Help”.

After you do that, Doc Explorer will only search your local disk.

Yeah, but after doing that, you don’t get all the cool driver development help from VBCity.com :slight_smile:

(For those of you who don’t know, Richard is one of the premier WDK doc writers…)

Peter

>> 1. Do people use the online MSDN documentation for the WDK or the
documentation that comes with the WDK?

WDK docs. When forced to use MSDN, I use it via Google.

> 2. Are people aware of the WIKI feature of the MSDN documentation? Do
you use it?

No. I’m somewhat interested though.

> 3. What do people think of “document explorer” the tool that presents
the WDK documentation? Is it better or worse than previous versions? Do
you use the search from it?

I like the previous version much better. I use the search feature as a last
resort.

> 4. Would you like to see samples in the documentation? Should they be
like:

Sure. Copy/paste == love.