Which version/build of IE7-8 Betas works on LH?

[maxtorix]

To make my question better and clear from that one from the title/subject:

Which version/build of IE7-IE8 Betas works best on which one Longhorn build?

I believe that many of you have test this, and I will be very grateful to post your opinions from results here.
,thanks in advance

[Boris]

I'm not even sure they'll install considering the installers check your Windows build number for compatibility before you can even start the installation.

[rafaelgs]

Probably you can extract the installation files, but IE7 beta will break many parts of Longhorn;

[maxtorix]

I can install any of them, after patching kernel (to be as xp - knabe method) in any build, but I am interesting which one is better?

[z180]

No running Longhorn installation here.
You could replace individual "Trident" DLLs like mshtml.dll that would keep the 6.05 look.

[rafaelgs]

I can install any of them, after patching kernel (to be as xp - knabe method) in any build, but I am interesting which one is better?

IE7 beta 1 or beta 2

[urban92]

All IE7 or IE8 builds will not work without patching mshtml.dll (Trident engine in IE7/8 requires new shlwapi.dll). You don't need patch kernel, but this is the simplest method to install updates from XP SP2/3.

IE7 Beta 2 (Build 5346) works perfectly. All longhorn features work with IE7 (excluding download manager, but you can download files in IE with disabled WinFS after installing IE7). You can use IE6 look after copy iexplore.exe from IE6.05.



IE8 RC1 works well (RTM not working), but interface has some errors.



There is patched mshtml.dll from IE7 Beta 2 (copy files to system32 folder): https://dl.dropbox.com/u/9112440/techvo ... 7_4074.zip

[maxtorix]

4053 with IE 7 Beta 1


Beside IE7, DX 11 on LH


5048 with IE 7 rtm/final


5048 with IE8 rtm

Offtopic Comment

.NET Framework 4.5 - Project
How many of you guys know, I was banned with a reason for 1 weak (last week).
That was for destroying my own post for .NET Framework 4.5.

...editing out all his posts in the topic.

Maybe is better to say editing and destroying...
But only that's not what happened. Not at all.

I was using some script what supposed to be used for automatic download from file-sharing service which one will click auto on buttons EDIT / SUBMIT / OK and etc, read hidden characters and auto put in text boxes... and when I click apply to all, there ware BA, MDL and some other sites opened what have same destiny. That was happening in parallel time when I also made my post for NET Framework 4.5. (This is not an excuse. Just I wanted to explain what was happen. I accidentally edit, but editing is editing.)

Project overview: administrative installation, unblock msi file to allow direct installation (orca used), and disabled rollback action.
Status: Work only as in-place replacement of version 4.0 in XP, Server 2003, Longhorn all builds.

My project is still alive (here is a proof)

[urban92]

Why you tested IE7 on 4053, no 4074? All .NET Framework versions on 4074? Amazing project

[maxtorix]

Why you tested IE7 on 4053, no 4074? All .NET Framework versions on 4074? Amazing project

Because I want to know how works all beta version of IE7 (and maybe IE8) on every leaked longhorn build...

[Knabe91]

Well from my tests IE7 should work well on all version of Longhorn except for a few bugs on newer ones like builds 4039ish and later. IE8 only seems to work on later builds like 4066 and later.

[maxtorix]

Well from my tests IE7 should work well on all version of Longhorn except for a few bugs on newer ones like builds 4039ish and later. IE8 only seems to work on later builds like 4066 and later.

Which build of IE 7?