Groups > microsoft.public.scripting.vbscript > #12486

IE automation solution

Path	csiph.com!weretis.net!feeder8.news.weretis.net!paganini.bofh.team!not-for-mail
From	"Newyana2" <Newyana2@invalid.nospam>
Newsgroups	microsoft.public.scripting.vbscript
Subject	IE automation solution
Date	Mon, 4 Sep 2023 13:57:32 -0400
Organization	To protect and to server
Lines	22
Message-ID	<ud55ro$163mb$1@paganini.bofh.team> (permalink)
Injection-Date	Mon, 4 Sep 2023 17:58:16 -0000 (UTC)
Injection-Info	paganini.bofh.team; logging-data="1248971"; posting-host="YqKngTRkOayeCX1S/e7lbw.user.paganini.bofh.team"; mail-complaints-to="usenet@bofh.team"; posting-account="9dIQLXBM7WM9KzA+yjdR4A";
Cancel-Lock	sha256:hQe2wMFtKrrzLM+tF3KS2EkLF/yc9cCXtiQRcmXoIa4=
X-MSMail-Priority	Normal
X-Priority	3
X-MimeOLE	Produced By Microsoft MimeOLE V6.00.2900.5512
X-Notice	Filtered by postfilter v. 0.9.3
X-Newsreader	Microsoft Outlook Express 6.00.2900.5512
Xref	csiph.com microsoft.public.scripting.vbscript:12486

Show key headers only | View raw

https://www.jsware.net/jsware/compfiles.php5#jsie

  No one responded to my question about getting hold
of InternetExplorer.Application on later Windows versions.
It's all gone, but the functionality is still built in and
HTAs still work.

  Personally I write a lot of HTAs but I also use IE as
a GUI for scripts. The above is a solution. It's a simple, tiny
wrapper ActiveX EXE that will work on virtually any Windows
machine with no requirements other than COM registration.
Source code included. It basically just wraps IE, as closely
as possible, so that one need only substitute
Set IE = CreateObject("InternetExplorer.Application")
with
Set IE = CreateObject("jsIE.Browser")

  There are minor differences, but the basics are there,
including script access to the DOM for whatever IE
core is on your system.

Back to microsoft.public.scripting.vbscript | Previous | Next | Find similar

Thread

IE automation solution "Newyana2" <Newyana2@invalid.nospam> - 2023-09-04 13:57 -0400

csiph-web