Re: [WiX-users] WiX 3.8 Votive Drawing Error?

[bwehking]

I got it! 

Steps to reproduce in VS2013:
- Go to Tools->Options->Environment and choose Color theme "Dark"
- restart Visual Studio
- View the "Paths" property page of a .wixproj

Voila! It looks like the "Paths" page simply uses a wrong background color!
In the Dark theme _only_ the "Paths" page is grey and the text color is grey
as well! All the other pages are dark! 

I hope this helps.

Bernd



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-3-8-Votive-Drawing-Error-tp7591851p7591919.html
Sent from the wix-users mailing list archive at Nabble.com.

--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Fwd: Creating registry for an application installed outside the current directory structure in WIX file

[Suvrajyoti Panda]

I do intend, but for that scenario i am changing the path accordingly, 
using  %~d0\Installers path.

On 21-01-2014 11:07, Blair Murri wrote:
> And you don’t intend on installing them on any other machine?
>
>
>
>
>
>
> Blair
>
>
>
>
>
> From: Suvrajyoti Panda
> Sent: ‎Monday‎, ‎January‎ ‎20‎, ‎2014 ‎9‎:‎18‎ ‎PM
> To: General discussion for Windows Installer XML toolset.
>
>
>
>
>
> Hi Blair,
>
> I build them from the same machine at the same from another location.
>
> Regards,
> SuvraJyoti
> On 21-01-2014 09:48, Blair Murri wrote:
>> You only install MSIs on the same machine you build those MSIs from?
>>
>>
>>
>>
>>
>>
>> Blair
>>
>>
>>
>>
>>
>> From: Suvrajyoti Panda
>> Sent: ‎Wednesday‎, ‎January‎ ‎15‎, ‎2014 ‎11‎:‎14‎ ‎PM
>> To: General discussion for Windows Installer XML toolset.
>>
>>
>>
>>
>>
>> Thanks David that works.
>>
>> I have used as below:
>>
>> 
>>> Path="$(var.SimulatorSearchRoot)" AssignToProperty="yes">
>>> Name="StandaloneSimulator.exe"/>
>>  
>> 
>>
>> Adding to it, is there any way i can refer to the root directory of the
>> current directory where the wix file is. My wix file is in the location
>> D:\Project\ESI\PLTLPLO\trunk\releaseFiles\GameraInstaller, how can i
>> refer to the root directory "D:\". I want to use this value in the path
>> attribute of DirectorySearch. If anyone has used the same please let me
>> know.
>>
>> Regards,
>> SuvraJyoti
>>
>> On 15-01-2014 20:53, David Watson wrote:
>>> If you are not shipping the simulator and it is already on the target 
>>> machine you can use a directory/file search to search the hard disk for it 
>>> then use the resulting property to set the registry value.
>>>
>>> See 
>>> http://wixtoolset.org/documentation/manual/v3/howtos/files_and_registry/parentdirectorysearch.html
>>>
>>>
>>> -Original Message-
>>> From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in]
>>> Sent: 15 January 2014 11:51
>>> To: General discussion about the WiX toolset.
>>> Subject: [WiX-users] Fwd: Creating registry for an application installed 
>>> outside the current directory structure in WIX file
>>>
>>> Hi All,
>>>
>>> To add to the below issue, i understand that i could use a property that 
>>> includes the registry search. But issue here is that the application 
>>> "StandaloneSimulator.exe" is not something that has been installed on my 
>>> machine(i cannot find it under control panel). The 
>>> D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin exists as it has been 
>>> checked out from SVN.Please let me know in case there are any workarounds.
>>>
>>>
>>>  Original Message 
>>> Subject:   Creating registry for an application installed outside the
>>> current directory structure in WIX file
>>> Date:  Wed, 15 Jan 2014 12:44:55 +0530
>>> From:  Suvrajyoti Panda 
>>> To:General discussion about the WiX toolset.
>>> 
>>>
>>>
>>>
>>> Hi All,
>>>
>>> I am creating an wix installer. I want to create a registry entry whose 
>>> path is not under the directory structure created in the WIX file. Below is 
>>> what i intend to do:
>>>
>>> 
>>>   
>>>
>>>
>>> >> Guid="{C769AC98-A3D0-4CB4-939F-F396B49D4E5F}" Win64="no">
>>>  >> Root="HKLM" Key="SOFTWARE\[Manufacturer]"
>>> Name="$(var.standalonesimulatorRegName)"
>>> *Value="D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin" *Type="string" />
>>>
>>>>> Guid="{0ED0A7FC-DCB1-4C36-A39B-56F9F97A3A2C}" Win64="yes">
>>>  >> Root="HKLM" Key="SOFTWARE\[Manufacturer]"
>>> Name="$(var.standalonesimulatorRegName)"
>>> Value="*D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin*" Type="string" />
>>>
>>>
>>>   
>>> 
>>>
>>> The *Value *in the above keys is the path where an application 
>>> "standalonesimulator.exe" is installed.Please suggest if there is anyway 
>>> that i do not have to hardcode this path. I know i can use an include file 
>>> and fetch this path, but again that path will be harcoded in the include 
>>> file anyways.
>>>
>>> Regards,
>>> SuvraJyoti
>>>
>>>
>>> --
>>> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
>>> Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical 
>>> Workloads, Development Environments & Everything In Between.
>>> Get a Quote or Start a Free Trial Today.
>>> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
>>> ___
>>> WiX-users mailing list
>>> WiX-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>> SDL PLC confidential, all rights reserved.
>>> If you are not the intended recipient of this mail SDL requests and 
>>> requires that you delete it without acting upon or copying any of its 
>>> contents, and we further request that you advise us.
>>> SDL PLC is a publ

