.NET application installation disturbs excel add-ins

[mthakershi]

Hi,

This looks like a combination of .NET and Office version issue. Here is my problem.

I have a .Net application using office components such as word, excel, and access. I also have my setup prepared in .NET which is not at all hi-fi. It detects the following Interop and COM assemblies related to office on the development computer (WIN 2000 Server with Office 2000 SR3).

EXCEL9.OLB
MSO9.dll
MSWORD9.OLB
Interop.Access.dll 9.0.0.0
Interop.Excel.dll 1.3.0.0
Interop.Office.dll 2.1.0.0
Interop.Word.dll 8.1.0.0
Office.dll 7.0.3300.0

All these dependencies go in the application folder on the deployment machine.

I have never installed any of the external Primary Interop Assemblies ever on my development computer. It just detected these dependencies itself.

As far as deployment goes, it could be on a machine with Office 2000/2003/XP on WIN 2000/XP. I can assume that the target machine has .Net framework 1.1 and office installed before the application setup takes place.

Problem:
On one of the deployment machines with WIN XP (SP2) and Office 2003 Basic Edition after I run my setup, MS Excel knocks off all the selected add-ins automatically and thus any VBA applications users might be using become useless. However, if I repair the office setup from Add/Remove programs both applications (office and my application) work as intended.

Please help me figure out this issue.

Thanks,
Malay Thakershi
mthakershi@yahoo.co.in

 

[mthakershi]

Hi,

I just fixed this. The problem was with FM20.dll (Microsoft Forms Library 2.0) that was being copied and registered on target machines via my setup. The version I was copying was 2.x while most machines had Office 2002/XP/2003 having newer version of this DLL. As I have an assumption that Office should be installed before my application, I don't supply this DLL anymore with my kit.

Malay