Including windows component with Installer

[langals]

Hi there

I am new to Windows Installer and to building installation packages. I have built a vb application that uses various components, some shipped with Windows, others not. I want to include these in my installation file because I am not sure if a) these will be on the user's machine and b) there might be an older version to the one I am using that is not supported by my application.

Should I specify that the files should be overwritten if they are an older version? I am worried about doing this if there are other applications running on the target computer that are not compatible with the older version.

Another option might be to use private assemblies or side-by-side assembly sharing, but it does not seem as though this is supported on Windows 200 (I want my app to run on Windows 200 and Windows XP).

I am a bit confused about what to do here, and any advice would be most welcome.

langals

[sreeni]

Hi,

Use merge modules files (.msm) in your application. If you are packaging your apps in wise or installshield select required mergermodules for the tab. I guess that should solve your dilemma.

post me if you require somemore info.

Thanks
sreeni
meetstranger_2020@yahoo.com

[langals]

Hi there

Thanks for replying. Really appreciate it.

I just downloaded Installshield and it seems to indicate which modules are needed in ones vb app and include these as mergemodules.

1. Does InstallShield automatically create merge modules from the components, and what logic is built into this? Are they side-by-side assembly sharing? what is the difference between including the merge module and just including the component .dll / .ocx, etc.

2. Will these merge modules work on Windows 2000 as well as Windows XP.

3. Does Advanced Installer include this kind of functionality.

My goal here is to create a foolproof installation package without damaging the target pc. It seems the former is easier than the latter

Many thanks

langals

[langals]

Sorry, another question.

I am not sure how to create registery keys. I understand that it is not recommended to create these keys automatically and better to create them manually.

What should the value, type and data of the keys be, and which folder should this go into? Also, if the user already has this component on their computer (but a different version), will this create any problems?

thanks

langals

[langals]

Hi ther again

Sorry about the multiple posts

The more research I do the more complex it seems to become - "don't install system32 components on users system, because there might be version conflicts, etc...it might render the users system inoperable...". But then how do I know that the user has the right version of the file?

Would a simpler solution not be to simply install ALL of the needed components in the app directory file folder, and put a .local file to direct the application to first look at these files. Then I won't need to register these files, there won't be any version conflicts, and I can uninstall them afterwards and restore the system to how it was. Would this work? What if there is the same version of the file in the system32 folder and I install a duplicate in the app directory (but don't register it) and run it at the same time. Is this a problem?

Lastly, would .local files work on XP. It seems as though side-by-side sharing will not work on Windows 2000, and I want my app to be able to run on 2000 and XP..

many thanks

langals

[langals]

.....here is a list of the components that my app depends on, just so you know what I am dealing with....

comct332.ocx
mscomct2.ocx
COMCTL32.OCX
COMCT232.OCX
COMDLG32.OCX
MSWINSCK.OCX
MSSTDFMT.DLL
MSHFLXGD.OCX
MBSplit.ocx
mscomctl.ocx
Msflxgrd.ocx
MSINET.OCX
rtcdll.dll
wininet.dll
asycfilt.dll
COMCAT.dll
FlexlistBox.ocx
Msado20.tlb
Msvbm60.dll
oleaut32.dll
olepro32.dll
stdole2.tlb
VB6STKIT.dll

[Cata]

Sorrry, but we are only able to respond to Advanced Installer - related issues. You need to ask the support for your respective product.

Regards,
Cata