wix3.6

问题 I'm about to create an installer, now i have to set the install-directory depending on the operation-system. My directory-tree: <Property Id="TARGETDIR" Value="C:\" /> <Directory Id="TARGETDIR" Name="SourceDir"> <Directory Id="TARGETDIRECTORY" Name="MyApplication"> <Directory Id="CONFIG" Name="Config"> <Directory Id="FOLDER2" Name="Folder2" /> </Directory> </Directory> </Directory> if i set the TARGETDIRECTORY in the c#-custom-action, the targetdirectory gets set correct, but the CONFIG

问题 <?xml version="1.0" encoding="UTF-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi" xmlns:util="http://schemas.microsoft.com/wix/UtilExtension"> <Bundle Name="My Test Program" Version="1.0.0.0" Manufacturer="Microsoft" UpgradeCode="cc7cfeae-c3a4-4430-841e-f927de3f9f95"> <BootstrapperApplicationRef Id="WixStandardBootstrapperApplication.RtfLicense" /> <util:RegistrySearch Id="FindDotNet35SP1InstallRegValue" Root="HKLM" Key="SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5" Value="SP"

问题 We have an MSI and Bundle created in Wix. I need to localize both of these in such a way that language selection GUI will be popped-up and language can be selected by the user at run time. Would be really appreciated if anybody can help me on this. For MSI, i am working on creating another bootstapper for bringing-up with language selection combobox and invoke the tranfomed MSI with the required transform(using command shell). I am still not sure about the feasibilty of this approach. I am

问题 I build a perMachine installer using WiX 3.6 to install a software I had not developed. Unfortunately the software creates some registry keys under HKCU during execution. On uninstall, the self created keys should also be removed. It seems not so easy to remove these keys. I am "fighting" with ICE57 and/or ICE38. Both complaining the mix between perUser and perMachine data. Hopefully you can point me in the right direction on fixing this issue. 回答1: To overcome ICEs you should move Per-User

问题 I'm aware of similar questions in WiX MSI, but I'm having issues starting an application within a bootstrapper EXE file created with Burn after the installation. My full bundle is below. If it makes any difference to the scenario, the bootstrapper is started in passive mode, so the user shouldn't need to press anything. <?xml version="1.0" encoding="UTF-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi" xmlns:bal="http://schemas.microsoft.com/wix/BalExtension" xmlns:util="http:/

问题 I'm using WixUI_Advanced sequence to allow users pick per-machine or per-user installation and change destination folder. My WiX project is intended to produce both x86 and x64 MSIs (I'm using WiX Tips and Tricks recommendations). I also keep the app installation folder in the registry for major upgrades (I use APPLICATIONFOLDER property and directory ID -- instead of INSTALLLOCATION -- per WixUI_Advanced requirements). There is a bug in WixUI_Advanced sequence that causes the Destination

问题 In base version of my setup, by mistakenly i added the same name for two files like: <component id="x" GUID="guid value"> <file id="x" source="c:\files\x.dll" name="x.dll"> </component> <component id="y" GUID="another guid value"> <file id="y" source="c:\files\y.dll" name="x.dll"> </component> Now I want to change the name to "y.dll" for the file with id="y" using HotFix. If we change the name directly, the compiler error has been thrown "Component "y" has a changed keypath in the transform

问题 How can I continue my installer after it reboots during installation of some package? Actually, I have build an installer package of a project using WiX bundles (having different packages to install in a chain). But when it installs Microsoft Windows Installer 4.5 (.msi) it goes to reboot the PC. After it reboots, I want my installation to continue after that. How can I do that? I guess we can do it with the use of the exit code, but I don't know how to use it in WiX bundles. 回答1: Yes, you

问题 In my custom Burn managed bootstrapper application, I want a way to set the default log directory of the installer so that customers can easily find the installation logs. If this can't be done, I would like a suitable way to copy the log files after installation. I tried unsuccessfully at setting the WixBundleLog variable in my setup project (i.e. Bundle.wxs) and in my managed bootstrapper application. Also, my bootstrapper applicaton is generic enough so that it my be used with a variety of

问题 I have one MSI setup like this: <Product Id="*" ... UpgradeCode="4207FF3B-5E0D-4311-9DFC-B41AA8DE2965" /> <MajorUpgrade DowngradeErrorMessage="Can't downgrade" /> It works as expected: Install product Recompile (effectively generating a new Id) Starting the new msi file brings up the change view and I can repair or uninstall the product. Good. But then comes burn. I have created the most simplistic Bundle one can thing of. I use the standard bootrapper and just add one single MsiPackage: