Dcom & Packaging with Dependency Cab

[wendas]

We have created a ActiveX exe application. We call this from a standard exe application. The standard app. is located on the user pc.. the ActiveX app. is on the server (not user pc).

We are trying to be able to just point to the server project so that when we update it we can just swap in the new ActiveX exe and everyone can get the new version without re running setups for everyone.

We created a dependency cab for the ActiveX and can see the neccessary controls are bundled into it.

When we packaged and deployed the standard exe we included the dependency file for the ActiveX exe.. But when we run the application, it seems that the setup did not create the controls from the dependency package.

We are not sure if we put the dependency cab into the correct area of the package (we added it to the list where all the .ocx & .dll are).. or if we missed some other step to get the dependency cab to kick in.

We didn't package & deploy the ActiveX exe. but we did "make" the exe.. so are we missing steps here?

Thanks,
Wenda and Ann