Re: [WiX-users] Fwd: Creating registry for an application installed outside the current directory structure in WIX file

[Blair Murri]

And you don’t intend on installing them on any other machine?






Blair





From: Suvrajyoti Panda
Sent: ‎Monday‎, ‎January‎ ‎20‎, ‎2014 ‎9‎:‎18‎ ‎PM
To: General discussion for Windows Installer XML toolset.





Hi Blair,

I build them from the same machine at the same from another location.

Regards,
SuvraJyoti
On 21-01-2014 09:48, Blair Murri wrote:
> You only install MSIs on the same machine you build those MSIs from?
>
>
>
>
>
>
> Blair
>
>
>
>
>
> From: Suvrajyoti Panda
> Sent: ‎Wednesday‎, ‎January‎ ‎15‎, ‎2014 ‎11‎:‎14‎ ‎PM
> To: General discussion for Windows Installer XML toolset.
>
>
>
>
>
> Thanks David that works.
>
> I have used as below:
>
> 
>Path="$(var.SimulatorSearchRoot)" AssignToProperty="yes">
>Name="StandaloneSimulator.exe"/>
> 
>
>
> Adding to it, is there any way i can refer to the root directory of the
> current directory where the wix file is. My wix file is in the location
> D:\Project\ESI\PLTLPLO\trunk\releaseFiles\GameraInstaller, how can i
> refer to the root directory "D:\". I want to use this value in the path
> attribute of DirectorySearch. If anyone has used the same please let me
> know.
>
> Regards,
> SuvraJyoti
>
> On 15-01-2014 20:53, David Watson wrote:
>> If you are not shipping the simulator and it is already on the target 
>> machine you can use a directory/file search to search the hard disk for it 
>> then use the resulting property to set the registry value.
>>
>> See 
>> http://wixtoolset.org/documentation/manual/v3/howtos/files_and_registry/parentdirectorysearch.html
>>
>>
>> -Original Message-
>> From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in]
>> Sent: 15 January 2014 11:51
>> To: General discussion about the WiX toolset.
>> Subject: [WiX-users] Fwd: Creating registry for an application installed 
>> outside the current directory structure in WIX file
>>
>> Hi All,
>>
>> To add to the below issue, i understand that i could use a property that 
>> includes the registry search. But issue here is that the application 
>> "StandaloneSimulator.exe" is not something that has been installed on my 
>> machine(i cannot find it under control panel). The 
>> D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin exists as it has been 
>> checked out from SVN.Please let me know in case there are any workarounds.
>>
>>
>>  Original Message 
>> Subject:   Creating registry for an application installed outside the
>> current directory structure in WIX file
>> Date:  Wed, 15 Jan 2014 12:44:55 +0530
>> From:  Suvrajyoti Panda 
>> To:General discussion about the WiX toolset.
>> 
>>
>>
>>
>> Hi All,
>>
>> I am creating an wix installer. I want to create a registry entry whose path 
>> is not under the directory structure created in the WIX file. Below is what 
>> i intend to do:
>>
>> 
>>  
>>   
>>
>>> Guid="{C769AC98-A3D0-4CB4-939F-F396B49D4E5F}" Win64="no">
>> > Root="HKLM" Key="SOFTWARE\[Manufacturer]"
>> Name="$(var.standalonesimulatorRegName)"
>> *Value="D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin" *Type="string" />
>>   
>>   > Guid="{0ED0A7FC-DCB1-4C36-A39B-56F9F97A3A2C}" Win64="yes">
>> > Root="HKLM" Key="SOFTWARE\[Manufacturer]"
>> Name="$(var.standalonesimulatorRegName)"
>> Value="*D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin*" Type="string" />
>>   
>>   
>>  
>>
>>
>> The *Value *in the above keys is the path where an application 
>> "standalonesimulator.exe" is installed.Please suggest if there is anyway 
>> that i do not have to hardcode this path. I know i can use an include file 
>> and fetch this path, but again that path will be harcoded in the include 
>> file anyways.
>>
>> Regards,
>> SuvraJyoti
>>
>>
>> --
>> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
>> Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical 
>> Workloads, Development Environments & Everything In Between.
>> Get a Quote or Start a Free Trial Today.
>> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>> SDL PLC confidential, all rights reserved.
>> If you are not the intended recipient of this mail SDL requests and requires 
>> that you delete it without acting upon or copying any of its contents, and 
>> we further request that you advise us.
>> SDL PLC is a public limited company registered in England and Wales.  
>> Registered number: 02675207.
>> Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 
>> 7DY, UK.
>>
>>
>>
>> This message has been scanned for malware by Websense. www.websense.com
>>
>> 

