Our installer uses major upgrades as described in many Wix documents.
I would like to add a little more comfort to the installer by giving the users
the following choices:
1. Uninstall the previous major version (4.0) during install of 5.0 or
2. Have 4.0 and 5.0 installed side by side
The instal
I use the SetupTypeDlg to let the user select whether to do a typical, custom
or complete installation.
I attach a custom action called "RequiredLicensesValidation" to the "DoAction"
events of the "TypicalButton" and "CompleteButton".
Inside of the "RequiredLicensesValidation" custom action I try
I use DTF to build a custom action Dll in C# (Wix Build 3.0.5217.0).
When I add the custom action named "SQLiteValidation" I encounter the
following installation error :
Error 1723. There is a problem with this Windows Installer package.
A DLL required for this install to complete could
I followed your suggestions and used "MergeMod.dll" via COM interop in my
little repackaging tool. This works perfectly.
After the successful merge I still have to do a couple of steps to patch the
resulting msi:
1. Extract the merge module's cab file
2. Insert the cab file into the "_Streams"
> WindowsInstaller.Installer automation interface but it'll port over to C#/DTF
> pretty easy.
>
>
> Christopher Painter, Author of Deployment Engineering Blog
> Have a hot tip, know a secret or read a really good thread that deserves
> attention? E-Mail Me
>
>
I consider using DTF to merge a merge module (msm) into an msi package.
Would you recommend DTF for this purpose? Where can I find additional
information (tutorial, examples) for it?
Regards,
Frank
--
Stay on top of ev
I consider using the autoupdate technology provided by the ClickThrough
project for a .NET 2.0 Windows Forms application.
Could somebody recommend ClickThrough from its own experiences?
Where can I found additional information (tutorial, examples) for it?
Regards,
Frank
7 matches
Mail list logo