wix3.5

How can I exclude files from being harvested with heat (WiX 3.5)?

梦想的初衷 提交于 2019-11-30 16:24:38
问题 I would like to harvest a folder with a lot of files by using heat.exe. But instead of harvesting all files, I would like to exclude specific file extensions like "*.txt" or something like that. How can I do this? 回答1: I think the only option for now is to harvest the entire folder and apply a transform to the resulting .wxs file (see -t:<xsl> switch) to exclude what is not required (txt files in your case). However, I didn't try the 3.5 version of heat (judging based on the 3.0), but I don't

WiX 3.5 Install Service from Heat, Need from Custom Action?

…衆ロ難τιáo~ 提交于 2019-11-30 15:32:38
问题 I have a VS2010 WiX project with a main .wxs file and an empty .wxs file. The empty .wxs is overwritten in the prebuild event of the project, using heat.exe to harvest everything from a console exe. The exe has InstallUtil hooks, and in the days of VS setup project the exe was installed as a Service. I tried to use the <ServiceInstall> bits in WiX, but when I specified the executable and other elements to get the Service installed, light complained of a collision between the .exe in the main

WiX 3.5 Install Service from Heat, Need from Custom Action?

最后都变了- 提交于 2019-11-30 14:10:38
I have a VS2010 WiX project with a main .wxs file and an empty .wxs file. The empty .wxs is overwritten in the prebuild event of the project, using heat.exe to harvest everything from a console exe. The exe has InstallUtil hooks, and in the days of VS setup project the exe was installed as a Service. I tried to use the <ServiceInstall> bits in WiX, but when I specified the executable and other elements to get the Service installed, light complained of a collision between the .exe in the main .wxs and the .exe in the heat-generated .wxs. I think Custom Action is not the best way to do the

Wix Not Removing Files on Uninstall

左心房为你撑大大i 提交于 2019-11-30 08:00:37
I've seen others' questions on this matter, but I can't make it work for me. I'm trying to get used to Wix so we can migrate our vdproj's (I feel like we've taken 1 step forward and 4 steps back here...the most basic of things have become completely non-trivial with Wix...but I do see value in having a fully fledged declarative markup for building installers). I have the following wxs in a wixproj in SharpDevelop. Install works. Uninstall does nothing and leaves the install folder and dll in place. What's the problem? Files.wxs: <?xml version="1.0"?> <Wix xmlns="http://schemas.microsoft.com

Error LGHT0301: Failed to open the database

你。 提交于 2019-11-30 06:41:58
I'm using WiX 3.5. Recently, the following WiX error started occurring frequently on the build server: light.exe (,): error LGHT0301: Failed to open the database. During validation, this most commonly happens when attempting to open a database using an unsupported code page or a file that is not a valid Windows Installer database. Please use a different code page in Module/@Codepage, Package/@SummaryCodepage, Product/@Codepage, or WixLocalization/@Codepage; or make sure you provide the path to a valid Windows Installer database. Which "database" does the error refer to? (None of the WiX source

wix specify licence shows nothing

拈花ヽ惹草 提交于 2019-11-30 04:12:37
I'm trying to specify the licence for my wix setup project. I have created a rtf with a few dummy lines in wordpad/notepad/vs tried a few different ways as I read there was an issue with ones created in word but I dont think that should apply here, in any case I also opened it up in notepad++ and verified there is no funky characters hidden in it. I am specifying the file like so <WixVariable Id="WixUILicenseRtf" Value="$(var.ProjectDir)\Resources\test.rtf" /> And the file exists under the project\Resources directory. When I run the installer all that is shown in the licence area is a blank

msiexec /a deploying .msi file[WIX]

ε祈祈猫儿з 提交于 2019-11-29 18:11:57
I have been asked to only deploy files that are bundled into MSI package. MSI contains 4 files, For that I'm using this command: `msiexec /a [path to MSI] TARGETDIR =[Application folder path]` Problem with above command is that it also deploys .MSI file to specified TARGETDIR which i don't want. Is there any workaround/way that i can only deploy that 4 files? Not to my knowledge, no. This is an administrative installation , and it is essentially just an extraction of the files embedded in the MSI file along with the MSI file itself - now adjusted to use external source files for installation,

WIX UI for multiple target directories

☆樱花仙子☆ 提交于 2019-11-29 16:12:07
I need the User to be able to set multiple different target directories for my installation. I have this directory structure: <Directory Id="TARGETDIR" Name="SourceDir"> <Directory Id="ProgramFilesFolder"> <Directory Id="DCOMPANY" Name="MyCompany" > <Directory Id="DMAIN" Name="MainDir"> <Directory Id="DPART1" Name="Part1"/> <Directory Id="DPART2" Name="Part2"/> </Directory> </Directory> </Directory> </Directory> I also have these Properties here <Property Id="WIXUI_INSTALLPATH" Hidden="yes" /> <Property Id="VARIABLE_PATH_DPART1" Value="DPART1" /> <Property Id="VARIABLE_PATH_DPART2" Value=

Wix Not Removing Files on Uninstall

喜夏-厌秋 提交于 2019-11-29 10:54:18
问题 I've seen others' questions on this matter, but I can't make it work for me. I'm trying to get used to Wix so we can migrate our vdproj's (I feel like we've taken 1 step forward and 4 steps back here...the most basic of things have become completely non-trivial with Wix...but I do see value in having a fully fledged declarative markup for building installers). I have the following wxs in a wixproj in SharpDevelop. Install works. Uninstall does nothing and leaves the install folder and dll in

Cannot register DLL using WiX

左心房为你撑大大i 提交于 2019-11-29 09:54:33
I am trying to register a DLL using WiX. Now I know and understand that I should use heat and get it to pull the registry information for me, but heat seems to fail with the following error message: heat.exe : warning HEAT5150 : Could not harvest data from a file that was expected to be a SelfReg DLL: C:\Users\seb\Desktop\Development\addin.dll. If this file does not support SelfReg you can ignore this warning. Otherwise, this error detail may be helpful to diagnose the failure: Unable to load file: C:\Users\seb\Desktop\Development\addin.dll, error: 193 I've looked around and found this post