Re: [WiX-users] Web Setup

[Blair Murri]

When you use the property remember pattern, all packages that store/retrieve 
the property at the same location will “remember” the same value. If you need 
the two setups to have different values, you should consider using two 
different registry locations for your property remember pattern.






Blair​





From: Tony Jose Mampilly
Sent: ‎Wednesday‎, ‎January‎ ‎15‎, ‎2014 ‎11‎:‎12‎ ‎PM
To: General discussion for Windows Installer XML toolset.





Hi,

I have created 2 web setups in a similar manner. In installation UI, the
user can change the name of virtual directory if needed. By default it
displays the name I have given in CDATA. The first web installer works as
required, but problem comes on installation of second installer. During the
installation, the default virtual directory name displayed is fetched from
the first installer. Say I gave name of first virtual directory as 123, and
I need the name of second virtual directory as 345, but by default it
displays 123. We can change if we want, but I need it to be displayed
correctly. If I am uninstalling the first website, then it works fine.
Somebody please help me with this issue, its urgent. Any help appreciated
The codes can be accessed at
https://drive.google.com/folderview?id=0B1gCMqS-Y9BFcFVPaEFVZjQwdFk&usp=sharing

Thank you

Regards
Tony
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Fwd: Creating registry for an application installed outside the current directory structure in WIX file

[Suvrajyoti Panda]

Hi Blair,

I build them from the same machine at the same from another location.

Regards,
SuvraJyoti
On 21-01-2014 09:48, Blair Murri wrote:
> You only install MSIs on the same machine you build those MSIs from?
>
>
>
>
>
>
> Blair
>
>
>
>
>
> From: Suvrajyoti Panda
> Sent: ‎Wednesday‎, ‎January‎ ‎15‎, ‎2014 ‎11‎:‎14‎ ‎PM
> To: General discussion for Windows Installer XML toolset.
>
>
>
>
>
> Thanks David that works.
>
> I have used as below:
>
> 
>Path="$(var.SimulatorSearchRoot)" AssignToProperty="yes">
>Name="StandaloneSimulator.exe"/>
> 
>
>
> Adding to it, is there any way i can refer to the root directory of the
> current directory where the wix file is. My wix file is in the location
> D:\Project\ESI\PLTLPLO\trunk\releaseFiles\GameraInstaller, how can i
> refer to the root directory "D:\". I want to use this value in the path
> attribute of DirectorySearch. If anyone has used the same please let me
> know.
>
> Regards,
> SuvraJyoti
>
> On 15-01-2014 20:53, David Watson wrote:
>> If you are not shipping the simulator and it is already on the target 
>> machine you can use a directory/file search to search the hard disk for it 
>> then use the resulting property to set the registry value.
>>
>> See 
>> http://wixtoolset.org/documentation/manual/v3/howtos/files_and_registry/parentdirectorysearch.html
>>
>>
>> -Original Message-
>> From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in]
>> Sent: 15 January 2014 11:51
>> To: General discussion about the WiX toolset.
>> Subject: [WiX-users] Fwd: Creating registry for an application installed 
>> outside the current directory structure in WIX file
>>
>> Hi All,
>>
>> To add to the below issue, i understand that i could use a property that 
>> includes the registry search. But issue here is that the application 
>> "StandaloneSimulator.exe" is not something that has been installed on my 
>> machine(i cannot find it under control panel). The 
>> D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin exists as it has been 
>> checked out from SVN.Please let me know in case there are any workarounds.
>>
>>
>>  Original Message 
>> Subject:   Creating registry for an application installed outside the
>> current directory structure in WIX file
>> Date:  Wed, 15 Jan 2014 12:44:55 +0530
>> From:  Suvrajyoti Panda 
>> To:General discussion about the WiX toolset.
>> 
>>
>>
>>
>> Hi All,
>>
>> I am creating an wix installer. I want to create a registry entry whose path 
>> is not under the directory structure created in the WIX file. Below is what 
>> i intend to do:
>>
>> 
>>  
>>   
>>
>>> Guid="{C769AC98-A3D0-4CB4-939F-F396B49D4E5F}" Win64="no">
>> > Root="HKLM" Key="SOFTWARE\[Manufacturer]"
>> Name="$(var.standalonesimulatorRegName)"
>> *Value="D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin" *Type="string" />
>>   
>>   > Guid="{0ED0A7FC-DCB1-4C36-A39B-56F9F97A3A2C}" Win64="yes">
>> > Root="HKLM" Key="SOFTWARE\[Manufacturer]"
>> Name="$(var.standalonesimulatorRegName)"
>> Value="*D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin*" Type="string" />
>>   
>>   
>>  
>>
>>
>> The *Value *in the above keys is the path where an application 
>> "standalonesimulator.exe" is installed.Please suggest if there is anyway 
>> that i do not have to hardcode this path. I know i can use an include file 
>> and fetch this path, but again that path will be harcoded in the include 
>> file anyways.
>>
>> Regards,
>> SuvraJyoti
>>
>>
>> --
>> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
>> Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical 
>> Workloads, Development Environments & Everything In Between.
>> Get a Quote or Start a Free Trial Today.
>> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>> SDL PLC confidential, all rights reserved.
>> If you are not the intended recipient of this mail SDL requests and requires 
>> that you delete it without acting upon or copying any of its contents, and 
>> we further request that you advise us.
>> SDL PLC is a public limited company registered in England and Wales.  
>> Registered number: 02675207.
>> Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 
>> 7DY, UK.
>>
>>
>>
>> This message has been scanned for malware by Websense. www.websense.com
>>
>> --
>> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
>> Learn Why More Businesses Are Choosing CenturyLink Cloud For
>> Critical Workloads, Development Environments & Everything In Betwee

Re: [WiX-users] Fwd: Creating registry for an application installed outside the current directory structure in WIX file

[Blair Murri]

You only install MSIs on the same machine you build those MSIs from?






Blair





From: Suvrajyoti Panda
Sent: ‎Wednesday‎, ‎January‎ ‎15‎, ‎2014 ‎11‎:‎14‎ ‎PM
To: General discussion for Windows Installer XML toolset.





Thanks David that works.

I have used as below:


 
 
   
  

