_IECreatePseudoEmbedded - Should I Use

[redrider81]

I've been using the amazing _IE.UDF for a few months, and have gone through 3 overhauls of a web server monitoring script that I created.  As I continue to battle a few recurring and frustrating problems, I constantly see reference to the "Embedded" options.  I would like to understand why the embedding seems to be so popular, but there really aren't any explanations that I can find about why you would use it over automating a normal IE window. There does seem to be some fundamental differences from _IECreate in the extra IE processes that normally get generated, and PID and window "handling" difficulties that follow (which is one of my challenges).  Also it looks like it might be a path to overcome the orphaned IE processes that my script leaves behind (maybe 1 out of 100 times it runs). 

Does the _IECreateEmbedded() or _IECreatePseudoEmbedded() offer significant advantages for advanced automation when compared to IECreate()?  If so, can anyone itemize the big ones?

Thanks in advance,

Jerry

 

 

[JLogan3o13]

It all depends on what you would like to do (which, without seeing your "few recurring and frustrating problems", is difficult to ascertain). I personally use _IECreateEmbedded for a couple of scripts where I want the user to stay where I want them, or provide them with quick-button access to specific sites/portals. See the "Deal-A-Day Sites" link in my signature for one example of what you can use it for.

 

As I said, though, without knowing more about the problems you're running into, it is difficult to suggest what will or will not work for you.

Edited August 22, 2014 by JLogan3o13

[redrider81]

Thanks for the response. I can see how controlling the window position would be easier. That makes sense. 

My biggest problem is the orphaned IE processes that get left behind due to unknown factors.  I can run 100 times manually and get no orphaned processes. But, when it's triggered by a system service, 1000 times over a few days, there will be dozen IE processes. 

My second biggest problem was getting a reliable handle to the IE Processes that get spawned so that I can reliably close them (trying to solve the former).  However, the multi-process design of IE makes this virtually impossible (I suppose intentionally to fight malware). Perhaps the PID's and windows work differently when using the embedded options?

[MikahS]

Hmm, post script?

[DaleHohm]

Use embedded when you want to wrap a browser instance inside your own UI and controls.  Otherwise, much simpler to simply use the full browser.

Regarding orphaned processes... make sure that _IEQuit() is called before script exit - normal or abnormal.

Dale

[redrider81]

Thanks for the responses.  I would very much like to post the script, but I'm not at liberty to because it's considered Intellectual Property where I work. I've sent messages to some of the _IE Guru's on this forum regarding professional consulting, as I think that's my only acceptable avenue for getting hands-on assistance.  No responses yet but I'm keeping my fingers crossed. 

Regards,
Jerry

[MikahS]

no problem redrider81, just seeing if we could have a look