Visual Installer - different file versions detected

[cjac]

Does anyone use Visual Installer to create msi's for their VB projects? I have never used this package before but I'm now in the process of attempting to create an installer for my VB project. I have used the 'VB Installer' option when selecting a new project from the menu but now have a list of tasks displayed in the Task List of Visual Installer which are:
"One of more files in MSVBVM60.MSM have different versions than those installed on this machine."
"Neither a merge module nor depending information could be found for c:\winnt\system32\fdfacx.dll"
I have around 10 tasks listed for different files in the format of the above. Should I not have used the VB Installer wizard and maually added all the files necessary fot the VB project? Any help much appreciated, or if you could point me in the direction of any documentation that would explain these 'errors'?

Thanks
C

 

[x508]

HI, I have also come across this a couple of times, with each of my setups I get at least 3 such messages of file versions, however my setups install my App perfectly.

My opinion is that the Installer is simply fussy about the file versions but I am sure it still includes them.

Does your setup app install your app correctly?

**********************************
May the Code Be With You...
----------
x50-8 (X Fifty Eigt)

 

[cjac]

Hi there. I've not actually created the msi yet due to the above mentioned problems. I noticed there are a few components missing from what I have included in my project references in VB. It maybe that the missing components are standard Windows ones and will be on the client machine anyway. I don't fully understand the purpose of creating a merge module at persent? Why not just include all components in the msi? Shouldn't the msi be checking for exisiting components and only replacing if new component is a more recent version than the installed component? ie. References in VB project:
C:\WINNT\System32\msvbvm60.dll
C:\WINNT\System32\msvbvm60.dll\3
C:\Program Files\Mircosoft Visual Studio\VB98\VB6.OLB
C:\WINNT\System32\STDOLE2.TLB
C:\WINNT\System32\shdocvw.oca
c:\Program Files\Common Files\System\ADO\msado25.tlb
C:\WINNT\System32\msbind.dll
C:\WINNT\System32\fdfacx.dll
C:\Program Files\Microsoft Office\Office\MSWORD9.OLB
C:\WINNT\System32\msrdo20.dll
C:\Program Files\Microsoft Office\Office\EXCEL9.OLB

Files included in Visual Installer project:
excel9.olb
msado25.tlb
msword9.olb
pdf.ocx
fdfacx.dll
fm20.dll
gsdll32.dll

Would it not be better to manually add the required files into the windows system directory and app dir in the Visual Installer project?

Thanks
C

 

[x508]

The first thing you should do is to create the Install APP and see if it works.

Being a Visual Studio Installer, I'm sure it can determine the best possible solutions to which components should and should not be installed.

**********************************
May the Code Be With You...
----------
x50-8 (X Fifty Eigt)

 

[cjac]

I was kinda thinking that, like it should know exactly what is needed, being a Windows Installer an' all.
I'll just run with it and create the msi. I'll find out soon enough if it's missing any components when I distribute it!
Thanks for the advice.

Cheers
C

 

[x508]

np

**********************************
May the Code Be With You...
----------
x50-8 (X Fifty Eigt)