Adding to it, is there any way i can refer to the root directory of the 
current directory where the wix file is. My wix file is in the location 
D:\Project\ESI\PLTLPLO\trunk\releaseFiles\GameraInstaller, how can i 
refer to the root directory "D:\". I want to use this value in the path 
attribute of DirectorySearch. If anyone has used the same please let me 
know.

Regards,
SuvraJyoti

On 15-01-2014 20:53, David Watson wrote:
> If you are not shipping the simulator and it is already on the target machine 
> you can use a directory/file search to search the hard disk for it then use 
> the resulting property to set the registry value.
>
> See 
> http://wixtoolset.org/documentation/manual/v3/howtos/files_and_registry/parentdirectorysearch.html
>
>
> -Original Message-
> From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in]
> Sent: 15 January 2014 11:51
> To: General discussion about the WiX toolset.
> Subject: [WiX-users] Fwd: Creating registry for an application installed 
> outside the current directory structure in WIX file
>
> Hi All,
>
> To add to the below issue, i understand that i could use a property that 
> includes the registry search. But issue here is that the application 
> "StandaloneSimulator.exe" is not something that has been installed on my 
> machine(i cannot find it under control panel). The 
> D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin exists as it has been 
> checked out from SVN.Please let me know in case there are any workarounds.
>
>
>  Original Message 
> Subject:   Creating registry for an application installed outside the
> current directory structure in WIX file
> Date:  Wed, 15 Jan 2014 12:44:55 +0530
> From:  Suvrajyoti Panda 
> To:General discussion about the WiX toolset.
> 
>
>
>
> Hi All,
>
> I am creating an wix installer. I want to create a registry entry whose path 
> is not under the directory structure created in the WIX file. Below is what i 
> intend to do:
>
> 
> 
>  
>
>Guid="{C769AC98-A3D0-4CB4-939F-F396B49D4E5F}" Win64="no">
> Root="HKLM" Key="SOFTWARE\[Manufacturer]"
> Name="$(var.standalonesimulatorRegName)"
> *Value="D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin" *Type="string" />
>  
>   Guid="{0ED0A7FC-DCB1-4C36-A39B-56F9F97A3A2C}" Win64="yes">
> Root="HKLM" Key="SOFTWARE\[Manufacturer]"
> Name="$(var.standalonesimulatorRegName)"
> Value="*D:\Project\ESI\PFW\trunk\StandaloneSimulator\bin*" Type="string" />
>  
>  
> 
>   
>
> The *Value *in the above keys is the path where an application 
> "standalonesimulator.exe" is installed.Please suggest if there is anyway that 
> i do not have to hardcode this path. I know i can use an include file and 
> fetch this path, but again that path will be harcoded in the include file 
> anyways.
>
> Regards,
> SuvraJyoti
>
>
> --
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical 
> Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> SDL PLC confidential, all rights reserved.
> If you are not the intended recipient of this mail SDL requests and requires 
> that you delete it without acting upon or copying any of its contents, and we 
> further request that you advise us.
> SDL PLC is a public limited company registered in England and Wales.  
> Registered number: 02675207.
> Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 
> 7DY, UK.
>
>
>
> This message has been scanned for malware by Websense. www.websense.com
>
> --
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>

--
CenturyLink Cloud: The Leader in 

Re: [WiX-users] FW: CertificatePath in Certificate element does not work

[Blair Murri]

The only certificate installation bug I found in the old sourceforge site was 
this: http://sourceforge.net/p/wix/bugs/1353/ and that one was marked fixed in 
2008 (it also describes a different bug with the same error code) and in the 
new system is found here: http://wixtoolset.org/issues/1768/.


The "tracker” link below isn’t to a specific bug but to the “bugs” group on SF.


Otherwise the existing bug report never contained the error number.


I would suggest opening a new bug. Include your knowledge of the Overwrite 
attribute causing the error message. Also please include the with the bug 
report.






Blair





From: Knapp Edgar
Sent: ‎Wednesday‎, ‎January‎ ‎15‎, ‎2014 ‎11‎:‎42‎ ‎AM
To: General discussion for Windows Installer XML toolset.





This keeps getting returned for some reason.

-Original Message-
From: MonteChristo [mailto:edgar.kn...@sepura.com] 
Sent: Wednesday, January 15, 2014 8:35 PM
To: 'wix-users@lists.sourceforge.net'
Subject: Re: CertificatePath in Certificate element does not work

