Hi There.
Firstly, apologies if i posted this in the wrong section

Im not a programmer but am really hoping some gurus can help me.

our enterprise system we use is to manage real estate called - MRI
we are currently on version 3 which runs on the web (ASP/.net2.0)
this version only supports up to IE7 clients

we would like to roll out windows 7 for our client pcs in our company, but have an issue:
As you know, Windows 7 comes with IE8 ,
the software version we are on currently ( MRI version 3) does not support IE 8.

The Vendor states that they do have a hotfix for IE 8 compatilbilty , but the hotfix can only be applied from MRI Version 4 onwards.

Upgrading our enterprise system to version 4 is not an option...(too many customisations,etc)

i have looked at the vendors so called "hotfix" and the only thing they have done is to rewrite a DLL file (mripageutil.dll) which would overwrite the old one.



this is what i have done in a test environment:
1) remove all old occurrences including the interop assemblies for the old DLL(mipageutil.dll)- version 1

regsvr32 MRIPageUtil.dll /u /s
gacutil /u mripageutil.interop
Regasm /u mripageutil.interop.dll

2) stop IIS

3) physically copy the new dll (mripageutil.dll) and overwrite the old dll (mripageutil.dll)

4)register the new dll including interop assemblies (mripageutil.dll) - version 4
regsvr32 MRIPageUtil.dll /s
gacutil /i mripageutil.interop.dll
Regasm mripageutil.interop.dll

5) start IIS

it does not work! - i get this error on the website -------------->>>>>

In Catch ex As Exception =Retrieving the COM class factory for component with CLSID {91190C7D-6890-4BA8-B39D-A8ECB4264B95} failed due to the following error: 800a801d.



looking in the registry , the CLSID {91190C7D-6890-4BA8-B39D-A8ECB4264B95} is referencing the old dll

i used tlbimp to create an interop.dll based on the new dll from the hotfix, but then get other errors stating interop is not valid file,etc

Can replacing a dll work or do i need source code,etc?
could this maybe be because the old dll was probably built on older .NET2.0 and the newer dll was built in maybe .NET 3.5? the appication is configured for .NET 2.0 as stated above