'Class not registered' When application is installed and run on another workstation.

[Hughsie]

Hi

I have created an installation package for my app and I have installed
the application onto another machine together with the framework and
the correct MDAC version.

The problem is when I access something in the application that uses
one of the required dlls.

All the dlls have been included with the application in the same
folder as the exe when it was installed. With .net I thought this was
enough.

This problem occurs with two specific dlls:-

I am using a COM control called CTDays (a calendar control). Now, in
my application folder I have AxInterop.CTDAYSLib.dll and
Interop.CTDAYSLib.dll which I believe are the wrappers to enable the
object to be accessed from dot net.

The others are the dlls to enable my application to create Word
documents.

I can't register these components with regsvr32 as they are dot net
assemblies so I tried regasm. They register OK but still cause the
error when accessed in the application.

In the package project I also set them to be registered but the
problem was sill the same.

Any help would be MUCH appreciated as I have been working on this for
over a year and it is to be installed this week.

Apologies for the long post.

Hughsie

 

[Chris Dunaway]

I am using a COM control called CTDays (a calendar control). Now, in
my application folder I have AxInterop.CTDAYSLib.dll and
Interop.CTDAYSLib.dll which I believe are the wrappers to enable the
object to be accessed from dot net.

Is the CTDAYSLib.dll file present and registered on the workstation? All
COM .dll's must still be registered.


Can you show the line of code that has the problem?

 

[Hughsie]

On 12 Apr 2004 07:44:22 -0700, Hughsie wrote:

Is the CTDAYSLib.dll file present and registered on the workstation? All
COM .dll's must still be registered.


Can you show the line of code that has the problem?

Thanks for the response. The CTDays problem is fixed now. I didn't
realise the actual COM dll had to be installed as well as the
wrappers. I thought the wrappers were instead of the original.

The problem with my Word stuff remains though.

I am creating Word docs from my application and the following
dependancies show (which I believe are related to Word):-

Interop.Office.dll
Interop.VBIDE.dll
Interop.Word.dll
MSO9.dll
MSWORD9.OLB

All of the above are in the application directory but still no Word
access.

Again, any help would be much appreciated.

Many Thanks

Hughsie

 

[David Guyer [MS]]

This might sound silly, but is Word already installed on the target
computer? You don't want to deploy MSO9.dll and MSWORD9.OLB, since they are
not standalone files.

You probably want to create a Launch Condition in your setup project that
will check to see if office/word are already installed, since your app
requires that they already be there.