robmen wrote
> http://wix.sourceforge.net/ link on the right to the bug database:
> http://sourceforge.net/tracker/?group_id=105970&atid=642714
> 
> 
> --
> virtually, Rob Mensching - http://RobMensching.com LLC
> --
> 

Hi,

A brief summary of the problem: When< iis:Certificate> is used with 
CertificatePath="Some\Path\To\Cert.pfx" and Overwrite="yes", installs fail with 
a rather misleading

InstallCertificates:  Error 0x80070057: Invalid Certificate.Attributes.
InstallCertificates:  Error 0x80070057: Failed to resolve certificate: 
SSL_Cerificate CustomAction InstallCertificates returned actual error code 1603 
(note this may not be 100% accurate if translation happened inside sandbox)

Turns out that Overwrite="yes" is the culprit. 

This bug has been reported and acknowledged long ago, but is still present in 
WiX 3.8. The quoted link to the bug database is a dead end. I just lost an 
entire afternoon to this because who would think that Overwrite="yes" causes 
this failure, and then only when CertificatePath is used?

Would someone please supply an update on this bug and, if appropriate, a fresh 
link to its entry in the bug database?

Also, there is zero documentation on the semantics of the Overwrite property. 

Thanks,

EK




--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CertificatePath-in-Certificate-element-does-not-work-tp6579192p7591789.html
Sent from the wix-users mailing list archive at Nabble.com.




--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Error Building WixProj from DevEnv Command Line

[Blair Murri]

dunno. I always use msbuild from the command line:


“FullPathToMSBuild.exe” /nologo /t:Rebuild “FullPathToSolutionFile”




DevEnv has always been a black box and has never been particularly build-box 
friendly.


You’ll have to use DevEnv on solutions containing projects that aren’t 
compatible with MSBuild, but there are fewer of those project types remaining 
with each new release of VS.




Blair





From: Dave Echols
Sent: ‎Wednesday‎, ‎January‎ ‎15‎, ‎2014 ‎10‎:‎47‎ ‎AM
To: General discussion for Windows Installer XML toolset.





I have a VS 2010 solution that contains 2 Wix projects for two different 
installs. I can compile/build the solution from within the Visual Studio IDE 
without errors. When I build the solution from the command line using 
DevEnv.exe, I get the following error on one of the projects...

MySetup.wixproj : error  : Catastrophic failure (Exception from HRESULT: 
0x8000 (E_UNEXPECTED))

One or more projects in the solution were not loaded correctly.
Please see the Output Window for details.

I am using the following command line to build the solution...

"FullPathToDevEnv.exe" /nologo /rebuild "FullPathToSolutionFile"

The other project in the solution builds without errors. I have examined each 
project file in a text editor and they are nearly identical, except for 
different files and different names/Guids. Any ideas on what might be causing 
this error and how I can make it go away?

Thanks in advance for any help.



David S. Echols
Senior Programmer

H&A Architects & Engineers | www.ha-inc.com
222 Central Park Ave., Suite 1200, Virginia Beach, Virginia 23462
d: (757) 213-6049 p: (757) 222-2010 f: (757) 222-2022

Follow Us: Twitter | 
Facebook | 
LinkedIn
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Creating registry for an application installed outside the current directory structure in WIX file

[Blair Murri]

What is "standalonesimulator.exe"’s file id?






Blair





From: Suvrajyoti Panda
Sent: ‎Tuesday‎, ‎January‎ ‎14‎, ‎2014 ‎11‎:‎27‎ ‎PM
To: General discussion for Windows Installer XML toolset.





Hi All,

I am creating an wix installer. I want to create a registry entry whose 
path is not under the directory structure created in the WIX file. Below 
is what i intend to do:


   


 
  


  


   
 

The *Value *in the above keys is the path where an application 
"standalonesimulator.exe" is installed.Please suggest if there is anyway 
that i do not have to hardcode this path. I know i can use an include 
file and fetch this path, but again that path will be harcoded in the 
include file anyways.

Regards,
SuvraJyoti
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Deleting files in a patch...

