mayayana
Mon May 30 12:16:50 CDT 2005
I usually do it that way, too, except
without limiting it to Microsoft.com
because there are often good postings
on newsgroups, MVP sites, etc.
In any case, I would never go to MSDN
for something specific. Google is the only
thing that makes MSDN online usable. It's not
only hard to search MSDN, it's also very slow
and bloated. On my dialup it takes perhaps 20
seconds for a page to load. Given that it could
easily require10 pages to follow the link trail to
where I want to be, that's a completely unworkable
setup. I'm guessing that they've deliberately
spread it out so that people won't just download
the docs rather than buying the CD.
--
--
Steven Burn <somewhere@in-time.invalid> wrote in message
news:eQ9RLyRZFHA.2124@TK2MSFTNGP14.phx.gbl...
> My approach to it is to find and store key entry
> points and then work through the left-hand hierarchical listing.
I generally use the following query in a search engine (typically Google
(via Scroogle))
<language> <query> [site:microsoft.com]
For example;
VBScript shellexecute site:microsoft.com
This brings up the following at the top of the results;
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shellcc/pla
tform/shell/reference/objects/ishelldispatch2/shellexecute.asp
Or;
VBScript (connect to remote computer) site:microsoft.com
This brings up the following at the top of the results;
http://msdn.microsoft.com/library/en-us/wmisdk/wmi/connecting_to_wmi_on_a_re
mote_computer.asp&e=9707
Additionally suggest bookmarking the wierd bald guy.....
http://www.microsoft.com/technet/scriptcenter/resources/qanda/hsgarch.mspx
.. and while your at it;
www.devdex.com (or www.developersdex.com)
www.aspfaq.com (mainly for ASP but can be quite useful for VBScript aswell)
and last but not least;
Planet Source Code - ASP/VBScript
http://surl.co.uk/?1482
Original URL:
http://www.planet-source-code.com/vb/scripts/BrowseCategoryOrSearchResults.a
sp?grpCategories=-1&optSort=DateDescending&txtMaxNumberOfEntriesPerPage=10&b
lnNewestCode=TRUE&blnResetAllVariables=TRUE&lngWId=4
--
Regards
Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk
Keeping it FREE!
"Joe Earnest" <jearnest3-SPAM@earthlink.net> wrote in message
news:#w1#PfRZFHA.228@TK2MSFTNGP12.phx.gbl...
> Hi,
>
> "David F" <David-White@earthlink.net> wrote in message
> news:uk7b%236KZFHA.3488@tk2msftngp13.phx.gbl...
> >I was looking for the SHELLEXECUTE command and it is not mentioned in any
> >of
> > the books I have.
> > I have MS' "Windows 2000 Scripting Guide", O'Reilly's "VB.NET Language"
> > Pocket reference book and other books, one which is called "The ULTIMATE
> > VB.Net" (the emphasis on "ultimate" is mine...). None is mentioning
that
> > command. So who knows what else I am missing.
> >
> > Does anybody knows about a good, COMPLETE and well organized
> > (alphabetically
> > and categorized, etc. - which by definition excludes MSDN) reference
> > source
> > for both, VB and VBScript?
> >
> > Thanks,
> >
> > David
> >
>
> To put mayayana's response in a slightly different light --
>
> Since VBS can operate under a number of different hosts and is designed to
> call different COM objects to effect the substance of its operations, what
> you're asking for just doesn't exist.
>
> Scripting facilitates other operations. It is not intended to be an
> all-encompassing language. When used under different hosts, the objects,
> properties and methods of those hosts can be directly accessed. The
number
> of both OS and third-party COM objects constantly changes and is different
> (to some degree) in both availability and specific implementation across
> different OSs, as well as on differently configured host computers. The
> script hosts also change in detail on a fairly continuous basis.
>
> The standard, and probably best, approach, is to get the basic WSH CHM
file
> (for which Steve Burn has provided the link) for actual VBS operations and
> inherent objects. Then look up the information on the COM objects and
hosts
> separately.
>
> There are books and e-documents out there that "try" to encompass
different
> hosts or COM objects in different ways. A book on websites may include
> website-specific scripting, one on servers may incorporate server-specific
> scripting, etc. These types of references may consolidate some information
> in a specialized area.
>
> But things change. When you find COM references, they may likely be
written
> to explain access from another language -- VB, C++, JS, .Net, etc.
>
> Here's the MSDN reference to Shell.Execute. It's under the
IShellDispatch2
> object, since it's not available in the earlier versions of Shell --
>
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shellcc/pla
tform/shell/reference/objects/ishelldispatch2/shellexecute.asp
>
> MSDN IShellDispatch2 listing --
>
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shellcc/pla
tform/shell/reference/objects/ishelldispatch2/ishelldispatch2.asp
>
> MSDN "Shell Objects for Scripting and Visual Basic" listing --
>
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shellcc/pla
tform/shell/reference/objects/objects.asp
>
> You're right that MSDN is difficult to work through. It's generally a
waste
> of time to search it. It's best thought of as a "sticky-note-pile" work
in
> progress that contains both outdated and very current information
(sometimes
> never implemented) covering so many languages, hosts and objects that when
> you find something, its likely not on the host or in the language you
> require. Very useful when needed, however, and probably the best
> accumulation around. My approach to it is to find and store key entry
> points and then work through the left-hand hierarchical listing.
>
> Joe Earnest
>
>
>