We have a product installer created with Wix, containing a program package (\"V1\") and some configuration files. Now, we are going to make a major upgrade with a new product code, where the old versi
Background: I would like to extract the COM data from a VB6 application so I can register it correctly (according to Microsoft best practice) the application.I am using WiX 3.0 and heat.exe will not
My patching system is severely limited in that whenever I need to patch my software product and add any new file I am prevented from using the \'-delta\' flag. If I do use this flag, when the msp runs
I need both these files, PathwaysMDF and PathwaysLDF to replace (overwrite) the old copies on a major upgrade.
Related to this: How to register file types/extensions with a WiX installer? but not a duplicate. I need to handle existing file types (.jpg files).
ARGH!Wix is driving me crazy. So, of course I have seen the many posts both here on stackoverflow and elsewhere about WiX and major upgrades.I inherited this software project using WiX and am releasi
We have a WiX fragment in a file SomeDialog.wxs that prompts the user for some information.It\'s referenced in another fragment in InstallerUI.wxs file that controls the dialog order.Of course, Produc
In my MSI package I need to set user rights to a directory using cacls.exe. It works fine in an NTFS environment but fails when run on a Fat32 file system. Is there a method to determine the type of f
I am trying to put together an installer using WiX 3.0 and I\'m unsure about one thing. I would like to use the FeaturesDlg dialog to allow the users to select features to install, but I need to be ab
I’m seeing some odd behaviour I can’t explain. I\'m using wix to generate a msi and using the msbuild GenerateBootstrapper task to handle pre-requisites. It all seems to build correctly i.e. there
加载中,请稍侯......