[Blair Murri]

Null/empty component guid components are only installed in major upgrades. 
Patches are not typical major upgrades and those components are ignored (just 
as with all other maintenance transactions).


As it says: it cannot be removed or repaired. A patch is basically always “a 
repair” (after the view is upgraded by applying the patch).






Blair





From: Mita Patel
Sent: ‎Tuesday‎, ‎January‎ ‎14‎, ‎2014 ‎1‎:‎59‎ ‎PM
To: General discussion for Windows Installer XML toolset.





Re: Deleting files in a patch.
Applying the same logic to a patch does not work.   
We set the component id for new files that do not need to be registered to 
null.   (to allow for  deletion in future patches)
Then apply the patch.  Resulting in the null component id files not getting 
installed.

Message: 6
Date: Tue, 14 Jan 2014 11:29:15 -0800
From: Phil Wilson 
Subject: Re: [WiX-users] Deleting files in a patch...
To: "General discussion for Windows Installer XML toolset."

Message-ID:

Content-Type: text/plain; charset=ISO-8859-1

It looks like you hijacked an existing discussion thread, so I'll start a new 
one. ...

Yes, that's the way it works. That might not be the best way to remove files if 
you decide you want them back later. An alternative is to make the component 
transitive and use a property to make the actual file be present or absent, so 
if you later decide you want the file present just set the property value. It 
can be tricky to make that work in all cases, such as adding/removing features, 
repair, patches etc because you need to preserve the property value that is 
keeping the file present or absent.

"The msdn doc says the following for component id in the column table.
ComponentId --> If this column is null the installer does not register the 
component and the component cannot be removed or repaired by the installer.
This might be intentionally done if the component is only needed during the 
installation, such as a custom action that cleans up temporary files or removes 
an old product. It may also be useful when copying data files to a user's 
computer that do not need to be registered.

Does this mean in the full msi, components with null id will not be registered 
and if deleted then will  not put the msi in repair?  Which further indicates 
that at  patch time we can call a custom action to delete these components , 
and this will not throw the msi in repair mode?"

Phil Wilson
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Buindle Major Upgrade cause first msi uninstallation

[Tim Comport]

For anyone coming across this issue in the future, I have filed a bug report 
here   .




--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Buindle-Major-Upgrade-cause-first-msi-uninstallation-tp7590764p7591906.html
Sent from the wix-users mailing list archive at Nabble.com.

--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] best way to handle su8pporting files

[Phil Wilson]

You can put the file in the Binary table (maybe encrypted)  and stream
it out yourself, decrypting it. Or you can install it (encrypted) but
give the component a null guid so that it is not registered, and can
therefore be removed with a custom action or some other method after
its been used. Without knowing when you're doing that compile (at
install time? Some indeterminate time after it?) it's tricky to
recommend anything specific.

You won't be able to make the file secure because (as far as I know)
the compiler probably can't read encrypted files, so it would have to
be plain text for a brief time even if you shipped it encrypted and
decrypted it for the compile process. There is no way to hide it in
the MSI file because they are very transparent, but you could encrypt
it so it couldn't easily be deciphered using something like Orca.

Phil Wilson


On Mon, Jan 20, 2014 at 5:55 AM, Sean Farrow
 wrote:
> Hi,
> Yes, it is because of the integration. The compile process needs to be done 
> on the target machine.
> Cheers
> Sean.
>
> -Original Message-
> From: Wesley Manning [mailto:wmann...@dynagen.ca]
> Sent: 20 January 2014 13:18
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] best way to handle su8pporting files
>
> Why can't you just compile the source code beforehand and place the binary in 
> the installer?  It's because of the integration; you are compiling both 
> together?  Usually you can compile your software into an intermediate library 
> that the user can use and compile with their software.  Any change on doing 
> that?
>
> -Original Message-
> From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk]
> Sent: January-19-14 7:16 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] best way to handle su8pporting files
> Importance: High
>
> Hi All,
> I'm in a situation where I'm doing some work for a client integrating some 
> software we have written in to a piece of software they use.
> They haven't paid for the source, so leaving this behind is not an option.
> What I need to do is to copy the source file to the target machine, compile 
> this file and then remove the source file leaving the compiled binary.
> Given that RemoveFiles comes before InstallFiles in the InstallExecute 
> sequence what is the best way of doing this?
> Is there a mechanism for some form of support files in windows installer that 
> are copied to the users machine but not actually installed?
> Any help appreciated.
> Cheers
> Sean.
> --
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical 
> Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> --
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical 
> Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> --
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users

