Re: [WiX-users] Add text to final window in burn bootstrapper/installer

I was actually looking for the change where I can have a separate header for uninstalls. Don't have a problem adding text or changing the current header. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Add-text-to-final-window-in-burn-bootstrapper-

Re: [WiX-users] Add text to final window in burn bootstrapper/installer

I do not see the change in v4 or v3.9. Any idea when this feature will be included? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Add-text-to-final-window-in-burn-bootstrapper-installer-tp7588444p7593500.html Sent from the wix-users mailing list

Re: [WiX-users] Cabinet does not contain any files

ceDir' Sascha On Mon, Dec 7, 2009 at 5:04 AM, Trevor wrote: > I'm using a fragment outputted from heat as my project includes a few > thousand files, so in VS I have a sourcefile.wxs: > > > > > > http://schemas.microsoft.com/wix/2006/wi";> > >  

[WiX-users] Cabinet does not contain any files

I'm using a fragment outputted from heat as my project includes a few thousand files, so in VS I have a sourcefile.wxs: http://schemas.microsoft.com/wix/2006/wi";> What determines what the folder "SourceDir" is? Since this is

[WiX-users] Problem harvesting website

I'm attempting to harvest a website on Windows 7 and am receiving this error: C:\Program Files (x86)\Windows Installer XML v3.5\bin>heat website "Default Web Site" -template:product -out C:\Users\trevor\Desktop\website.wxs Microsoft (R) Windows Installer Xml Toolset

[WiX-users] CustomAction tied to feature?

I need to call two separate 3rd party installation Setup.exe files during my WiX installation. I have managed to do so by using the following XML:

[WiX-users] Registry Entry befor Service Install

need the registry values to be removed prior to the service unloading (ServiceControl). How can I guarantee the order of these during install/uninstall? I am trying the following: Thanks in advance, -Trevor

Re: [WiX-users] Vista & unknown publisher [OT]

h would be a super set of the Organizational Certificate. It is not required to go with VeriSign and their prices in order to get the Digital ID's. Hope that helps, otherwise ask directly as to not disturb others who are having WiX issues. -Trevor -Original Message- From: Martin Cetk

Re: [WiX-users] Vista & unknown publisher

tures and services. https://winqual.microsoft.com/help/default.htm#obtaining_a_verisign_class_3_ digital_id.htm So, choose whomever you wish, but we found that paying more didn't get you anything extra. -Trevor -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]

Re: [WiX-users] Wix Version

could help you migrate easily at a later date. If v2 satisfies your needs now, then I would say to stick with it. That's my opinion! -Trevor _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, May 24, 2007 12:10 AM To: wix-

Re: [WiX-users] Variables

Or, yet another example -Trevor _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthony Wieser Sent: Tuesday, May 22, 2007 1:35 AM To: Wik Carl-Johan; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Variables Sorry, som

Re: [WiX-users] Conditional statement?

/wix_xsd_condition.htm Hope that helps. -Trevor _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Burton Sent: Wednesday, May 16, 2007 2:53 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Conditional statement? I have only found which is a

Re: [WiX-users] Prevent installing on Windows 2000

n also check if it is 64 bit or not with VersionNT64 Us this reference for the syntax: http://msdn2.microsoft.com/en-us/library/aa368012.aspx and use this reference for the values look here: http://msdn2.microsoft.com/en-us/library/aa370556.aspx -Trevor -Original Message- From: Nick [

Re: [WiX-users] Prevent installing on Windows 2000

I do just the opposite and require it to be 2k or better. Here is my "Condition" line to do that: You would modify the condition to be > 500 instead of >= 500 to exclude the Win2k. Then you can also customize your Condition message as you wish. -Trevor -Original Message--

[WiX-users] Persist ini file parameters for use during reinstall, repair

trieving them? If anyone can help provide a sample or some direction it would be greatly appreciated. -Trevor - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take

Re: [WiX-users] Port monitor + printer driver

p://schemas.microsoft.com/wix/2003/01/wi";> Good Luck, -Trevor -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stefan Pavlik Sent: Tuesday, April 10, 2007 2:56 AM To: Friedri

[WiX-users] Using Registered Sign in Name property

Thanks Rob, The codepage was not set for the Product which is what describes the resulting msi file. Instead I had set the SummaryCodepage for the package. It is now set in both places to 1252 and the Registered Symbol shows up correctly. -Trevor -Original Message- From: [EMAIL

[WiX-users] Using Registered Sign in Name property

underlined and then eg; follows &0256; - Candle Error: fatal error CNDL0031: An error occurred while parsing EntityName. \0256 - this is not escaped Does anyone have any ideas on how to get this R symbol to appear correctly in the MSI and to not give an error in the WiX? Thanks in advance, -Tr