wix

问题 I have a general task: install .NET Framework 3.5 during the setup of my product. I do the following: I have created a custom action X Custom action X starts an executable Y via Process.Start() Executable Y kills the msiexec process and run .NET Framework setup package Here appear some problems: .NET Framework setup says that Windows Installer Service is not accessible and asks to terminate all another installations! I think, the cause of it is that Process.Kill() method terminate the process

问题 <?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"

问题 I have creeated an installer, which installs a database using the sqlstring element provided by the WixSqlExtension. Here is a sample of the code: <ComponentGroup Id="DatabaseCreation" Directory="INSTALLFOLDER"> <Component Id="CreateDatabase" Guid="SOMEGUID" KeyPath="yes"> <sql:SqlString Id="CreateDB" Sequence="1" ExecuteOnInstall="yes" ContinueOnError="no" SqlDb="MasterDB" SQL="DECLARE @dbname nvarchar(128) SET @dbname = N'{[SQLDATABASE]}' IF(NOT EXISTS (SELECT name FROM master.dbo

问题 We are using Wix to build msi for our software. We have some components (plugins) to be implemented to the target machine. The plugins are different from one client to another. What we want to be able to do is to create a standard build and modify the feature list in the msi package. Is there a way to change the feature list dynamically from a custom action? (e.g. read the available plugins from a custom action and add some entries into the msi feature list accordingly)? Any comments, advice,

问题 Using WiX Toolset 3.10, and trying to create shortcuts to certain files that have been harvested with the heat.exe utility, as by: "%WIX%\bin\heat.exe" dir SourceDir -nologo -platform x64 ^ -ke -gg -g1 -suid -srd -scom -sreg -dr INSTALLDIR ^ -cg ProjFiles -out ProjFiles.wxs My issues: I know by now that I'm supposed to use an XSLT file to transform ProjFiles.wxs (the -t option in heat.exe ) but WiX-specific documentation on how to write it is non-existent: can someone please provide an

问题 I am trying to programmatically find the exe file that is run for a given MSI lnk file (advertised shortcut). I have used an approach similar to that shown in the answer to Is there a way to resolve a .lnk target that works for links that end up in c:\windows\installer?. This approach works fine for the majority of MSI lnk files. Unfortunately there are a minority of lnk files that run fine, but MsiGetShortcutTarget returns no component id. So the subsequent call to MsiGetComponentPath

问题 Trying to get a wix installer to kill a process, from what I have found online it looks like this is the way to go: <Directory Id="TARGETDIR" Name="SourceDir"> <Directory Id="WindowsFolder" Name="WINDOWS"/> <Property Id="QtExecCmdLine" Value='"[WindowsFolder]System32\taskkill.exe" /F /IM Foo.exe'/> <CustomAction Id="KillTaskProcess" BinaryKey="WixCA" DllEntry="CAQuietExec" Execute="immediate" Return="ignore"/> The problem I have is building the project will throw the following error

问题 Is there any way to execute a custom action in WIX as soon as the first dialog (welcome) appears? The requirement is to check prerequisites, and some of those require a custom action. The custom action could be executed as we click to the next dialog, but then the standard WIX prereqs are determined apart from our custom prereq. (The custom action we need is to check that IIS 6 Metabase Compatibility is turned on and a registry search does not work on x64 machines with a 32-bit installer) 回答1

问题 I have a Burn bundle with this chain: <Chain> <PackageGroupRef Id="NetFx40Web"/> <MsiPackage SourceFile="c:\\My\\Path\\MyMsi.msi" Id="MyMsi" DisplayName="MyMsi" DisplayInternalUI="yes" Vital="yes"> <MsiProperty Name="INSTALLLOCATION" Value="[InstallFolder]" /> </MsiPackage> </Chain> Both .NET framework and my MSI files are installed correctly. But the MSI package is not uninstalled during uninstall procedure (both after clicking on the bootstrapper EXE or from Programs And Features). Is there

问题 Does Burn support dual-purpose (per-user or per-machine) MSI packages which were prepared according to these Microsoft guidelines? I tried to prepare such a package, but it looks like bootstrapper created with Burn doesn't uninstall MSI package, which was installed per-machine after raising UAC privileges by End-User. The source code for Burn is: <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi" xmlns:util="http://schemas.microsoft.com/wix/UtilExtension" xmlns:bal="http://schemas