wix3.11 | 易学教程

Require WIX Bootstrapper to reboot after .NET Framework installation and skip application launch

阅读更多关于 Require WIX Bootstrapper to reboot after .NET Framework installation and skip application launch

问题 Thanks to Andrei's answer here: Install .NET Framework 4.7.2 (if needed) with WIX installer I check to see if .NETFramework 4.7.2 is installed and install it. I have one slight problem remaining though... My main app has a post install action that launches the app. One can't launch the app until 4.7.2 has been installed AND the system has been rebooted. I could simply remove this post install action code from my apps installer, but it would be nice if it did launch the app if 4.7.2 was

WiX - VS Schema and Visual Studio 2019

阅读更多关于 WiX - VS Schema and Visual Studio 2019

问题 I'm having trouble upgrading a setup project that referenced Visual Studio 2017 and now I want to reference Visual Studio 2019. Product.wxs references the following properties (as documented here): VS2019_IDE_VCSHARP_PROJECTSYSTEM_INSTALLED VS2019_EXTENSIONS_DIR When building the setup I get the following error: Unresolved reference to symbol 'Property:VS2019_IDE_VCSHARP_PROJECTSYSTEM_INSTALLED' in section 'Product:*'. Unresolved reference to symbol 'Property:VS2019_EXTENSIONS_DIR' in section

WiX/MSI installer successfully runs for uninstalling an app but the app has not been uninstalled

阅读更多关于 WiX/MSI installer successfully runs for uninstalling an app but the app has not been uninstalled

问题 I created a Wix Installer for my Visual Studio 2017 project by using this Wix Toolset Visual Studio 2017 Extension from its original author Rob Mensching . The installer successfully installed the app but when I run the installer again to uninstall the app, the installer, as expected, first shows the option of either repairing or uninstalling the app. When I choose Uninstall option it successfully runs indicating it's uninstalling and finally shows the Finish button, but when I go to my

How do I make a 64 bit MSI?

阅读更多关于 How do I make a 64 bit MSI?

问题 I've specified: -arch x64 when running candle.exe . Platform=x64 on the Package . ProgramFiles64Folder as the Directory id where things get installed. and still, when the app gets installed, it goes to C:\Program Files (x86) . There are some other wxs generated by heat.exe . I tried adding -platform x64 and -platform win64 to the calls to heat.exe , but it made no difference. I read https://msdn.microsoft.com/en-us/library/gg513929.aspx The section on 64 bit installer in the Wix Cookbook How

How do I make a 64 bit MSI?

阅读更多关于 How do I make a 64 bit MSI?

I've specified: -arch x64 when running candle.exe . Platform=x64 on the Package . ProgramFiles64Folder as the Directory id where things get installed. and still, when the app gets installed, it goes to C:\Program Files (x86) . There are some other wxs generated by heat.exe . I tried adding -platform x64 and -platform win64 to the calls to heat.exe , but it made no difference. I read https://msdn.microsoft.com/en-us/library/gg513929.aspx The section on 64 bit installer in the Wix Cookbook How do I get WiX to generate a 64-bit MSI? and I think I'm doing everything that was described there. What

“Hide” Features Based on ALLUSERS / MSIINSTALLPERUSER

阅读更多关于 “Hide” Features Based on ALLUSERS / MSIINSTALLPERUSER

问题 I have an installer that I'm converting from being an admin-only installation into a Single Package Authoring installer capable of being installed for the current user or for all users. Two of my features require writing to a registry key that would not be available to a regular user. They deal with integration to another application, so I can't write the registry values somewhere else in user space... They have to go in this location. I'm not concerned with users not being able to install

Install .NET Framework 4.7.2 (if needed) with WIX installer

阅读更多关于 Install .NET Framework 4.7.2 (if needed) with WIX installer

问题 Help! I've inherited a .NET project with a WIX installer project. They make the implicit assumption that .NET Framework 4.5 is installed on each machine which for the most part is true. Now we are adding some features that require .NET Framework 4.7.2 . I'd like to modify the install set to check for the presence of 4.7.2 (or higher) and install via web if necessary. I've found some documentation that's partially answered my questions but I'm still very confused how to get started and how to

WiX Checkbox property only working if default value given

阅读更多关于 WiX Checkbox property only working if default value given

问题 As I understand it, in WiX, a checkbox is checked if the property is not null. So in order to default a checkbox to "Checked", the property must be defined apart from the checkbox. Given that, I have a checkbox that allows the user to choose whether or not they want a shortcut added to their desktop. Originally it was set up to be checked by default, but I'm now trying to change it so that it is unchecked by default. However, when I remove the property definition so that it won't be checked,

WiX Checkbox property only working if default value given

阅读更多关于 WiX Checkbox property only working if default value given

As I understand it, in WiX, a checkbox is checked if the property is not null. So in order to default a checkbox to "Checked", the property must be defined apart from the checkbox. Given that, I have a checkbox that allows the user to choose whether or not they want a shortcut added to their desktop. Originally it was set up to be checked by default, but I'm now trying to change it so that it is unchecked by default. However, when I remove the property definition so that it won't be checked, the option no longer works. The installer won't add the shortcut whether the checkbox is checked or not

“Hide” Features Based on ALLUSERS / MSIINSTALLPERUSER

阅读更多关于 “Hide” Features Based on ALLUSERS / MSIINSTALLPERUSER

I have an installer that I'm converting from being an admin-only installation into a Single Package Authoring installer capable of being installed for the current user or for all users. Two of my features require writing to a registry key that would not be available to a regular user. They deal with integration to another application, so I can't write the registry values somewhere else in user space... They have to go in this location. I'm not concerned with users not being able to install these 2 specific features if they aren't administrators and the installer functions without issue if they