Running Multiple Versions Of IE On The Same Box
MOVED
This content has been moved to my new blog at
https://petelepage.com/blog/2009/04/running-multiple-versions-of-ie-on-the-same-box/
Thanks,
PEte
Comments
Anonymous
April 27, 2009
The comment has been removedAnonymous
April 27, 2009
Are you talking about SuperPreview ?Anonymous
April 27, 2009
Do you know when the latest vhds will be available? The April 30 expiration is around the corner. Thank you.Anonymous
April 27, 2009
VPC images do not run on Vista Home Premium, which is by far the most installed version of Vista. If there's something which doesn't help us web developers here, then it's Microsoft itself.Anonymous
April 28, 2009
Strange timing for your post. The IE test VPN images expire in a couple of days, and I haven't seen anything about new images with new expiration dates. Is Microsoft going to release new images?Anonymous
April 28, 2009
There are applications out there that will put IE4/5/6/7/8 on the same machine and let you switch betweenAnonymous
April 28, 2009
The comment has been removedAnonymous
April 28, 2009
Re: Edward Martin's post about VPC image not running under Vista Home Premium. Virtual PC and VPC images do run under Vista Home Premium. It's not "officially supported", and you get a warning message when you install it, but you can safely ignore the warning.Anonymous
April 28, 2009
How about a link to those VPCs then?Anonymous
April 29, 2009
The comment has been removedAnonymous
April 29, 2009
What about IETester? (http://www.my-debugbar.com/wiki/IETester/HomePage)Anonymous
April 30, 2009
The VHDs are expired! Where are the new ones?Anonymous
April 30, 2009
Application virtualzation have a look at the following http://geekswithblogs.net/kazimmehdi/archive/2009/04 /29/running-internet-explorer-7---8-side-by-side-again.aspxAnonymous
May 01, 2009
My IE6 VPC image expired last night. When will a new image be posted? Thanks.Anonymous
May 06, 2009
Just wanted to get a post out to let people know that we’ve updated the IE VPC Test images. These imagesAnonymous
May 06, 2009
IETester will still have the same problems as other multiple IE solutions - as you aren't getting a true test environment (beyond CSS testing).Anonymous
May 06, 2009
The comment has been removedAnonymous
May 06, 2009
@Sam: IETester is using the exact rendering engin and javascript engine of the ie engine it is instanciating for each tab. What do you mean exactly when you say "IETester will still have the same problems as other multiple IE solutions". Can you be precise please ?Anonymous
May 06, 2009
"VPC images do not run on Vista Home Premium" possibly, but developers will be running vista business, so that's ok :PAnonymous
May 06, 2009
The comment has been removedAnonymous
May 06, 2009
The comment has been removedAnonymous
May 07, 2009
as asked above, what about Xenocode? http://www.xenocode.com/Browsers/Anonymous
May 08, 2009
The comment has been removedAnonymous
May 11, 2009
The comment has been removedAnonymous
May 12, 2009
The inability to run multiple versions of IE does not just hurt when testing websites. Upgrading IE is a major issue for many corporations because there is a very real risk of breaking existing web applications. For the same reason, this may hold organizations back from using new webapplications that run well only on the more standards compliant versions of IE (like 7 and 8). All these problems would be gone if IE was architected such that IE instances would be stand alone and isolated from one another. Firefox can, why can't IE? What is the benefit for the customer to integrate an application with the OS to the extent that you cannot upgrade it without the risk of breaking something?Anonymous
May 14, 2009
The comment has been removedAnonymous
May 26, 2009
The problem is chaining a relatively trivial app that needs to be widely deployed, to a lumpy anchor like an OS. Ideally, it should be possible to install and use any version of IE on any version of Windows, and by eating that SxS dogfood, have it co-exist with different versions of itself. Now I know you'll say IE is hardly a "trivial app" - but it is hugely edge-facing, and IMO that means it should be somewhat detached from the OS's innards. Think of how a leaf can be pulled off a tree without ripping it open; that's how I'd prefer to see edge-facing software that's exposed to exploits, so I can quickly amputate it if need be. Jake Munson refers to "stagnant IE6" - heh, imagine if all those years weren't stagnating in IE6, you'd prolly have another 2 or 3 versions of OS-bound browsers to test :-)