I have been reading up on manifests. Thanks for the suggestion - it looks like this is the way to go.

I have several questions - perhaps you know the answers to some of them?

1: My application has a small program goRun.exe that calls an APP. If I call the manifest file goRun.exe.manifest, will that be good for the OCXs used in the APP, or do I need a manifest for the APP as well. Perhaps "MyApp.APP.manifest"?

2: If goRun.exe calls another exe (goRun2.exe), does goRun2.exe need a manifest file as well, or does it "inherit" the initial one.

3: When my application gets installed on the F: drive, I have been running a second install file on each user's PC that registers the controls on their computer. With a manifest file, I guess that this would not be needed anymore - a shortcut to the EXE on the network drive would work correctly?

4. What about files that get installed under Common files, for example, Crystal reports. At the moment I install these on each user's PC, and register them on each PC, example:
Register Library $COMMONFILES$\Crystal Decisions\2.0\bin\crqe.dll

I am inclined to leave this alone, as so far it works Would it be better to bring these into the manifest instead of doing the registration?

I am just starting off with manifests, so I will be doing a lot of experiments. Any other tips?


Thanks
Cyril



>>If RichTx32.ocx is in the same folder as the application, does it need to be registered?
>
>Hi Cyril,
>
>Yes and no. Traditionally you have to register and ActiveX because the registry is used by an application to find it. Starting with Windows XP, a manifest can be used instead of registration. See Simplify App Deployment with ClickOnce and Registration-Free COM and http://community.acresso.com/showthread.php?t=149554. Check also http://blogs.msdn.com/calvin_hsia/archive/2007/04/13/add-a-manifest-to-control-your-application-vista-uac-behavior.aspx