>Hi all,
>
>The old ocx registration process is a hassle in Internet times. However we still use the MSCOMCT2.OCX extensively in our VFP stuff.
>Has anyone successfully built a manifest file to be used in conjunction to the ocx in order to run the component registration-free ?
>
>I understand that these files can be built with a MS tool called MT.exe - do not have one. Even better those running VB6 application can use a program called "make my manifest" to run xcopy deployment of their VB legacy apps.
>
>Not looking for this. A plain MSCOMCT2.OCX.MANIFEST file would certainly do the job :)

Check Inno setup - I think that it doesn't have this problem. Its setups compress very well (dial it to the max, isn't much slower), the autoregistration of components is quite common, and it seems to handle the manifest stuff by itself. "Seems to", because I don't have the Vista to try it on, but then I have users who did, and they aren't complaining.