--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] WiX 3.8 Votive Drawing Error?

[JohnLudlow]

Do you get any issues if you create any issues with other project types? If
you create a C# project and go to the properties, does it display correctly?



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-3-8-Votive-Drawing-Error-tp7591851p7591900.html
Sent from the wix-users mailing list archive at Nabble.com.

--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] best way to handle su8pporting files

[Sean Farrow]

Hi,
Yes, it is because of the integration. The compile process needs to be done on 
the target machine.
Cheers
Sean.

-Original Message-
From: Wesley Manning [mailto:wmann...@dynagen.ca] 
Sent: 20 January 2014 13:18
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] best way to handle su8pporting files

Why can't you just compile the source code beforehand and place the binary in 
the installer?  It's because of the integration; you are compiling both 
together?  Usually you can compile your software into an intermediate library 
that the user can use and compile with their software.  Any change on doing 
that? 

-Original Message-
From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk]
Sent: January-19-14 7:16 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] best way to handle su8pporting files
Importance: High

Hi All,
I'm in a situation where I'm doing some work for a client integrating some 
software we have written in to a piece of software they use.
They haven't paid for the source, so leaving this behind is not an option.
What I need to do is to copy the source file to the target machine, compile 
this file and then remove the source file leaving the compiled binary.
Given that RemoveFiles comes before InstallFiles in the InstallExecute sequence 
what is the best way of doing this?
Is there a mechanism for some form of support files in windows installer that 
are copied to the users machine but not actually installed?
Any help appreciated.
Cheers
Sean.
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical 
Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical 
Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Enabling platform features during install

[Loïc Delambre]

Hi,

I used a command line tool embedded in my burn package like a prerequisite, 
this tool calls pkgmgr.exe in order to enable Windows features.





Regards,
Loïc Delambre

-Message d'origine-
De : Stephen I. Woolhead [mailto:s...@gtl.biz] 
Envoyé : vendredi 17 janvier 2014 19:11
À : General discussion about the WiX toolset.
Objet : [WiX-users] Enabling platform features during install

Hi, following up on an issue that came up in another thread, we have the need 
to enable platform features such as MSMQ during our install.  At the moment we 
do this during install with dism.exe in a custom action.  This so far has 
worked well for us but it was hinted this was not ideal.

Does anyone have any guidance about enabling platform features during install 
that they could share?

Cheers,

Stephen.
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical 
Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] best way to handle su8pporting files

[Wesley Manning]

Why can't you just compile the source code beforehand and place the binary in 
the installer?  It's because of the integration; you are compiling both 
together?  Usually you can compile your software into an intermediate library 
that the user can use and compile with their software.  Any change on doing 
that? 

-Original Message-
From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] 
Sent: January-19-14 7:16 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] best way to handle su8pporting files
Importance: High

Hi All,
I'm in a situation where I'm doing some work for a client integrating some 
software we have written in to a piece of software they use.
They haven't paid for the source, so leaving this behind is not an option.
What I need to do is to copy the source file to the target machine, compile 
this file and then remove the source file leaving the compiled binary.
Given that RemoveFiles comes before InstallFiles in the InstallExecute sequence 
what is the best way of doing this?
Is there a mechanism for some form of support files in windows installer that 
are copied to the users machine but not actually installed?
Any help appreciated.
Cheers
Sean.
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical 
Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] WiX 3.8 Votive Drawing Error?

[bwehking]

Thank you for your reply. That's strange... I will keep an eye on it.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-3-8-Votive-Drawing-Error-tp7591851p7591891.html
Sent from the wix-users mailing list archive at Nabble.com.

--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Failed to resolve source for file after reboot in custom BAL

[Tobias S]

Just for completeness.
OnResolveSource was not the proper way to do what we wanted (Setting the
local source to the started Bundle after reboot). SetLocalSource did the
trick.
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users