Improvement I would like to see...

[basara]

One thing I wish that would happen for the HTML help for VB ( as well as the
rest of VS) is better limiting of the standard help subsets. It's a pain
in the butt when searching thru the so-called "VB Documentation" and finding
stuff for the Microsoft Java SDK! For example, when you look for MouseUp
in the index, the first thing found In the VB Documentation set is the MouseUp
function from the MS Java SDK. What is that doing in the VB Docs to begin
with?

[Cristof Falk]

In article <3947fa43$1@news.devx.com>, ky.markw@angelfire.com says...
>
> One thing I wish that would happen for the HTML help for VB ( as well as the
> rest of VS) is better limiting of the standard help subsets. It's a pain
> in the butt when searching thru the so-called "VB Documentation" and finding
> stuff for the Microsoft Java SDK! For example, when you look for MouseUp
> in the index, the first thing found In the VB Documentation set is the MouseUp
> function from the MS Java SDK. What is that doing in the VB Docs to begin
> with?
>
Actually, I like that (as I develop in multiple languages). But what I
dislike about VS6 is that the keywords across products are not well
integrated, so I have lots of the same or similar topics to look over.
Hope they clean this up (and I guess the web forms will be a way in that
direction, as all the VS7 will support this for form-ing). -cf