wix3.5

问题 i am not to able to pass "[SourceDir]" path when SourceDir path has spaces. ex: SourceDir = "C:\Temp\Setup" i am able to send "C:\Temp\Setup" path to custom action SourceDir = "C:\Temp setup\Setup" wix passing only "C:\Temp" to custom action ExeCommand="[SourceDir]Setup" 回答1: You need to enclose it in quotes like so: ExeCommand=""[SourceDir]Setup"" 回答2: I found I also had to put in a second set of "s but with an escaping \ "\"[Path with spaces]\"" I believe this is because the text gets

问题 I created an installer, deployed to our test environment and got an error due to a missing dll (it was not included in the wsx file). Is it possible to create a MSP patch to ship the missing dll or is it better to simply create a whole new installer? I tried following various examples but I keep getting this error: DEBUG: Error 2356 : Couldn't locate cabinet in stream: media1.cab. 回答1: A patch can do anything an updated MSI can do, but it is merely a packaging and delivery mechanism that

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

问题 I've got a WIX installation project for my application. As part of my solution I have a VSIX extension, that I want to install on the customer's Visual Studio. What I don't know, is how to get WIX to automatically initiate the VSIX importer. I tried following the advice on MSDN (How to: Prepare Extensions for Windows Installer Deployment as well as Installing a VSIX as part of a Larger installation), to no avail. Neither included guidance for WIX projects. Any help will be appreciated. 回答1:

问题 I have wix installer and it copies some files to some directories. Each file is declared as single component, with some path - if directory does not exist, installer will create it and place file there. What I want to do: if directory already exists, installer should not copy any files there (even if file does not exists, it should not be copied to already existing directory). But it's impossible to set "Never overwrite" to directory, so how can I prevent copy new files to already existing

问题 I'm updating one of our installers for .NET 4.0 and IIS 7.5, and one of the tasks is to switch the AppPool over to use its own identity. I have found this fairly trivial in WiX using the IIS Extension, but I'm struggling with two extra sets of permissions that we define, specifically to grant write permissions to the AppPool Identity: <Directory Id="LOGS_LOCATION" Name="logs"> <!-- SourceDir\logs --> <Component Id="LogsFolder" Guid="{3A7C38C7-6604-4063-A425-D62427B21AEE}" KeyPath="yes" DiskId

问题 I have some dll compiled either in .Net3.5 or in .Net4.0. (They have the same name) In wix, I have 2 conditionals features. Feature A installs .net3.5 dll of my app with ComponentRef Id="Cmp35" Feature B installs .net4.0 dll with ComponentRef Id="Cmp40" Features are mutually exclusives, only one feature is installed. my components: <?xml version="1.0" encoding="UTF-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"> <Fragment> <DirectoryRef Id="INSTALLDIR"> <Component Id="Cmp35" Guid=

问题 I need to use variable in WIX localization file WIXUI_en-us.wxl. I tried use it like this: <String Id="Message_SomeVersionAlreadyInstalled" Overridable="yes">A another version of product $(var.InstallationVersionForGUI) is already installed</String> But it doesn't work. And when I declared property and used it this way: <String Id="Message_SomeVersionAlreadyInstalled" Overridable="yes">A another version of product [InstallationVersionForGUI] is already installed</String > doesn't work either.

问题 I once had TeamCity + WiX + MSBuild Community Tasks working. Now that I've upgraded to WiX 3.5, I can't remember how I had configured it. :) As I was poking through TeamCity, I came across the "AssemblyInfo Patcher". I thought, "Great! This will make my life much easier!". I used %build.vcs.number.1% for the format and built my installer. While the patcher did pull in the vcs number, it used it for the major number in the version. So instead of 1.0.0.xxxx , it made the version xxxx.0.0.0 . I

问题 We were using WIX 3.5 (Build Number 1811) and built a custom action built using Visual Studio 2008 and with target framework as .Net 3.5. This used to work great, until we built the custom action using Visual Studio 2010 and with target framework as .Net 4.0. WIX is unable to invoke the custom action, the error that we get is this: SFXCA: Extracting custom action to temporary directory: C:\Windows\Installer\MSI69BD.tmp-\ SFXCA: Binding to CLR version v2.0.50727 Calling custom action