date:20130827

If you are intending to use the 32-bit registry in a 64-bit platform in 
RegEdit, you need to start from the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node 
(which is the 32-bit HKEY_LOCAL_MACHINE\SOFTWARE key).
You make TARGETDIR conditional by setting a property by that name to the full 
path (hopefully with a backslash ('\') at the end) before costing starts in 
whatever sequence starts first. Same with INSTALLDIR. Subdirectories will 
automatically use the path set for their parents if a path is not presupplied. 
During costing, properties will be created for all directories that didn't 
already have properties (and each one will be set to the full path of that 
directory).
AppSearch, et. al. will set the property you specify. So will the command-line. 
By default, the *Search actions will override the command-line.

 From: rob...@softdev.net
 To: wix-users@lists.sourceforge.net
 Date: Mon, 26 Aug 2013 23:52:18 +
 Subject: Re: [WiX-users] RegistrySearch example in tutorial
 
 Thanks for both replies. I am indeed on a x64 machine and have no idea how to 
 distinguish between x86/x64 registries. I've probably created the key in the 
 wrong one. Any pointers? To open the editor, I type in regedit
 
 If not that, then how should I make this conditional:
 
   Directory Id='TARGETDIR' Name='SourceDir'
 Directory Id='ProgramFilesFolder' Name='PFiles'
   Directory Id='Acme' Name='Acme'
 Directory Id='INSTALLDIR' Name='Foobar 1.0'
 
 -Original Message-
 From: Phil Wilson [mailto:phildgwil...@gmail.com] 
 Sent: Tuesday, 27 August 2013 4:49 AM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] RegistrySearch example in tutorial
 
 What often happens is that there is a custom action to set the default 
 INSTALLDIR location to the program files folder, and people forget to make it 
 conditional, with a condition like NOT INSTALDIR.  You may find that if you 
 set INSTALLDIR on an msiexec command line it would also get overwritten. The 
 NOT INSTALLDIR condition just means don't set it to default if it's already 
 set.
 
 Phil Wilson
 
 
 On Mon, Aug 26, 2013 at 3:42 AM, Blair Murri os...@live.com wrote:
 
  Adding is not overridding, it is creating.
  That would suggest that there is no InstallDir value at 
  HKLM\Software\Acme\Foobar 1.0 Do you have a 32-bit MSI and are trying 
  to read a 64-bit registry location, per chance? Or vice versa?
 
   From: rob...@softdev.net
   To: wix-users@lists.sourceforge.net
   Date: Mon, 26 Aug 2013 06:31:51 +
   Subject: [WiX-users] RegistrySearch example in tutorial
  
   I'm a novice user, going through Getting Started. I cannot get the
  RegistrySearch to work, or FILEEXISTS - both from Where to Install? 
  page in your tutorial.
  
   I suspect it is because this element:
   Property Id=INSTALLDIR
 RegistrySearch Id='AcmeFoobarRegistry' Type='raw' Root='HKLM'
  Key='Software\Acme\Foobar 1.0' Name='InstallDir' /
   /Property
  
   is overridden by the subsequent
  
   Directory Id='TARGETDIR' Name='SourceDir'
 Directory Id='ProgramFilesFolder' Name='PFiles'
   Directory Id='Acme' Name='Acme'
 Directory Id='INSTALLDIR' Name='Foobar 1.0'
  
   Meaning that if the registry sets a directory outside of program 
   files,
  then it seems to not work because later in the wxs file it is 
  contained within ProgramFilesFolder. Logging reveals it is overridden:
  
   MSI (c) (50:AC) [16:21:36:966]: PROPERTY CHANGE: Adding INSTALLDIR
  property. Its value is 'C:\Program Files (x86)\... etc
  
   I realise the file is not read sequentially.
  
   Regards,
   Robert
  
  --
  
   Introducing Performance Central, a new site from SourceForge and 
   AppDynamics. Performance Central is your source for news, insights, 
   analysis and resources for efficient Application Performance Management.
   Visit us today!
  
  http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.c
  lktrk
   ___
   WiX-users mailing list
   WiX-users@lists.sourceforge.net
   https://lists.sourceforge.net/lists/listinfo/wix-users
 
 
  --
   Introducing Performance Central, a new site from SourceForge 
  and AppDynamics. Performance Central is your source for news, 
  insights, analysis and resources for efficient Application Performance 
  Management.
  Visit us today!
  http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.c
  lktrk ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users
 
 --
 Introducing Performance Central, a new site from SourceForge and AppDynamics. 
 Performance Central is your

Re: [WiX-users] DCOM Launch and Access permissions

Looks to me like a really good thing to include in WiX. Would you be willing to 
contribute it?

 Date: Tue, 27 Aug 2013 17:08:37 +1200
 From: benjamins...@gmail.com
 To: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] DCOM Launch and Access permissions
 
 Cool, thanks Phil.  I was hoping for some native support for DCOM in WIX
 utilities or something like that... but alas I don't think it exists.
 
 I hadn't discovered this SDK sample before though, so it is very helpful.
  I would just build this into a custom action for the WIX installer
 obviously?
 
 Cheers
 Ben
 
 
 On Tue, Aug 27, 2013 at 7:35 AM, Phil Wilson phildgwil...@gmail.com wrote:
 
  I don't know if there's anything more recent, but DCOMPerm can be used for
  this:
 
  http://msdn.microsoft.com/en-us/library/aa242178(v=vs.60).aspx
 
  Phil Wilson
 
 
  On Sat, Aug 24, 2013 at 4:20 AM, Benjamin Sole benjamins...@gmail.com
  wrote:
 
   Hi there, does anyone know if there is a way to change the launch and
   access permission for a DCOM Component via WIX?
  
  
  --
   Introducing Performance Central, a new site from SourceForge and
   AppDynamics. Performance Central is your source for news, insights,
   analysis and resources for efficient Application Performance Management.
   Visit us today!
  
  http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
   ___
   WiX-users mailing list
   WiX-users@lists.sourceforge.net
   https://lists.sourceforge.net/lists/listinfo/wix-users
  
 
  --
  Introducing Performance Central, a new site from SourceForge and
  AppDynamics. Performance Central is your source for news, insights,
  analysis and resources for efficient Application Performance Management.
  Visit us today!
  http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
  ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users
 
 --
 Introducing Performance Central, a new site from SourceForge and 
 AppDynamics. Performance Central is your source for news, insights, 
 analysis and resources for efficient Application Performance Management. 
 Visit us today!
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
  
--
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Modifiing Burn UI to make silent

2013-08-27 Thread Natalie Carr

Is there any way to modify burn to only show the Msi dialogs? I would like
to use burn to install .Net Framework but don't like the two dialogs being
shown and have tried to play around with the HyperLinkTheme.xml but cannot
figure out if it can be done so that it is silent and to fire the Msi
dialogs.

 

Thanks

Natalie

--
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] The Last Error Received is: 0xc00000fd (-1073741571) while creating a patch

This is interesting to me:The last files being compared were RegistASM.exe. The
Comparing bytes message is from the comparison of the files in the Comparing
Files message just previous.
The error is being reported on TSResourceDllChs.dll. That isn't the same file.
This suggests that it was done comparing all of the files that could possibly
be in that transform, and it was in the process of either making deltas,
building cabs, or adding the patch header to the appropriate patch tables when
it errored out.
Did you supply PDB files? What happens if you remove them (or conversely add
them if they weren't there)?

From: jocoo...@jackhenry.com
To: wix-users@lists.sourceforge.net
Date: Mon, 26 Aug 2013 18:03:50 +
Subject: Re: [WiX-users] The Last Error Received is: 0xc0fd (-1073741571)
while creating a patch

0xc0fd is Unknown Software Exception. It's usually related to a stack
overflow somewhere.

--
John Merryweather Cooper
Build Install Engineer -- ESA
Jack Henry Associates, Inc.(r)
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com

-Original Message-
From: Shaun Greenfield [mailto:sgreenfi...@tradestation.com]
Sent: Monday, August 26, 2013 12:26 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] The Last Error Received is: 0xc0fd (-1073741571)
while creating a patch

Hi all:

Wondering if anyone can shed light on this - have a huge application where
patch creation was working fine till Friday last week. After investigating,
*NO* configuration changes to my build system were made other than some
updates from Microsoft. The system consistently stops on the same file as
seen in the snippet below -

INFO Comparing Files:
D:\TradeStation\Platform\TS\Dev\TS9.4\Source\WixInstall\TradeStation\bin\Release\Admin\Build290\TradeStation
Technologies\TradeStation\RegistASM.exe
D:\TradeStation\Platform\TS\Dev\TS9.4\Source\WixInstall\TradeStation\bin\Release\Admin\Build298\TradeStation
Technologies\TradeStation\RegistASM.exe...
INFO Comparing bytes...
ERROR: Cannot create patch file for
'D:\TradeStation\Platform\TS\Dev\TS9.4\Source\WixInstall\TradeStation\bin\Release\Admin\Build298\program
files\TradeStation 9.4\Program\TSResourceDllChs.dll' at 'C:\Temp'.
ERROR: The Last Error Received is: 0xc0fd (-1073741571)
INFO: Temporary folder is about to be cleaned out and deleted: C:\Temp
ERROR: Internal PatchWiz Error occurred.
ERROR: The Last Error Received is: 0x91 (145)
ERROR: During cleanup, could not delete the temporary folder: C:\Temp.
ERROR: The Last Error Received is: 0x91 (145)

The file in question is a resource only .dll about 11-13 megs in size (we
have one per language we support). I tried including the whole file to see
if the system would then pick on the next resource .dll in question but even
with that change we still crash. MsiMsp is version 5.x (latest I'm aware
of). Assumed first it was low space or another annoying Temp issue so I
checked - plenty of space (60 gig) and cleaned out Temp with the same results.

Any advice anyone can share would be greatly appreciated - I'm stumped with
this one.

Thanks,
Shaun

TradeStation Group, Inc. is the parent company of five separate but
affiliated operating subsidiaries, TradeStation Securities, Inc. (Member
NYSE, FINRA, NFA and SIPC), IBFX, Inc. (Member NFA), IBFX Australia Pty Ltd,
which is authorized and regulated by the Australian Securities and
Investments Commission, TradeStation Technologies, Inc., a trading software
and subscription company, and TradeStation Europe Limited, a United Kingdom,
FSA-authorized introducing brokerage firm. None of these companies provides
trading or investment advice, recommendations or endorsements of any kind.
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and dele
te the material from any computer. Forex products and services are offered by
the TradeStation Forex divisions of IBFX, Inc. (Member NFA) and IBFX Australia
Pty Ltd (ASIC registered).

--
Introducing Performance Central, a new site from SourceForge and AppDynamics.
Performance Central is your source for news, insights, analysis and resources
for efficient Application Performance Management.
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list

Re: [WiX-users] Modifiing Burn UI to make silent

This has been discussed on this list. The two proposed solutions were 1) 
command-line, and 2) a custom BA.
It has also been suggested on this same list that that isn't the best user 
experience (think repair and removal where the MSI UI is NOT available at all 
via Burn). Burn isn't intended as a fire-and-forget bootstrapper, it instead is 
intended to be a fully featured chainer.

 From: natalie.c...@measuresoft.com
 To: wix-users@lists.sourceforge.net
 Date: Tue, 27 Aug 2013 10:35:41 +0100
 Subject: [WiX-users] Modifiing Burn UI to make silent

 Is there any way to modify burn to only show the Msi dialogs? I would like
 to use burn to install .Net Framework but don't like the two dialogs being
 shown and have tried to play around with the HyperLinkTheme.xml but cannot
 figure out if it can be done so that it is silent and to fire the Msi
 dialogs.

 Thanks

 Natalie

 --
 Introducing Performance Central, a new site from SourceForge and 
 AppDynamics. Performance Central is your source for news, insights, 
 analysis and resources for efficient Application Performance Management. 
 Visit us today!
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Custom element

That page in the docs is part of the reference, and the reference pages assume 
that you know how you wish to configure your custom action and simply give the 
syntax required to express it in WiX.
The tutorial and the book are both great places to get more beginners 
information on Windows Installer custom actions.
 From: laasu...@hotmail.com
 To: wix-users@lists.sourceforge.net
 Date: Tue, 27 Aug 2013 09:28:03 +0200
 Subject: [WiX-users] Custom element

 Hello,

 Reading the http://wixtoolset.org/documentation/manual/v3/xsd/wix/custom.html 
 docs. Would it be possible to specify the legal values for attribute before 
 and after, and inner value? 

 Using google I found the state 'InstallInitialize' and 'InstallFinalize' 
 which solved two issues. However it would be nice if the docs could have told 
 me. I guess there might be other states aswell.

 For the inner text I used NOT Installed and Installed, again based on 
 google. In this case I am more confussed as to how it works. How does the 
 installer know if something is installer or not? What other options do I 
 have? What happens if I enter no inner text?

 Sorry for all the questions. Just thought I would give a feedback.

 Regards, Lars

 --
 Introducing Performance Central, a new site from SourceForge and 
 AppDynamics. Performance Central is your source for news, insights, 
 analysis and resources for efficient Application Performance Management. 
 Visit us today!
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] [Wix]: Conditional installation for Windows Server 2008/Windows Server 2012

I'm not understanding your request. VersionNT is a property indicating the 
platform version of windows, expressed (in the case of MSI) as an integer.
If you tell us what you are trying to do with VersionNT and what you want your 
package to do between different platforms, we could help more. An example of 
your current non-working code would help as well.

 Date: Tue, 27 Aug 2013 12:49:10 +0530
 From: dileep.sanamp...@gmail.com
 To: wix-users@lists.sourceforge.net
 Subject: [WiX-users] [Wix]: Conditional installation for Windows Server 
 2008/Windows Server 2012

 Hi All,

 I have created MSI/EXE using Wix based on OS (Operating System).

 Used VersionNT property values for creating MSI/EXE.

 Installation is not working for Windows Server 2008/Windows Server 2012.

 How can I check the conditional installation for Windows Server
 2008/Windows Server 2012.

 Please help me to solve this...
 --
 Introducing Performance Central, a new site from SourceForge and 
 AppDynamics. Performance Central is your source for news, insights, 
 analysis and resources for efficient Application Performance Management. 
 Visit us today!
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

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

Which UI are you using in your bundle?

 From: afor...@cmu.edu
 To: wix-users@lists.sourceforge.net
 Date: Mon, 26 Aug 2013 18:55:39 -0400
 Subject: [WiX-users] Add text to final window in burn bootstrapper/installer
 
 Hi all,
 
 Our installer bundled with burn currently posts a simple Setup Complete 
 message when the install is done. How can we add additional text on this last 
 window when the install is complete?
 
 Thanks,
 Alain
 
 
 --
 Introducing Performance Central, a new site from SourceForge and 
 AppDynamics. Performance Central is your source for news, insights, 
 analysis and resources for efficient Application Performance Management. 
 Visit us today!
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
  
--
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] MSBuild wix project file - how to detect skipped and specific culture

You could try looking at the msbuild files supplied with WiX, but the go/no-go 
data for linking depends on what compile did, so in reality it won't be 
straightforward to determine pre-compile what the decision will be at link.
AfterCompileAndLink fires after all cultures have been linked.

 Date: Sun, 25 Aug 2013 13:48:19 -0700
 From: phogl...@rimage.com
 To: wix-users@lists.sourceforge.net
 Subject: [WiX-users] MSBuild wix project file - how to detect skipped and 
 specific culture

 Is there a MSBuild Task or a method of conditioning one of the Targets that
 fires prior to Compile, so that my in-line task will not fire if linking is
 going to be skipped?

 I notice that when I add a task to Target MsiSign that it does not file if
 linking is skipped (which is the behavior that I want to achieve with on of
 the Target that fires prior to Compile.  I know about Input and Output and I
 assume that they need to be set to something but I am not clear on how to
 define the Input group (which already exists obviously).

 A related but different question is that the MSBuild property Cultures is a
 list of all cultures to build.  After linking is there a property that can
 detect in Target AfterCompileAndLink which indicates the specific culture
 that was just built?

 --
 View this message in context: 
 http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/MSBuild-wix-project-file-how-to-detect-skipped-and-specific-culture-tp7588418.html
 Sent from the wix-users mailing list archive at Nabble.com.

 --
 Introducing Performance Central, a new site from SourceForge and 
 AppDynamics. Performance Central is your source for news, insights, 
 analysis and resources for efficient Application Performance Management. 
 Visit us today!
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Fallback when not getting admin rights

2013-08-27 Thread Trond Andersen

Thank you for your feeback.
 I forget what the DropBox install experience was, but when I look at
 those shell extensions they are all in HKCU, so they are per-user and
 not per-system. That might work for you too.

I run Regshot on my computer and looked at the changes in registry. A lot
of the changes are in HKU, but there are quite a few changes in HKLM as
shown below.

We are currently using regasm to get our shell extension registered. Is it
possible to avoid using regasm for shell extension registration? Any
pointers to how this can be achieved? Currently we are using custom tasks
for this. Here is an example on how we do it:

CustomAction Id=CA.CmdLine.RegisterShellExt Property=QtExecCmdLine
  Value='[NETFRAMEWORK40CLIENTINSTALLROOTDIR64]RegAsm.exe
/codebase [INSTALLLOCATION]$(var.SE.TargetFileName)' /
CustomAction Id=CA.RegisterShellExt BinaryKey='WixCA'
DllEntry='CAQuietExec' Execute='immediate' Return='check' /

Overview of registry changes while Dropbox installer was run:

Keys added:
HKLM\SOFTWARE\Microsoft\Windows Media Player
NSS\3.0\Events\{7F6A42D2-D502-47C2-A2D4-A5A62B1226B7}
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\ShellIconOverlayIdentifiers\DropboxExt1
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\ShellIconOverlayIdentifiers\DropboxExt2
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\ShellIconOverlayIdentifiers\DropboxExt3

The first one probably doesn't matter for us, but we also will need icon
overlay.

Values added:
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\ShellIconOverlayIdentifiers\DropboxExt1\:
{FB314ED9-A251-47B7-93E1-CDD82E34AF8B}
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\ShellIconOverlayIdentifiers\DropboxExt2\:
{FB314EDA-A251-47B7-93E1-CDD82E34AF8B}
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\ShellIconOverlayIdentifiers\DropboxExt3\:
{FB314EDB-A251-47B7-93E1-CDD82E34AF8B}
HKLM\SYSTEM\ControlSet001\Control\Session
Manager\PendingFileRenameOperations:  ...
HKLM\SYSTEM\ControlSet001\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules\{7D6075E4-64CB-4AED-80A3-6DF08642ABE8}:
v2.10|Action=Allow|Active=TRUE|Dir=In|Protocol=6|Profile=Private|App=C:\Users\Tester\AppData\Roaming\Dropbox\bin\Dropbox.exe|Name=Dropbox|
HKLM\SYSTEM\ControlSet001\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules\{D72FE29F-B264-46D2-A8E0-FFCADCF3E83F}:
v2.10|Action=Allow|Active=TRUE|Dir=In|Protocol=17|Profile=Private|App=C:\Users\Tester\AppData\Roaming\Dropbox\bin\Dropbox.exe|Name=Dropbox|
HKLM\SYSTEM\CurrentControlSet\Control\Session
Manager\PendingFileRenameOperations: ...
HKLM\SYSTEM\CurrentControlSet\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules\{7D6075E4-64CB-4AED-80A3-6DF08642ABE8}:
v2.10|Action=Allow|Active=TRUE|Dir=In|Protocol=6|Profile=Private|App=C:\Users\Tester\AppData\Roaming\Dropbox\bin\Dropbox.exe|Name=Dropbox|
HKLM\SYSTEM\CurrentControlSet\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules\{D72FE29F-B264-46D2-A8E0-FFCADCF3E83F}:
v2.10|Action=Allow|Active=TRUE|Dir=In|Protocol=17|Profile=Private|App=C:\Users\Tester\AppData\Roaming\Dropbox\bin\Dropbox.exe|Name=Dropbox|


Not sure how many of these would be applicable for us. Firewall rules -
probably not.


Values modified:
HKLM\SOFTWARE\Microsoft\Reliability Analysis\RAC\WmiLastTime:  75 A0 B5 46
5E A2 CE 01
HKLM\SOFTWARE\Microsoft\Reliability Analysis\RAC\WmiLastTime:  C7 D0 DD 4D
01 A3 CE 01
HKLM\SOFTWARE\Microsoft\SystemCertificates\AuthRoot\AutoUpdate\DisallowedCertLastSyncTime:
 38 1D 55 ED 36 A2 CE 01
HKLM\SOFTWARE\Microsoft\SystemCertificates\AuthRoot\AutoUpdate\DisallowedCertLastSyncTime:
 25 93 69 47 01 A3 CE 01
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009\Counter:  

There were some others in HKLM, but I don't think the Dropbox installer is
responsible for these changes.
--
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Fallback when not getting admin rights

My understanding is that Heat should produce the same result (on a clean 
machine) that regasm produces (unless the binary is 64-bit only or if it is an 
EXE instead of a DLL). If the machine heat is running on already had the binary 
registered then most of the time it won't work (you have to unregister 
everything you intend to harvest before you run the harvester, at minimum).
 Date: Tue, 27 Aug 2013 12:01:35 +0200
 From: trond.ander...@gmail.com
 To: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] Fallback when not getting admin rights

 Thank you for your feeback.
  I forget what the DropBox install experience was, but when I look at
  those shell extensions they are all in HKCU, so they are per-user and
  not per-system. That might work for you too.

 I run Regshot on my computer and looked at the changes in registry. A lot
 of the changes are in HKU, but there are quite a few changes in HKLM as
 shown below.

 We are currently using regasm to get our shell extension registered. Is it
 possible to avoid using regasm for shell extension registration? Any
 pointers to how this can be achieved? Currently we are using custom tasks
 for this. Here is an example on how we do it:

 CustomAction Id=CA.CmdLine.RegisterShellExt Property=QtExecCmdLine
   Value='[NETFRAMEWORK40CLIENTINSTALLROOTDIR64]RegAsm.exe
 /codebase [INSTALLLOCATION]$(var.SE.TargetFileName)' /
 CustomAction Id=CA.RegisterShellExt BinaryKey='WixCA'
 DllEntry='CAQuietExec' Execute='immediate' Return='check' /

 Overview of registry changes while Dropbox installer was run:

 Keys added:
 HKLM\SOFTWARE\Microsoft\Windows Media Player
 NSS\3.0\Events\{7F6A42D2-D502-47C2-A2D4-A5A62B1226B7}
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\ShellIconOverlayIdentifiers\DropboxExt1
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\ShellIconOverlayIdentifiers\DropboxExt2
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\ShellIconOverlayIdentifiers\DropboxExt3

 The first one probably doesn't matter for us, but we also will need icon
 overlay.

 Values added:
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\ShellIconOverlayIdentifiers\DropboxExt1\:
 {FB314ED9-A251-47B7-93E1-CDD82E34AF8B}
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\ShellIconOverlayIdentifiers\DropboxExt2\:
 {FB314EDA-A251-47B7-93E1-CDD82E34AF8B}
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\explorer\ShellIconOverlayIdentifiers\DropboxExt3\:
 {FB314EDB-A251-47B7-93E1-CDD82E34AF8B}
 HKLM\SYSTEM\ControlSet001\Control\Session
 Manager\PendingFileRenameOperations:  ...
 HKLM\SYSTEM\ControlSet001\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules\{7D6075E4-64CB-4AED-80A3-6DF08642ABE8}:
 v2.10|Action=Allow|Active=TRUE|Dir=In|Protocol=6|Profile=Private|App=C:\Users\Tester\AppData\Roaming\Dropbox\bin\Dropbox.exe|Name=Dropbox|
 HKLM\SYSTEM\ControlSet001\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules\{D72FE29F-B264-46D2-A8E0-FFCADCF3E83F}:
 v2.10|Action=Allow|Active=TRUE|Dir=In|Protocol=17|Profile=Private|App=C:\Users\Tester\AppData\Roaming\Dropbox\bin\Dropbox.exe|Name=Dropbox|
 HKLM\SYSTEM\CurrentControlSet\Control\Session
 Manager\PendingFileRenameOperations: ...
 HKLM\SYSTEM\CurrentControlSet\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules\{7D6075E4-64CB-4AED-80A3-6DF08642ABE8}:
 v2.10|Action=Allow|Active=TRUE|Dir=In|Protocol=6|Profile=Private|App=C:\Users\Tester\AppData\Roaming\Dropbox\bin\Dropbox.exe|Name=Dropbox|
 HKLM\SYSTEM\CurrentControlSet\services\SharedAccess\Parameters\FirewallPolicy\FirewallRules\{D72FE29F-B264-46D2-A8E0-FFCADCF3E83F}:
 v2.10|Action=Allow|Active=TRUE|Dir=In|Protocol=17|Profile=Private|App=C:\Users\Tester\AppData\Roaming\Dropbox\bin\Dropbox.exe|Name=Dropbox|

 Not sure how many of these would be applicable for us. Firewall rules -
 probably not.

 Values modified:
 HKLM\SOFTWARE\Microsoft\Reliability Analysis\RAC\WmiLastTime:  75 A0 B5 46
 5E A2 CE 01
 HKLM\SOFTWARE\Microsoft\Reliability Analysis\RAC\WmiLastTime:  C7 D0 DD 4D
 01 A3 CE 01
 HKLM\SOFTWARE\Microsoft\SystemCertificates\AuthRoot\AutoUpdate\DisallowedCertLastSyncTime:
  38 1D 55 ED 36 A2 CE 01
 HKLM\SOFTWARE\Microsoft\SystemCertificates\AuthRoot\AutoUpdate\DisallowedCertLastSyncTime:
  25 93 69 47 01 A3 CE 01
 HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009\Counter:  

 There were some others in HKLM, but I don't think the Dropbox installer is
 responsible for these changes.
 --
 Introducing Performance Central, a new site from SourceForge and 
 AppDynamics. Performance Central is your source for news, insights, 
 analysis and resources for efficient Application Performance Management. 
 Visit us today!
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk

Re: [WiX-users] [Wix]: Conditional installation for Windows Server 2008/Windows Server 2012

2013-08-27 Thread dileep s

Hi Blair,

Thank you for the information.

I am checking windows version to install the MSI/EXE file.

Ex: In my code, I have used for Windows XP 32 bit,
Condition ![CDATA[Installed OR (VersionNT = 501)]] /Condition

So, installer will installs only Windows XP 32 bit machine.

Same like, I have to create windows Installer for Windows Server 2008 and
Windows Server 2012.

How can I differentiate Windows server 2008 and Windows Vista as they have
same VersionNT values.

Regards,
Dileep



On Tue, Aug 27, 2013 at 3:19 PM, Blair Murri os...@live.com wrote:

 I'm not understanding your request. VersionNT is a property indicating the
 platform version of windows, expressed (in the case of MSI) as an integer.
 If you tell us what you are trying to do with VersionNT and what you want
 your package to do between different platforms, we could help more. An
 example of your current non-working code would help as well.

  Date: Tue, 27 Aug 2013 12:49:10 +0530
  From: dileep.sanamp...@gmail.com
  To: wix-users@lists.sourceforge.net
  Subject: [WiX-users] [Wix]: Conditional installation for Windows Server
 2008/Windows Server 2012
 
  Hi All,
 
  I have created MSI/EXE using Wix based on OS (Operating System).
 
  Used VersionNT property values for creating MSI/EXE.
 
  Installation is not working for Windows Server 2008/Windows Server 2012.
 
  How can I check the conditional installation for Windows Server
  2008/Windows Server 2012.
 
  Please help me to solve this...
 
 --
  Introducing Performance Central, a new site from SourceForge and
  AppDynamics. Performance Central is your source for news, insights,
  analysis and resources for efficient Application Performance Management.
  Visit us today!
 
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
  ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users


 --
 Introducing Performance Central, a new site from SourceForge and
 AppDynamics. Performance Central is your source for news, insights,
 analysis and resources for efficient Application Performance Management.
 Visit us today!
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] [Wix]: Copy INI file to WINDOWS folder before 'InstallFiles' action.

2013-08-27 Thread dileep s

I have Config.ini file which is having Model Information.

If this Config.ini file is existing in Windows folder before running MSI
file, I can able to read Model information in INI file.

Is there any way to copy INI file and read that while installing MSI.

Regards,
Dileep



On Tue, Aug 27, 2013 at 12:49 AM, Phil Wilson phildgwil...@gmail.comwrote:

 This is what I don't understand. You said the ini file is packaged in the
 MSI file, therefore you know what this model thing is (in the ini file)
 when you build the MSI file. Why bother to try to find it at install time?

 Even it's awkward in your build for some reason, a post build step could
 extract and add it as a property in the MSI file. There's no point in
 creating an unreliable solution at install time when you can do this
 at build time.

 Phil Wilson


 On Mon, Aug 26, 2013 at 11:27 AM, Blair Murri os...@live.com wrote:

  You read it during InstallFiles? How?
 
   Date: Mon, 26 Aug 2013 16:37:12 +0530
   From: dileep.sanamp...@gmail.com
   To: wix-users@lists.sourceforge.net
   Subject: Re: [WiX-users] [Wix]: Copy INI file to WINDOWS folder before
  'InstallFiles' action.
  
   Hi Blair,
  
   I should copy the INI file in C:\Windows folder before 'InstallFiles'
   action.
   I have to read that INI file information and needs to be set Property
   values for Modelname.
  
   Thanks...
  
  
   On Mon, Aug 26, 2013 at 4:08 PM, Blair Murri os...@live.com wrote:
  
It would be much easier to copy it to C:\Windows folder either as
 part
  of
InstallFiles or right after InstallFiles action. Copying it there
  before
InstallFiles is a fair bit of work.
What are you trying to do? Maybe we can help you with that.
   
 Date: Mon, 26 Aug 2013 12:54:05 +0530
 From: dileep.sanamp...@gmail.com
 To: wix-users@lists.sourceforge.net
 Subject: [WiX-users] [Wix]: Copy INI file to WINDOWS folder before
 'InstallFiles' action.

 Hi All,

 How to copy INI file in C:\Windows folder using Wix created MSI
 file?

 INI file is packaged in MSI.

 Before InstallFiles action in MSI, This INI file should copy in
C:\Windows
 folder.

 Please help me to solve this.

   
 
 --
 Introducing Performance Central, a new site from SourceForge and
 AppDynamics. Performance Central is your source for news, insights,
 analysis and resources for efficient Application Performance
  Management.
 Visit us today!

   
 
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
   
   
   
 
 --
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance
  Management.
Visit us today!
   
 
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
   
  
 
 --
   Introducing Performance Central, a new site from SourceForge and
   AppDynamics. Performance Central is your source for news, insights,
   analysis and resources for efficient Application Performance
 Management.
   Visit us today!
  
 
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
   ___
   WiX-users mailing list
   WiX-users@lists.sourceforge.net
   https://lists.sourceforge.net/lists/listinfo/wix-users
 
 
 
 --
  Introducing Performance Central, a new site from SourceForge and
  AppDynamics. Performance Central is your source for news, insights,
  analysis and resources for efficient Application Performance Management.
  Visit us today!
 
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
  ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users
 

 --
 Introducing Performance Central, a new site from SourceForge and
 AppDynamics. Performance Central is your source for news, insights,
 analysis and resources for efficient Application Performance Management.
 Visit us today!
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
 ___
 WiX-users mailing

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

Good question. I'm not sure exactly, but here’s some code snippets that what 
I'm guessing are UI-related:

Wix 
xmlns='http://schemas.microsoft.com/wix/2006/wi'
xmlns:bal=http://schemas.microsoft.com/wix/BalExtension;
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;

...
BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.RtfLicense 
bal:WixStandardBootstrapperApplication
LicenseFile=License.rtf
LogoFile=lib\Logo_64x64.png
SuppressOptionsUI=yes
ThemeFile=RtfTheme-Custom.xml
/
/BootstrapperApplicationRef

Obviously, we are using a custom theme (RtfTheme-Custom.xml), but it's almost 
identical to the original src\ext\BalExtension\wixstdba\Resources\RtfTheme.xml 
. 


-Original Message-
From: Blair Murri [mailto:os...@live.com] 
Sent: Tuesday, August 27, 2013 05:51
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Add text to final window in burn bootstrapper/installer

Which UI are you using in your bundle?

 From: afor...@cmu.edu
 To: wix-users@lists.sourceforge.net
 Date: Mon, 26 Aug 2013 18:55:39 -0400
 Subject: [WiX-users] Add text to final window in burn bootstrapper/installer
 
 Hi all,
 
 Our installer bundled with burn currently posts a simple Setup Complete 
 message when the install is done. How can we add additional text on this last 
 window when the install is complete?
 
 Thanks,
 Alain
 
 
 --
 Introducing Performance Central, a new site from SourceForge and 
 AppDynamics. Performance Central is your source for news, insights, 
 analysis and resources for efficient Application Performance Management. 
 Visit us today!
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
  
--
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] [Wix]: Conditional installation for Windows Server 2008/Windows Server 2012

2013-08-27 Thread Porterfield, Tom

http://robmensching.com/blog/posts/2008/11/3/how-to-determine-if-you-are-installing-on-windows-client

should help.

Tom Porterfield
-Original Message-
From: dileep s [mailto:dileep.sanamp...@gmail.com] 
Sent: Tuesday, August 27, 2013 6:51 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] [Wix]: Conditional installation for Windows Server 
2008/Windows Server 2012

Hi Blair,

Thank you for the information.

I am checking windows version to install the MSI/EXE file.

Ex: In my code, I have used for Windows XP 32 bit,
Condition ![CDATA[Installed OR (VersionNT = 501)]] /Condition

So, installer will installs only Windows XP 32 bit machine.

Same like, I have to create windows Installer for Windows Server 2008 and
Windows Server 2012.

How can I differentiate Windows server 2008 and Windows Vista as they have
same VersionNT values.

Regards,
Dileep

On Tue, Aug 27, 2013 at 3:19 PM, Blair Murri os...@live.com wrote:

 I'm not understanding your request. VersionNT is a property indicating the
 platform version of windows, expressed (in the case of MSI) as an integer.
 If you tell us what you are trying to do with VersionNT and what you want
 your package to do between different platforms, we could help more. An
 example of your current non-working code would help as well.

  Date: Tue, 27 Aug 2013 12:49:10 +0530
  From: dileep.sanamp...@gmail.com
  To: wix-users@lists.sourceforge.net
  Subject: [WiX-users] [Wix]: Conditional installation for Windows Server
 2008/Windows Server 2012

  Hi All,

  I have created MSI/EXE using Wix based on OS (Operating System).

  Used VersionNT property values for creating MSI/EXE.

  Installation is not working for Windows Server 2008/Windows Server 2012.

  How can I check the conditional installation for Windows Server
  2008/Windows Server 2012.

  Please help me to solve this...

 --
  Introducing Performance Central, a new site from SourceForge and
  AppDynamics. Performance Central is your source for news, insights,
  analysis and resources for efficient Application Performance Management.
  Visit us today!

 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
  ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users

 --
 Introducing Performance Central, a new site from SourceForge and
 AppDynamics. Performance Central is your source for news, insights,
 analysis and resources for efficient Application Performance Management.
 Visit us today!
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Question about $(Platform) in Votive Output name

2013-08-27 Thread moc

This still seems to be the case in 3.7.1224.0
I'd like to be able to use MSBuild variables in the output name as
everything else works with my current project expect this. Currently I
either have to duplicate my project wixproj file and 'hard code' the name in
the UI or bypass the UI and edit the xml myself. I'd like to use the votive
UI! (I realize it's a minor issue as there is a workaround, but it's
confusing for a wixproj/votive newbie).
Thanks
Matt




--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Question-about-Platform-in-Votive-Output-name-tp709453p7588469.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Custom element

2013-08-27 Thread Rob Mensching

It'd be great if you could contribute what you learned or maybe go in and
understand how the documentation is created for the WiX toolset to help
enhance it. The guys on wix-devs mailing list are very supportive of people
wanting to help improve.

Feature suggestions here are welcome but I always like to remind people
that to really make features a reality, we'll need contributors. smile/


On Tue, Aug 27, 2013 at 12:28 AM, Lars Lars laasu...@hotmail.com wrote:

 Hello,

 Reading the
 http://wixtoolset.org/documentation/manual/v3/xsd/wix/custom.html docs.
 Would it be possible to specify the legal values for attribute before and
 after, and inner value?

 Using google I found the state 'InstallInitialize' and 'InstallFinalize'
 which solved two issues. However it would be nice if the docs could have
 told me. I guess there might be other states aswell.

 For the inner text I used NOT Installed and Installed, again based on
 google. In this case I am more confussed as to how it works. How does the
 installer know if something is installer or not? What other options do I
 have? What happens if I enter no inner text?

 Sorry for all the questions. Just thought I would give a feedback.

 Regards, Lars


 --
 Introducing Performance Central, a new site from SourceForge and
 AppDynamics. Performance Central is your source for news, insights,
 analysis and resources for efficient Application Performance Management.
 Visit us today!
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] 64 bit version of MS build cannot find the WIX toolset

I know there is probably a posting somewhere out on the web describing the 
issue I am having, but I am not able to find it at the present moment.

The problem I am current having is that the 64 bit version of MS build does not 
properly evaluate the build variables and is not able to find WIX tools.  The 
32 bit version works correctly and everything is happy, but when I switch MS  
Build targets everything goes to pot.

Does anyone have a way around this issue or a link to the documentation on why 
I am seeing this?  

Thank you in advance,

Mat Skildum

--
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] [Wix]: Copy INI file to WINDOWS folder before 'InstallFiles' action.

If the INI file is in your MSI, whatever is in that INI file could be added to 
your MSI when your MSI is built, right? If not, please explain why not.
If the INI file is not in the MSI, how does your MSI know where the INI file is 
in order to copy it to the Windows folder? Could that action in your MSI just 
read the INI file in place instead of having to read it from C:\Windows?
And, exactly when do you have what kind (immediate, deferred) of custom action 
scheduled in your InstallExecuteSequence that actually reads that information? 
That is critical to telling you how to get your file there at the right time.

 Date: Tue, 27 Aug 2013 17:13:26 +0530
 From: dileep.sanamp...@gmail.com
 To: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] [Wix]: Copy INI file to WINDOWS folder before 
 'InstallFiles' action.
 
 I have Config.ini file which is having Model Information.
 
 If this Config.ini file is existing in Windows folder before running MSI
 file, I can able to read Model information in INI file.
 
 Is there any way to copy INI file and read that while installing MSI.
 
 Regards,
 Dileep
 
 
 
 On Tue, Aug 27, 2013 at 12:49 AM, Phil Wilson phildgwil...@gmail.comwrote:
 
  This is what I don't understand. You said the ini file is packaged in the
  MSI file, therefore you know what this model thing is (in the ini file)
  when you build the MSI file. Why bother to try to find it at install time?
 
  Even it's awkward in your build for some reason, a post build step could
  extract and add it as a property in the MSI file. There's no point in
  creating an unreliable solution at install time when you can do this
  at build time.
 
  Phil Wilson
 
 
  On Mon, Aug 26, 2013 at 11:27 AM, Blair Murri os...@live.com wrote:
 
   You read it during InstallFiles? How?
  
Date: Mon, 26 Aug 2013 16:37:12 +0530
From: dileep.sanamp...@gmail.com
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] [Wix]: Copy INI file to WINDOWS folder before
   'InstallFiles' action.
   
Hi Blair,
   
I should copy the INI file in C:\Windows folder before 'InstallFiles'
action.
I have to read that INI file information and needs to be set Property
values for Modelname.
   
Thanks...
   
   
On Mon, Aug 26, 2013 at 4:08 PM, Blair Murri os...@live.com wrote:
   
 It would be much easier to copy it to C:\Windows folder either as
  part
   of
 InstallFiles or right after InstallFiles action. Copying it there
   before
 InstallFiles is a fair bit of work.
 What are you trying to do? Maybe we can help you with that.

  Date: Mon, 26 Aug 2013 12:54:05 +0530
  From: dileep.sanamp...@gmail.com
  To: wix-users@lists.sourceforge.net
  Subject: [WiX-users] [Wix]: Copy INI file to WINDOWS folder before
  'InstallFiles' action.
 
  Hi All,
 
  How to copy INI file in C:\Windows folder using Wix created MSI
  file?
 
  INI file is packaged in MSI.
 
  Before InstallFiles action in MSI, This INI file should copy in
 C:\Windows
  folder.
 
  Please help me to solve this.
 

  
  --
  Introducing Performance Central, a new site from SourceForge and
  AppDynamics. Performance Central is your source for news, insights,
  analysis and resources for efficient Application Performance
   Management.
  Visit us today!
 

  
  http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
  ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users



  
  --
 Introducing Performance Central, a new site from SourceForge and
 AppDynamics. Performance Central is your source for news, insights,
 analysis and resources for efficient Application Performance
   Management.
 Visit us today!

  
  http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

   
  
  --
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance
  Management.
Visit us today!
   
  
  http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Question about $(Platform) in Votive Output name

Please file a feature request. Even better, contributing a fix would be much
appreciated.

Date: Tue, 27 Aug 2013 07:18:38 -0700
From: techsupport...@gmail.com
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Question about $(Platform) in Votive Output name

This still seems to be the case in 3.7.1224.0
I'd like to be able to use MSBuild variables in the output name as
everything else works with my current project expect this. Currently I
either have to duplicate my project wixproj file and 'hard code' the name in
the UI or bypass the UI and edit the xml myself. I'd like to use the votive
UI! (I realize it's a minor issue as there is a workaround, but it's
confusing for a wixproj/votive newbie).
Thanks
Matt

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Question-about-Platform-in-Votive-Output-name-tp709453p7588469.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance Management.
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

Which version of WiX are you running? There was a bug a ways back about that.
 From: mathew.skil...@aspect.com
 To: wix-users@lists.sourceforge.net
 Date: Tue, 27 Aug 2013 14:54:30 +
 Subject: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

 I know there is probably a posting somewhere out on the web describing the 
 issue I am having, but I am not able to find it at the present moment.

 The problem I am current having is that the 64 bit version of MS build does 
 not properly evaluate the build variables and is not able to find WIX tools.  
 The 32 bit version works correctly and everything is happy, but when I switch 
 MS  Build targets everything goes to pot.

 Does anyone have a way around this issue or a link to the documentation on 
 why I am seeing this?  

 Thank you in advance,

 Mat Skildum

 --
 Introducing Performance Central, a new site from SourceForge and 
 AppDynamics. Performance Central is your source for news, insights, 
 analysis and resources for efficient Application Performance Management. 
 Visit us today!
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

I am using WIX 3.8 (build 3.8.708).  The build system is using the GA version 
of WIX 3.7.

I am havine issues on both systems.

-Original Message-
From: Blair Murri [mailto:os...@live.com] 
Sent: Tuesday, August 27, 2013 10:37 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

Which version of WiX are you running? There was a bug a ways back about that.
 From: mathew.skil...@aspect.com
 To: wix-users@lists.sourceforge.net
 Date: Tue, 27 Aug 2013 14:54:30 +
 Subject: [WiX-users] 64 bit version of MS build cannot find the WIX 
 toolset

 I know there is probably a posting somewhere out on the web describing the 
 issue I am having, but I am not able to find it at the present moment.

 The problem I am current having is that the 64 bit version of MS build does 
 not properly evaluate the build variables and is not able to find WIX tools.  
 The 32 bit version works correctly and everything is happy, but when I switch 
 MS  Build targets everything goes to pot.

 Does anyone have a way around this issue or a link to the documentation on 
 why I am seeing this?  

 Thank you in advance,

 Mat Skildum

 --
  Introducing Performance Central, a new site from SourceForge 
 and AppDynamics. Performance Central is your source for news, 
 insights, analysis and resources for efficient Application Performance 
 Management.
 Visit us today!
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.c
 lktrk ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
Introducing Performance Central, a new site from SourceForge and AppDynamics. 
Performance Central is your source for news, insights, analysis and resources 
for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

How far back do you wixproj files go?  Modern ones should have something like:

lt;WixTargetsPath Condition= '$(WixTargetsPath)' == '' AND 
'$(MSBuildExtensionsPath32)' != '' 
gt;$(MSBuildExtensionsPath32)\Microsoft\WiX\v3.x\Wix.targetslt;/WixTargetsPathgt;
lt;WixTargetsPath Condition= '$(WixTargetsPath)' == '' 
gt;$(MSBuildExtensionsPath)\Microsoft\WiX\v3.x\Wix.targetslt;/WixTargetsPathgt;

Older files don't have both lines causing things to fail on x64 systems.

--
John Merryweather Cooper
Build  Install Engineer -- ESA
Jack Henry  Associates, Inc.(r)
Shawnee Mission, KS  66227
Office:  913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com




-Original Message-
From: Skildum, Mathew [mailto:mathew.skil...@aspect.com] 
Sent: Tuesday, August 27, 2013 10:44 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

I am using WIX 3.8 (build 3.8.708).  The build system is using the GA version 
of WIX 3.7.

I am havine issues on both systems.

-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: Tuesday, August 27, 2013 10:37 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

Which version of WiX are you running? There was a bug a ways back about that.
 From: mathew.skil...@aspect.com
 To: wix-users@lists.sourceforge.net
 Date: Tue, 27 Aug 2013 14:54:30 +
 Subject: [WiX-users] 64 bit version of MS build cannot find the WIX 
 toolset
 
 I know there is probably a posting somewhere out on the web describing the 
 issue I am having, but I am not able to find it at the present moment.
 
 The problem I am current having is that the 64 bit version of MS build does 
 not properly evaluate the build variables and is not able to find WIX tools.  
 The 32 bit version works correctly and everything is happy, but when I switch 
 MS  Build targets everything goes to pot.
 
 Does anyone have a way around this issue or a link to the documentation on 
 why I am seeing this?  
 
 Thank you in advance,
 
 Mat Skildum
 
 --
  Introducing Performance Central, a new site from SourceForge 
 and AppDynamics. Performance Central is your source for news, 
 insights, analysis and resources for efficient Application Performance 
 Management.
 Visit us today!
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.c
 lktrk ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
  
--
Introducing Performance Central, a new site from SourceForge and AppDynamics. 
Performance Central is your source for news, insights, analysis and resources 
for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Introducing Performance Central, a new site from SourceForge and AppDynamics. 
Performance Central is your source for news, insights, analysis and resources 
for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are 
intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged 
information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.


--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

All  of the WIX projects in question have those lines in place:

WixTargetsPath Condition= '$(WixTargetsPath)' == '' AND 
'$(MSBuildExtensionsPath32)' != '' 
$(MSBuildExtensionsPath32)\Microsoft\WiX\v3.x\Wix.targets/WixTargetsPath
WixTargetsPath Condition= '$(WixTargetsPath)' == '' 
$(MSBuildExtensionsPath)\Microsoft\WiX\v3.x\Wix.targets/WixTargetsPath

I just realized that forgot to mention I was using the .Net 4.0 version of MS 
Build.

MAT SKILDUM
SR PRINCIPAL ENGINEER
+1 (630) 227.8534 WORK
+1 (847) 909.9921 MOBILE
mathew.skil...@aspect.com
aspect.com




-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com] 
Sent: Tuesday, August 27, 2013 11:05 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

How far back do you wixproj files go?  Modern ones should have something like:

lt;WixTargetsPath Condition= '$(WixTargetsPath)' == '' AND 
'$(MSBuildExtensionsPath32)' != '' 
gt;$(MSBuildExtensionsPath32)\Microsoft\WiX\v3.x\Wix.targetslt;/WixTargetsPathgt;
lt;WixTargetsPath Condition= '$(WixTargetsPath)' == '' 
gt;$(MSBuildExtensionsPath)\Microsoft\WiX\v3.x\Wix.targetslt;/WixTargetsPathgt;

Older files don't have both lines causing things to fail on x64 systems.

--
John Merryweather Cooper
Build  Install Engineer -- ESA
Jack Henry  Associates, Inc.(r)
Shawnee Mission, KS  66227
Office:  913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com




-Original Message-
From: Skildum, Mathew [mailto:mathew.skil...@aspect.com]
Sent: Tuesday, August 27, 2013 10:44 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

I am using WIX 3.8 (build 3.8.708).  The build system is using the GA version 
of WIX 3.7.

I am havine issues on both systems.

-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: Tuesday, August 27, 2013 10:37 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

Which version of WiX are you running? There was a bug a ways back about that.
 From: mathew.skil...@aspect.com
 To: wix-users@lists.sourceforge.net
 Date: Tue, 27 Aug 2013 14:54:30 +
 Subject: [WiX-users] 64 bit version of MS build cannot find the WIX 
 toolset
 
 I know there is probably a posting somewhere out on the web describing the 
 issue I am having, but I am not able to find it at the present moment.
 
 The problem I am current having is that the 64 bit version of MS build does 
 not properly evaluate the build variables and is not able to find WIX tools.  
 The 32 bit version works correctly and everything is happy, but when I switch 
 MS  Build targets everything goes to pot.
 
 Does anyone have a way around this issue or a link to the documentation on 
 why I am seeing this?  
 
 Thank you in advance,
 
 Mat Skildum
 
 --
  Introducing Performance Central, a new site from SourceForge 
 and AppDynamics. Performance Central is your source for news, 
 insights, analysis and resources for efficient Application Performance 
 Management.
 Visit us today!
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.c
 lktrk ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
  
--
Introducing Performance Central, a new site from SourceForge and AppDynamics. 
Performance Central is your source for news, insights, analysis and resources 
for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Introducing Performance Central, a new site from SourceForge and AppDynamics. 
Performance Central is your source for news, insights, analysis and resources 
for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are 
intended exclusively for the individual or entity to which it is addressed. The 
message, together with any attachment, may contain confidential and/or 
privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution is strictly

Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

MSBuild 4.0 x64 uses the 32-bit path for both $(MSBuildExtensionsPath32) and 
$(MSBuildExtensionsPath), so it should be picking up the right file.
What are the specific errors you are getting?

 From: mathew.skil...@aspect.com
 To: wix-users@lists.sourceforge.net
 Date: Tue, 27 Aug 2013 16:38:03 +
 Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX 
 toolset
 
 All  of the WIX projects in question have those lines in place:
 
 WixTargetsPath Condition= '$(WixTargetsPath)' == '' AND 
 '$(MSBuildExtensionsPath32)' != '' 
 $(MSBuildExtensionsPath32)\Microsoft\WiX\v3.x\Wix.targets/WixTargetsPath
 WixTargetsPath Condition= '$(WixTargetsPath)' == '' 
 $(MSBuildExtensionsPath)\Microsoft\WiX\v3.x\Wix.targets/WixTargetsPath
 
 I just realized that forgot to mention I was using the .Net 4.0 version of MS 
 Build.
 
 MAT SKILDUM
 SR PRINCIPAL ENGINEER
 +1 (630) 227.8534 WORK
 +1 (847) 909.9921 MOBILE
 mathew.skil...@aspect.com
 aspect.com
 
 
 
 
 -Original Message-
 From: John Cooper [mailto:jocoo...@jackhenry.com] 
 Sent: Tuesday, August 27, 2013 11:05 AM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX 
 toolset
 
 How far back do you wixproj files go?  Modern ones should have something like:
 
 lt;WixTargetsPath Condition= '$(WixTargetsPath)' == '' AND 
 '$(MSBuildExtensionsPath32)' != '' 
 gt;$(MSBuildExtensionsPath32)\Microsoft\WiX\v3.x\Wix.targetslt;/WixTargetsPathgt;
 lt;WixTargetsPath Condition= '$(WixTargetsPath)' == '' 
 gt;$(MSBuildExtensionsPath)\Microsoft\WiX\v3.x\Wix.targetslt;/WixTargetsPathgt;
 
 Older files don't have both lines causing things to fail on x64 systems.
 
 --
 John Merryweather Cooper
 Build  Install Engineer -- ESA
 Jack Henry  Associates, Inc.(r)
 Shawnee Mission, KS  66227
 Office:  913-341-3434 x791011
 jocoo...@jackhenry.com
 www.jackhenry.com
 
 
 
 
 -Original Message-
 From: Skildum, Mathew [mailto:mathew.skil...@aspect.com]
 Sent: Tuesday, August 27, 2013 10:44 AM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX 
 toolset
 
 I am using WIX 3.8 (build 3.8.708).  The build system is using the GA version 
 of WIX 3.7.
 
 I am havine issues on both systems.
 
 -Original Message-
 From: Blair Murri [mailto:os...@live.com]
 Sent: Tuesday, August 27, 2013 10:37 AM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX 
 toolset
 
 Which version of WiX are you running? There was a bug a ways back about that.
  From: mathew.skil...@aspect.com
  To: wix-users@lists.sourceforge.net
  Date: Tue, 27 Aug 2013 14:54:30 +
  Subject: [WiX-users] 64 bit version of MS build cannot find the WIX 
  toolset
  
  I know there is probably a posting somewhere out on the web describing the 
  issue I am having, but I am not able to find it at the present moment.
  
  The problem I am current having is that the 64 bit version of MS build does 
  not properly evaluate the build variables and is not able to find WIX 
  tools.  The 32 bit version works correctly and everything is happy, but 
  when I switch MS  Build targets everything goes to pot.
  
  Does anyone have a way around this issue or a link to the documentation on 
  why I am seeing this?  
  
  Thank you in advance,
  
  Mat Skildum
  
  --
   Introducing Performance Central, a new site from SourceForge 
  and AppDynamics. Performance Central is your source for news, 
  insights, analysis and resources for efficient Application Performance 
  Management.
  Visit us today!
  http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.c
  lktrk ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users
 
 --
 Introducing Performance Central, a new site from SourceForge and AppDynamics. 
 Performance Central is your source for news, insights, analysis and resources 
 for efficient Application Performance Management. 
 Visit us today!
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
 
 --
 Introducing Performance Central, a new site from SourceForge and AppDynamics. 
 Performance Central is your source for news, insights, analysis and resources 
 for efficient Application Performance Management. 
 Visit us today!
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk

Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

Ok.  So the proj files are modern.  What is the path of WiX on the build server 
and how was it installed there?  What is the specific message from the build 
logs?

--
John Merryweather Cooper
Build  Install Engineer -- ESA
Jack Henry  Associates, Inc.(r)
Shawnee Mission, KS  66227
Office:  913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com




-Original Message-
From: Skildum, Mathew [mailto:mathew.skil...@aspect.com] 
Sent: Tuesday, August 27, 2013 11:38 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

All  of the WIX projects in question have those lines in place:

WixTargetsPath Condition= '$(WixTargetsPath)' == '' AND 
'$(MSBuildExtensionsPath32)' != '' 
$(MSBuildExtensionsPath32)\Microsoft\WiX\v3.x\Wix.targets/WixTargetsPath
WixTargetsPath Condition= '$(WixTargetsPath)' == '' 
$(MSBuildExtensionsPath)\Microsoft\WiX\v3.x\Wix.targets/WixTargetsPath

I just realized that forgot to mention I was using the .Net 4.0 version of MS 
Build.

MAT SKILDUM
SR PRINCIPAL ENGINEER
+1 (630) 227.8534 WORK
+1 (847) 909.9921 MOBILE
mathew.skil...@aspect.com
aspect.com




-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Tuesday, August 27, 2013 11:05 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

How far back do you wixproj files go?  Modern ones should have something like:

lt;WixTargetsPath Condition= '$(WixTargetsPath)' == '' AND 
'$(MSBuildExtensionsPath32)' != '' 
gt;$(MSBuildExtensionsPath32)\Microsoft\WiX\v3.x\Wix.targetslt;/WixTargetsPathgt;
lt;WixTargetsPath Condition= '$(WixTargetsPath)' == '' 
gt;$(MSBuildExtensionsPath)\Microsoft\WiX\v3.x\Wix.targetslt;/WixTargetsPathgt;

Older files don't have both lines causing things to fail on x64 systems.

--
John Merryweather Cooper
Build  Install Engineer -- ESA
Jack Henry  Associates, Inc.(r)
Shawnee Mission, KS  66227
Office:  913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com




-Original Message-
From: Skildum, Mathew [mailto:mathew.skil...@aspect.com]
Sent: Tuesday, August 27, 2013 10:44 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

I am using WIX 3.8 (build 3.8.708).  The build system is using the GA version 
of WIX 3.7.

I am havine issues on both systems.

-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: Tuesday, August 27, 2013 10:37 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

Which version of WiX are you running? There was a bug a ways back about that.
 From: mathew.skil...@aspect.com
 To: wix-users@lists.sourceforge.net
 Date: Tue, 27 Aug 2013 14:54:30 +
 Subject: [WiX-users] 64 bit version of MS build cannot find the WIX 
 toolset
 
 I know there is probably a posting somewhere out on the web describing the 
 issue I am having, but I am not able to find it at the present moment.
 
 The problem I am current having is that the 64 bit version of MS build does 
 not properly evaluate the build variables and is not able to find WIX tools.  
 The 32 bit version works correctly and everything is happy, but when I switch 
 MS  Build targets everything goes to pot.
 
 Does anyone have a way around this issue or a link to the documentation on 
 why I am seeing this?  
 
 Thank you in advance,
 
 Mat Skildum
 
 --
  Introducing Performance Central, a new site from SourceForge 
 and AppDynamics. Performance Central is your source for news, 
 insights, analysis and resources for efficient Application Performance 
 Management.
 Visit us today!
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.c
 lktrk ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
  
--
Introducing Performance Central, a new site from SourceForge and AppDynamics. 
Performance Central is your source for news, insights, analysis and resources 
for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Introducing Performance Central, a new site from SourceForge and AppDynamics. 
Performance Central is your source for news, insights, analysis and resources 
for efficient Application

Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

WIX was installed through the released installed and the installation path is 
C:\Program Files (x86)\WiX Toolset v3.7.

Here is an example of the build errors:

  CustomAction.cs(4,17): error CS0234: The type or namespace name 'Deployment'
does not exist in the namespace 'Microsoft' (are you missing an assembly refere
nce?) 
  CustomAction.cs(12,58): error CS0246: The type or namespace name 'Session' co
uld not be found (are you missing a using directive or an assembly reference?)
  CustomAction.cs(12,23): error CS0246: The type or namespace name 'ActionResul
t' could not be found (are you missing a using directive or an assembly referen
ce?) 

Mat Skildum
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com] 
Sent: Tuesday, August 27, 2013 11:55 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

Ok.  So the proj files are modern.  What is the path of WiX on the build server 
and how was it installed there?  What is the specific message from the build 
logs?

--
John Merryweather Cooper
Build  Install Engineer -- ESA
Jack Henry  Associates, Inc.(r)
Shawnee Mission, KS  66227
Office:  913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com




-Original Message-
From: Skildum, Mathew [mailto:mathew.skil...@aspect.com]
Sent: Tuesday, August 27, 2013 11:38 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

All  of the WIX projects in question have those lines in place:

WixTargetsPath Condition= '$(WixTargetsPath)' == '' AND 
'$(MSBuildExtensionsPath32)' != '' 
$(MSBuildExtensionsPath32)\Microsoft\WiX\v3.x\Wix.targets/WixTargetsPath
WixTargetsPath Condition= '$(WixTargetsPath)' == '' 
$(MSBuildExtensionsPath)\Microsoft\WiX\v3.x\Wix.targets/WixTargetsPath

I just realized that forgot to mention I was using the .Net 4.0 version of MS 
Build.

MAT SKILDUM
SR PRINCIPAL ENGINEER
+1 (630) 227.8534 WORK
+1 (847) 909.9921 MOBILE
mathew.skil...@aspect.com
aspect.com




-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Tuesday, August 27, 2013 11:05 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

How far back do you wixproj files go?  Modern ones should have something like:

lt;WixTargetsPath Condition= '$(WixTargetsPath)' == '' AND 
'$(MSBuildExtensionsPath32)' != '' 
gt;$(MSBuildExtensionsPath32)\Microsoft\WiX\v3.x\Wix.targetslt;/WixTargetsPathgt;
lt;WixTargetsPath Condition= '$(WixTargetsPath)' == '' 
gt;$(MSBuildExtensionsPath)\Microsoft\WiX\v3.x\Wix.targetslt;/WixTargetsPathgt;

Older files don't have both lines causing things to fail on x64 systems.

--
John Merryweather Cooper
Build  Install Engineer -- ESA
Jack Henry  Associates, Inc.(r)
Shawnee Mission, KS  66227
Office:  913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com




-Original Message-
From: Skildum, Mathew [mailto:mathew.skil...@aspect.com]
Sent: Tuesday, August 27, 2013 10:44 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

I am using WIX 3.8 (build 3.8.708).  The build system is using the GA version 
of WIX 3.7.

I am havine issues on both systems.

-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: Tuesday, August 27, 2013 10:37 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

Which version of WiX are you running? There was a bug a ways back about that.
 From: mathew.skil...@aspect.com
 To: wix-users@lists.sourceforge.net
 Date: Tue, 27 Aug 2013 14:54:30 +
 Subject: [WiX-users] 64 bit version of MS build cannot find the WIX 
 toolset
 
 I know there is probably a posting somewhere out on the web describing the 
 issue I am having, but I am not able to find it at the present moment.
 
 The problem I am current having is that the 64 bit version of MS build does 
 not properly evaluate the build variables and is not able to find WIX tools.  
 The 32 bit version works correctly and everything is happy, but when I switch 
 MS  Build targets everything goes to pot.
 
 Does anyone have a way around this issue or a link to the documentation on 
 why I am seeing this?  
 
 Thank you in advance,
 
 Mat Skildum
 
 --
  Introducing Performance Central, a new site from SourceForge 
 and AppDynamics. Performance Central is your source for news, 
 insights, analysis and resources for efficient Application Performance 
 Management.
 Visit us today!
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.c
 lktrk ___
 WiX-users mailing list

Re: [WiX-users] RegistrySearch example in tutorial

2013-08-27 Thread Phil Wilson

The original registry search you posted doesn't have Win64=yes so it
will be a 32-bit registry search if you have an x86 platform install (and
it looks like you do).

Phil Wilson


On Tue, Aug 27, 2013 at 2:29 AM, Blair Murri os...@live.com wrote:

 If you are intending to use the 32-bit registry in a 64-bit platform in
 RegEdit, you need to start from the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node
 (which is the 32-bit HKEY_LOCAL_MACHINE\SOFTWARE key).
 You make TARGETDIR conditional by setting a property by that name to the
 full path (hopefully with a backslash ('\') at the end) before costing
 starts in whatever sequence starts first. Same with INSTALLDIR.
 Subdirectories will automatically use the path set for their parents if a
 path is not presupplied. During costing, properties will be created for all
 directories that didn't already have properties (and each one will be set
 to the full path of that directory).
 AppSearch, et. al. will set the property you specify. So will the
 command-line. By default, the *Search actions will override the
 command-line.

  From: rob...@softdev.net
  To: wix-users@lists.sourceforge.net
  Date: Mon, 26 Aug 2013 23:52:18 +
  Subject: Re: [WiX-users] RegistrySearch example in tutorial
 
  Thanks for both replies. I am indeed on a x64 machine and have no idea
 how to distinguish between x86/x64 registries. I've probably created the
 key in the wrong one. Any pointers? To open the editor, I type in regedit
 
  If not that, then how should I make this conditional:
 
Directory Id='TARGETDIR' Name='SourceDir'
  Directory Id='ProgramFilesFolder' Name='PFiles'
Directory Id='Acme' Name='Acme'
  Directory Id='INSTALLDIR' Name='Foobar 1.0'
 
  -Original Message-
  From: Phil Wilson [mailto:phildgwil...@gmail.com]
  Sent: Tuesday, 27 August 2013 4:49 AM
  To: General discussion for Windows Installer XML toolset.
  Subject: Re: [WiX-users] RegistrySearch example in tutorial
 
  What often happens is that there is a custom action to set the default
 INSTALLDIR location to the program files folder, and people forget to make
 it conditional, with a condition like NOT INSTALDIR.  You may find that if
 you set INSTALLDIR on an msiexec command line it would also get
 overwritten. The NOT INSTALLDIR condition just means don't set it to
 default if it's already set.
 
  Phil Wilson
 
 
  On Mon, Aug 26, 2013 at 3:42 AM, Blair Murri os...@live.com wrote:
 
   Adding is not overridding, it is creating.
   That would suggest that there is no InstallDir value at
   HKLM\Software\Acme\Foobar 1.0 Do you have a 32-bit MSI and are trying
   to read a 64-bit registry location, per chance? Or vice versa?
  
From: rob...@softdev.net
To: wix-users@lists.sourceforge.net
Date: Mon, 26 Aug 2013 06:31:51 +
Subject: [WiX-users] RegistrySearch example in tutorial
   
I'm a novice user, going through Getting Started. I cannot get the
   RegistrySearch to work, or FILEEXISTS - both from Where to Install?
   page in your tutorial.
   
I suspect it is because this element:
Property Id=INSTALLDIR
  RegistrySearch Id='AcmeFoobarRegistry' Type='raw' Root='HKLM'
   Key='Software\Acme\Foobar 1.0' Name='InstallDir' /
/Property
   
is overridden by the subsequent
   
Directory Id='TARGETDIR' Name='SourceDir'
  Directory Id='ProgramFilesFolder' Name='PFiles'
Directory Id='Acme' Name='Acme'
  Directory Id='INSTALLDIR' Name='Foobar 1.0'
   
Meaning that if the registry sets a directory outside of program
files,
   then it seems to not work because later in the wxs file it is
   contained within ProgramFilesFolder. Logging reveals it is overridden:
   
MSI (c) (50:AC) [16:21:36:966]: PROPERTY CHANGE: Adding INSTALLDIR
   property. Its value is 'C:\Program Files (x86)\... etc
   
I realise the file is not read sequentially.
   
Regards,
Robert
   
   --
   
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance Central is your source for news, insights,
analysis and resources for efficient Application Performance
 Management.
Visit us today!
   
   http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.c
   lktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
  
  
   --
    Introducing Performance Central, a new site from SourceForge
   and AppDynamics. Performance Central is your source for news,
   insights, analysis and resources for efficient Application Performance
   Management.
   Visit us today!
   http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.c
   lktrk

Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

You have broken references in your custom action project to 
Microsoft.Deployment.WindowsInstaller.dll.  It should be in C:\Program Files 
(x86)\WiX Toolset v3.7\bin\.

--
John Merryweather Cooper
Build  Install Engineer -- ESA
Jack Henry  Associates, Inc.(r)
Shawnee Mission, KS  66227
Office:  913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com




-Original Message-
From: Skildum, Mathew [mailto:mathew.skil...@aspect.com] 
Sent: Tuesday, August 27, 2013 12:05 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

WIX was installed through the released installed and the installation path is 
C:\Program Files (x86)\WiX Toolset v3.7.

Here is an example of the build errors:

  CustomAction.cs(4,17): error CS0234: The type or namespace name 'Deployment'
does not exist in the namespace 'Microsoft' (are you missing an assembly refere
nce?)
  CustomAction.cs(12,58): error CS0246: The type or namespace name 'Session' co 
uld not be found (are you missing a using directive or an assembly reference?)
  CustomAction.cs(12,23): error CS0246: The type or namespace name 'ActionResul 
t' could not be found (are you missing a using directive or an assembly referen
ce?) 

Mat Skildum
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Tuesday, August 27, 2013 11:55 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

Ok.  So the proj files are modern.  What is the path of WiX on the build server 
and how was it installed there?  What is the specific message from the build 
logs?

--
John Merryweather Cooper
Build  Install Engineer -- ESA
Jack Henry  Associates, Inc.(r)
Shawnee Mission, KS  66227
Office:  913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com




-Original Message-
From: Skildum, Mathew [mailto:mathew.skil...@aspect.com]
Sent: Tuesday, August 27, 2013 11:38 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

All  of the WIX projects in question have those lines in place:

WixTargetsPath Condition= '$(WixTargetsPath)' == '' AND 
'$(MSBuildExtensionsPath32)' != '' 
$(MSBuildExtensionsPath32)\Microsoft\WiX\v3.x\Wix.targets/WixTargetsPath
WixTargetsPath Condition= '$(WixTargetsPath)' == '' 
$(MSBuildExtensionsPath)\Microsoft\WiX\v3.x\Wix.targets/WixTargetsPath

I just realized that forgot to mention I was using the .Net 4.0 version of MS 
Build.

MAT SKILDUM
SR PRINCIPAL ENGINEER
+1 (630) 227.8534 WORK
+1 (847) 909.9921 MOBILE
mathew.skil...@aspect.com
aspect.com




-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Tuesday, August 27, 2013 11:05 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

How far back do you wixproj files go?  Modern ones should have something like:

lt;WixTargetsPath Condition= '$(WixTargetsPath)' == '' AND 
'$(MSBuildExtensionsPath32)' != '' 
gt;$(MSBuildExtensionsPath32)\Microsoft\WiX\v3.x\Wix.targetslt;/WixTargetsPathgt;
lt;WixTargetsPath Condition= '$(WixTargetsPath)' == '' 
gt;$(MSBuildExtensionsPath)\Microsoft\WiX\v3.x\Wix.targetslt;/WixTargetsPathgt;

Older files don't have both lines causing things to fail on x64 systems.

--
John Merryweather Cooper
Build  Install Engineer -- ESA
Jack Henry  Associates, Inc.(r)
Shawnee Mission, KS  66227
Office:  913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com




-Original Message-
From: Skildum, Mathew [mailto:mathew.skil...@aspect.com]
Sent: Tuesday, August 27, 2013 10:44 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

I am using WIX 3.8 (build 3.8.708).  The build system is using the GA version 
of WIX 3.7.

I am havine issues on both systems.

-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: Tuesday, August 27, 2013 10:37 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

Which version of WiX are you running? There was a bug a ways back about that.
 From: mathew.skil...@aspect.com
 To: wix-users@lists.sourceforge.net
 Date: Tue, 27 Aug 2013 14:54:30 +
 Subject: [WiX-users] 64 bit version of MS build cannot find the WIX 
 toolset
 
 I know there is probably a posting somewhere out on the web describing the 
 issue I am having, but I am not able to find it at the present moment.
 
 The problem I am current having is that the 64 bit version of MS build does 
 not properly evaluate the build variables and is not able to find WIX tools.  
 The 32 bit version works correctly and everything is happy, but when I switch 
 MS  Build targets everything goes to

Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

2013-08-27 Thread Edwin Castro

On 8/27/13 10:05 AM, Skildum, Mathew wrote:
 Here is an example of the build errors:

   CustomAction.cs(4,17): error CS0234: The type or namespace name 'Deployment'
 does not exist in the namespace 'Microsoft' (are you missing an assembly 
 refere
 nce?) 
   CustomAction.cs(12,58): error CS0246: The type or namespace name 'Session' 
 co
 uld not be found (are you missing a using directive or an assembly reference?)
   CustomAction.cs(12,23): error CS0246: The type or namespace name 
 'ActionResul
 t' could not be found (are you missing a using directive or an assembly 
 referen
 ce?) 

These are C# compile errors. It appears you might be missing a reference
to a DTF assembly. Or perhaps the assembly reference you already has an
incorrect HintPath and can't be found...?

--
Edwin G. Castro


--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

All hint paths are correct as everything build correctly in Visual Studio (2010 
and 2012).  The only time it fails is when I use the 64 bit version of MS Build.

Mat Skildum

-Original Message-
From: Edwin Castro [mailto:0ptikgh...@gmx.us] 
Sent: Tuesday, August 27, 2013 12:54 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

On 8/27/13 10:05 AM, Skildum, Mathew wrote:
 Here is an example of the build errors:

   CustomAction.cs(4,17): error CS0234: The type or namespace name 'Deployment'
 does not exist in the namespace 'Microsoft' (are you missing an 
 assembly refere
 nce?) 
   CustomAction.cs(12,58): error CS0246: The type or namespace name 
 'Session' co uld not be found (are you missing a using directive or an 
 assembly reference?)
   CustomAction.cs(12,23): error CS0246: The type or namespace name 
 'ActionResul t' could not be found (are you missing a using directive 
 or an assembly referen
 ce?)

These are C# compile errors. It appears you might be missing a reference to a 
DTF assembly. Or perhaps the assembly reference you already has an incorrect 
HintPath and can't be found...?

--
Edwin G. Castro


--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies and 
advance your career. Get an incredible 1,500+ hours of step-by-step tutorial 
videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

Building correctly on VS 2010 or 2012 doesn't tell you much as both of the 
those cache references.

Where is the Microsoft.Deployment.WindowsInstaller assembly on your build 
server, and what does the HintPath look like on the failing custom action 
project?

--
John Merryweather Cooper
Build  Install Engineer -- ESA
Jack Henry  Associates, Inc.(r)
Shawnee Mission, KS  66227
Office:  913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com




-Original Message-
From: Skildum, Mathew [mailto:mathew.skil...@aspect.com] 
Sent: Tuesday, August 27, 2013 1:03 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

All hint paths are correct as everything build correctly in Visual Studio (2010 
and 2012).  The only time it fails is when I use the 64 bit version of MS Build.

Mat Skildum

-Original Message-
From: Edwin Castro [mailto:0ptikgh...@gmx.us]
Sent: Tuesday, August 27, 2013 12:54 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

On 8/27/13 10:05 AM, Skildum, Mathew wrote:
 Here is an example of the build errors:

   CustomAction.cs(4,17): error CS0234: The type or namespace name 'Deployment'
 does not exist in the namespace 'Microsoft' (are you missing an 
 assembly refere
 nce?) 
   CustomAction.cs(12,58): error CS0246: The type or namespace name 
 'Session' co uld not be found (are you missing a using directive or an 
 assembly reference?)
   CustomAction.cs(12,23): error CS0246: The type or namespace name 
 'ActionResul t' could not be found (are you missing a using directive 
 or an assembly referen
 ce?)

These are C# compile errors. It appears you might be missing a reference to a 
DTF assembly. Or perhaps the assembly reference you already has an incorrect 
HintPath and can't be found...?

--
Edwin G. Castro


--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies and 
advance your career. Get an incredible 1,500+ hours of step-by-step tutorial 
videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies and 
advance your career. Get an incredible 1,500+ hours of step-by-step tutorial 
videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are 
intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged 
information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.


--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

2013-08-27 Thread Edwin Castro

On 8/27/13 11:03 AM, Skildum, Mathew wrote:
 All hint paths are correct as everything build correctly in Visual Studio 
 (2010 and 2012).  The only time it fails is when I use the 64 bit version of 
 MS Build.

Can you provide the reference XML from the project file? I assume you
have not modified them manually, correct?

--
Edwin G. Castro


--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Error Uninstalling a Wix Burn Bundle

2013-08-27 Thread thejohno

When trying to uninstall a WiX Burn Bundle (WiX 3.6) I get these errors from
the log file:

[0F90:0F94][2013-08-27T11:55:28]: Applying execute package: AI_MsiInstaller,
action: Uninstall, path: C:\Documents and Settings\All Users\Application
Data\Package
Cache\{12A4D809-34A8-4837-B376-521C2ACBE39D}v3.0.5\AI-3_0_5-May28.msi,
arguments: ' ARPSYSTEMCOMPONENT=1 MSIFASTINSTALL=7'
[0F90:0F94][2013-08-27T11:55:31]: Error 0x80070652: Failed to uninstall MSI
package.
[0F90:0F94][2013-08-27T11:55:31]: Error 0x80070652: Failed to execute MSI
package.
[0F60:0F64][2013-08-27T11:55:31]: Error 0x80070652: Failed to configure
per-machine MSI package.

I can't seem to figure out why this is occuring.  Please see the attached
files for my Bundle.wxs code as well as my Product.wxs and the full log
file.  Any help would be appreciated, thanks.






Green's_AI_Bootstrapper_(Wix_Burn)_20130827115439.log
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7588487/Green%27s_AI_Bootstrapper_%28Wix_Burn%29_20130827115439.log
  

Bundle.wxs
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7588487/Bundle.wxs
  

Product.wxs
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7588487/Product.wxs
  



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Error-Uninstalling-a-Wix-Burn-Bundle-tp7588487.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Reading xml file

2013-08-27 Thread Carl Enander

Hello,
I am new to Wix and have a question regarding wix and reading settings from an 
xml file when running the installer. I have an xml file with database 
connectionstrings that are different for my test and production environment:
configurationprodservernameconnectionstringconnstr1/connectionstring/prodservernametestservernameconnectionstringconnstr2/connectionstring/testservername/configuration
   When running installer I want to use the [COMPUTERNAME] variable to find the 
correct connectionstring value from the xml file and use this in a Custom 
Action (e.g. conntr1 to be used when installing on prod server and connstr2 
on test server):CustomAction Id=MyAction 

  ExeCommand=cmd.exe /C MyDatabaseInstaller Connstr  
  Execute=deferred 
  Return=check / 
Please guide me to the best way to do this simple task.
 
BR, Carl
 
 
  
--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

The Microsoft.Deployment.WindowsInstaller assembly is located in the default 
installation location.  No customization has been done to the system or the 
projects.

Here is the project file section that lists the above assembly refference:
  ItemGroup
Reference Include=System /
Reference Include=System.Core
  RequiredTargetFramework3.5/RequiredTargetFramework
/Reference
Reference Include=System.Management.Automation, Version=1.0.0.0, 
Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL
  SpecificVersionFalse/SpecificVersion
  
HintPath..\..\Assemblies\Powershell\System.Management.Automation.dll/HintPath
  PrivateTrue/Private
/Reference
Reference Include=System.Windows.Forms /
Reference Include=Microsoft.Deployment.WindowsInstaller /
  /ItemGroup

Mat Skildum




-Original Message-
From: Edwin Castro [mailto:0ptikgh...@gmx.us] 
Sent: Tuesday, August 27, 2013 1:13 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

On 8/27/13 11:03 AM, Skildum, Mathew wrote:
 All hint paths are correct as everything build correctly in Visual Studio 
 (2010 and 2012).  The only time it fails is when I use the 64 bit version of 
 MS Build.

Can you provide the reference XML from the project file? I assume you have not 
modified them manually, correct?

--
Edwin G. Castro


--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies and 
advance your career. Get an incredible 1,500+ hours of step-by-step tutorial 
videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

That doesn't look right.  Bearing in mind that we're still using WiX 3.6 RTM, 
my HintPath looks like:

lt;Reference Include=Microsoft.Deployment.WindowsInstaller, Version=3.0.0.0, 
Culture=neutral, PublicKeyToken=ce35f76fcda82bad, 
processorArchitecture=MSILgt;
  lt;HintPathgt;..\..\..\..\..\Program Files (x86)\WiX Toolset 
v3.6\bin\Microsoft.Deployment.WindowsInstaller.dlllt;/HintPathgt;
lt;/Referencegt;

I don't think you're going to resolve an assembly without a hint path unless 
it's in the GAC.
--
John Merryweather Cooper
Build  Install Engineer -- ESA
Jack Henry  Associates, Inc.(r)
Shawnee Mission, KS  66227
Office:  913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com




-Original Message-
From: Skildum, Mathew [mailto:mathew.skil...@aspect.com] 
Sent: Tuesday, August 27, 2013 1:45 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

The Microsoft.Deployment.WindowsInstaller assembly is located in the default 
installation location.  No customization has been done to the system or the 
projects.

Here is the project file section that lists the above assembly refference:
  ItemGroup
Reference Include=System /
Reference Include=System.Core
  RequiredTargetFramework3.5/RequiredTargetFramework
/Reference
Reference Include=System.Management.Automation, Version=1.0.0.0, 
Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL
  SpecificVersionFalse/SpecificVersion
  
HintPath..\..\Assemblies\Powershell\System.Management.Automation.dll/HintPath
  PrivateTrue/Private
/Reference
Reference Include=System.Windows.Forms /
Reference Include=Microsoft.Deployment.WindowsInstaller /
  /ItemGroup

Mat Skildum




-Original Message-
From: Edwin Castro [mailto:0ptikgh...@gmx.us]
Sent: Tuesday, August 27, 2013 1:13 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

On 8/27/13 11:03 AM, Skildum, Mathew wrote:
 All hint paths are correct as everything build correctly in Visual Studio 
 (2010 and 2012).  The only time it fails is when I use the 64 bit version of 
 MS Build.

Can you provide the reference XML from the project file? I assume you have not 
modified them manually, correct?

--
Edwin G. Castro


--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies and 
advance your career. Get an incredible 1,500+ hours of step-by-step tutorial 
videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies and 
advance your career. Get an incredible 1,500+ hours of step-by-step tutorial 
videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail message and any files transmitted with it are 
intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged 
information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.


--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

2013-08-27 Thread Edwin Castro

MSBuild uses the AssemblySearchPaths property to determine the locations
where it searches for assembly references. See
http://msdn.microsoft.com/en-us/library/vstudio/bb629394.aspx

You could either set the HintPath for the reference OR you could add the
location of Microsoft.Deployment.WindowsInstaller.dll to
AssemblySearchPaths with something like this:

PropertyGroup
  AssemblySearchPaths
C:\Program Files (x86)\WiX Toolset v3.6\bin;
$(AssemblySearchPaths)
  /AssemblySearchPaths
/PropertyGroup

Note that you could possibly shadow other assemblies you depend on if
they exist in WiX's bin directory (or whatever appropriate directory you
use).

My guess as to why 32-bit MSBuild (on the command line, not through
Visual Studio) is that AssemblySearchPaths must be getting set with
32-bit only path. Perhaps something like C:\Program Files\WiX Toolset
v3.6\bin which would only resolve for 32-bit processes... You can use
the /verbose:diagnostic command line option to show you property values
and a lot of other stuff you never cared about too!


On 8/27/13 11:59 AM, John Cooper wrote:
 That doesn't look right.  Bearing in mind that we're still using WiX 3.6 RTM, 
 my HintPath looks like:

 lt;Reference Include=Microsoft.Deployment.WindowsInstaller, 
 Version=3.0.0.0, Culture=neutral, PublicKeyToken=ce35f76fcda82bad, 
 processorArchitecture=MSILgt;
   lt;HintPathgt;..\..\..\..\..\Program Files (x86)\WiX Toolset 
 v3.6\bin\Microsoft.Deployment.WindowsInstaller.dlllt;/HintPathgt;
 lt;/Referencegt;

 I don't think you're going to resolve an assembly without a hint path unless 
 it's in the GAC.
 --
 John Merryweather Cooper
 Build  Install Engineer -- ESA
 Jack Henry  Associates, Inc.(r)
 Shawnee Mission, KS  66227
 Office:  913-341-3434 x791011
 jocoo...@jackhenry.com
 www.jackhenry.com




 -Original Message-
 From: Skildum, Mathew [mailto:mathew.skil...@aspect.com] 
 Sent: Tuesday, August 27, 2013 1:45 PM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX 
 toolset

 The Microsoft.Deployment.WindowsInstaller assembly is located in the default 
 installation location.  No customization has been done to the system or the 
 projects.

 Here is the project file section that lists the above assembly refference:
   ItemGroup
 Reference Include=System /
 Reference Include=System.Core
   RequiredTargetFramework3.5/RequiredTargetFramework
 /Reference
 Reference Include=System.Management.Automation, Version=1.0.0.0, 
 Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL
   SpecificVersionFalse/SpecificVersion
   
 HintPath..\..\Assemblies\Powershell\System.Management.Automation.dll/HintPath
   PrivateTrue/Private
 /Reference
 Reference Include=System.Windows.Forms /
 Reference Include=Microsoft.Deployment.WindowsInstaller /
   /ItemGroup

 Mat Skildum




 -Original Message-
 From: Edwin Castro [mailto:0ptikgh...@gmx.us]
 Sent: Tuesday, August 27, 2013 1:13 PM
 To: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX 
 toolset

 On 8/27/13 11:03 AM, Skildum, Mathew wrote:
 All hint paths are correct as everything build correctly in Visual Studio 
 (2010 and 2012).  The only time it fails is when I use the 64 bit version of 
 MS Build.
 Can you provide the reference XML from the project file? I assume you have 
 not modified them manually, correct?

 --
 Edwin G. Castro


 --
 Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
 Discover the easy way to master current and previous Microsoft technologies 
 and advance your career. Get an incredible 1,500+ hours of step-by-step 
 tutorial videos with LearnDevNow. Subscribe today and save!
 http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

 --
 Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
 Discover the easy way to master current and previous Microsoft technologies 
 and advance your career. Get an incredible 1,500+ hours of step-by-step 
 tutorial videos with LearnDevNow. Subscribe today and save!
 http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
 NOTICE: This electronic mail message and any files transmitted with it are 
 intended
 exclusively for the individual or entity to which it is addressed. The 
 message, 
 together with any attachment, may contain confidential and/or privileged

Re: [WiX-users] Reading xml file

2013-08-27 Thread John Ludlow

You would need an immediate custom action to read the .config file, find
the appropriate connection string, and set its value to a property.

CustomAction Id=MyAction

  ExeCommand=cmd.exe /C MyDatabaseInstaller [CONNSTR] 
  Execute=deferred
  Return=check /

If you're using WiX from Visual Studio, you can go to File  New Project,
and choose Windows Installer XML  C# Custom Action Project. (Or C++ if you
prefer).

The C# version will generate a method for you which represents your custom
action entry point, with a Session object which represents the MSI session.
You can treat it like a dictionary when it comes to properties:

 // Get a property
 string cfgFile = session[ConfigurationFilePath];

// Whatever code you need to find the right connection string

 // Set a property
 session[CONNSTR] = connstr;



The C++ version uses a bunch of functions all beginning with Wca. I can't
remember the syntax right now but the set and get functions for properties
aren't too difficult IIRC.


On 27 August 2013 19:32, Carl Enander c_enan...@hotmail.com wrote:

 Hello,
 I am new to Wix and have a question regarding wix and reading settings
 from an xml file when running the installer. I have an xml file with
 database connectionstrings that are different for my test and production
 environment:
 configurationprodservernameconnectionstringconnstr1/connectionstring/prodservernametestservernameconnectionstringconnstr2/connectionstring/testservername/configuration
   When running installer I want to use the [COMPUTERNAME] variable to find
 the correct connectionstring value from the xml file and use this in a
 Custom Action (e.g. conntr1 to be used when installing on prod server and
 connstr2 on test server):CustomAction Id=MyAction

   ExeCommand=cmd.exe /C MyDatabaseInstaller Connstr 
   Execute=deferred
   Return=check /
 Please guide me to the best way to do this simple task.

 BR, Carl




 --
 Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
 Discover the easy way to master current and previous Microsoft technologies
 and advance your career. Get an incredible 1,500+ hours of step-by-step
 tutorial videos with LearnDevNow. Subscribe today and save!
 http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Pending Reboot

2013-08-27 Thread tom


I think you can test for

 Command.Resume == ResumeType.RebootPending



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Pending-Reboot-tp7588050p7588495.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Error Uninstalling a Wix Burn Bundle

2013-08-27 Thread Phil Wilson

That error is Another installation is already in progress. Complete that
installation before proceeding with this install. .

Does that make sense?

Phil Wilson

On Tue, Aug 27, 2013 at 11:13 AM, thejohno jherm...@ualberta.ca wrote:

When trying to uninstall a WiX Burn Bundle (WiX 3.6) I get these errors
from
the log file:

[0F90:0F94][2013-08-27T11:55:28]: Applying execute package:
AI_MsiInstaller,
action: Uninstall, path: C:\Documents and Settings\All Users\Application
Data\Package
Cache\{12A4D809-34A8-4837-B376-521C2ACBE39D}v3.0.5\AI-3_0_5-May28.msi,
arguments: ' ARPSYSTEMCOMPONENT=1 MSIFASTINSTALL=7'
[0F90:0F94][2013-08-27T11:55:31]: Error 0x80070652: Failed to uninstall MSI
package.
[0F90:0F94][2013-08-27T11:55:31]: Error 0x80070652: Failed to execute MSI
package.
[0F60:0F64][2013-08-27T11:55:31]: Error 0x80070652: Failed to configure
per-machine MSI package.

I can't seem to figure out why this is occuring. Please see the attached
files for my Bundle.wxs code as well as my Product.wxs and the full log
file. Any help would be appreciated, thanks.

Green's_AI_Bootstrapper_(Wix_Burn)_20130827115439.log

http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7588487/Green%27s_AI_Bootstrapper_%28Wix_Burn%29_20130827115439.log

Bundle.wxs

http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7588487/Bundle.wxs

Product.wxs

http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7588487/Product.wxs

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Error-Uninstalling-a-Wix-Burn-Bundle-tp7588487.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Error Uninstalling a Wix Burn Bundle

2013-08-27 Thread John Hermary

Yes I think that was it. Thanks Phil.

*John Hermary *
*Software Developer
Green's Publishing*

Phone: +1 (780) 484-5550
Toll Free: +1 (866) 463-6968
jherm...@ualberta.ca

WordMemoryTest.com http://www.wordmemorytest.com
**

On Tue, Aug 27, 2013 at 3:13 PM, Phil Wilson phildgwil...@gmail.com wrote:

That error is Another installation is already in progress. Complete that
installation before proceeding with this install. .

Does that make sense?

Phil Wilson

On Tue, Aug 27, 2013 at 11:13 AM, thejohno jherm...@ualberta.ca wrote:

When trying to uninstall a WiX Burn Bundle (WiX 3.6) I get these errors
from
the log file:

[0F90:0F94][2013-08-27T11:55:28]: Applying execute package:
AI_MsiInstaller,
action: Uninstall, path: C:\Documents and Settings\All Users\Application
Data\Package
Cache\{12A4D809-34A8-4837-B376-521C2ACBE39D}v3.0.5\AI-3_0_5-May28.msi,
arguments: ' ARPSYSTEMCOMPONENT=1 MSIFASTINSTALL=7'
[0F90:0F94][2013-08-27T11:55:31]: Error 0x80070652: Failed to uninstall
MSI
package.
[0F90:0F94][2013-08-27T11:55:31]: Error 0x80070652: Failed to execute MSI
package.
[0F60:0F64][2013-08-27T11:55:31]: Error 0x80070652: Failed to configure
per-machine MSI package.

I can't seem to figure out why this is occuring. Please see the attached
files for my Bundle.wxs code as well as my Product.wxs and the full log
file. Any help would be appreciated, thanks.

Green's_AI_Bootstrapper_(Wix_Burn)_20130827115439.log

http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7588487/Green%27s_AI_Bootstrapper_%28Wix_Burn%29_20130827115439.log

Bundle.wxs

http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7588487/Bundle.wxs

Product.wxs

http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7588487/Product.wxs

--
View this message in context:

http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Error-Uninstalling-a-Wix-Burn-Bundle-tp7588487.html
Sent from the wix-users mailing list archive at Nabble.com.

http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

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

I've noticed that in the RtfTheme-Custom.xml, there is this which I'm guessing 
represents the Setup Successful page:

Page Name=Success
Text X=11 Y=80 Width=-11 Height=30 FontId=2 
DisablePrefix=yes#(loc.SuccessHeader)/Text
Button Name=LaunchButton X=-91 Y=-11 Width=75 Height=23 
TabStop=yes FontId=0 
HideWhenDisabled=yes#(loc.SuccessLaunchButton)/Button
Text Name=SuccessRestartText X=-11 Y=-51 Width=400 Height=34 
FontId=3 HideWhenDisabled=yes 
DisablePrefix=yes#(loc.SuccessRestartText)/Text
Button Name=SuccessRestartButton X=-91 Y=-11 Width=75 
Height=23 TabStop=yes FontId=0 
HideWhenDisabled=yes#(loc.SuccessRestartButton)/Button
Button Name=SuccessCancelButton X=-11 Y=-11 Width=75 
Height=23 TabStop=yes FontId=0#(loc.SuccessCloseButton)/Button
/Page

So I could theoretically add a Text element, but I'm not sure how I would set 
the text of that field. Furthermore, I may only want the text to show in 
specific cases (i.e. successful install) and not in others (i.e. install 
failure, modification, or repair).

Any ideas?

Alain

-Original Message-
From: Alain Forget [mailto:afor...@cmu.edu] 
Sent: Tuesday, August 27, 2013 08:13
To: 'General discussion for Windows Installer XML toolset.'
Subject: RE: [WiX-users] Add text to final window in burn bootstrapper/installer

Good question. I'm not sure exactly, but here’s some code snippets that what 
I'm guessing are UI-related:

Wix 
xmlns='http://schemas.microsoft.com/wix/2006/wi'
xmlns:bal=http://schemas.microsoft.com/wix/BalExtension;
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;

...
BootstrapperApplicationRef Id=WixStandardBootstrapperApplication.RtfLicense 
bal:WixStandardBootstrapperApplication
LicenseFile=License.rtf
LogoFile=lib\Logo_64x64.png
SuppressOptionsUI=yes
ThemeFile=RtfTheme-Custom.xml
/
/BootstrapperApplicationRef

Obviously, we are using a custom theme (RtfTheme-Custom.xml), but it's almost 
identical to the original src\ext\BalExtension\wixstdba\Resources\RtfTheme.xml 
. 


-Original Message-
From: Blair Murri [mailto:os...@live.com] 
Sent: Tuesday, August 27, 2013 05:51
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Add text to final window in burn bootstrapper/installer

Which UI are you using in your bundle?

 From: afor...@cmu.edu
 To: wix-users@lists.sourceforge.net
 Date: Mon, 26 Aug 2013 18:55:39 -0400
 Subject: [WiX-users] Add text to final window in burn bootstrapper/installer
 
 Hi all,
 
 Our installer bundled with burn currently posts a simple Setup Complete 
 message when the install is done. How can we add additional text on this last 
 window when the install is complete?
 
 Thanks,
 Alain
 
 
 --
 Introducing Performance Central, a new site from SourceForge and 
 AppDynamics. Performance Central is your source for news, insights, 
 analysis and resources for efficient Application Performance Management. 
 Visit us today!
 http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users
  
--
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] UNSUBSCRIBE

2013-08-27 Thread msanchez




Mark Sanchez
Systems Developer
SPEC Services, Inc.
--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] UNSUBSCRIBE

No.

Go here to unsubscribe yourself: 
https://lists.sourceforge.net/lists/listinfo/wix-users

-Original Message-
From: msanc...@specservices.com [mailto:msanc...@specservices.com] 
Sent: Tuesday, August 27, 2013 18:26
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] UNSUBSCRIBE




Mark Sanchez
Systems Developer
SPEC Services, Inc.
--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] UNSUBSCRIBE

2013-08-27 Thread msanchez

My company is blocking that site.

I didn't really need to unsubscribe but it seems as though I get an email for 
every entry added there.  It's as though I have been registered on a thread to 
receive replies, which I have never even posted anything.  How can this be 
turned off?


Mark Sanchez
Systems Developer
SPEC Services, Inc.


-Original Message-
From: Alain Forget [mailto:afor...@cmu.edu]
Sent: Tuesday, August 27, 2013 3:40 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] UNSUBSCRIBE

No.

Go here to unsubscribe yourself: 
https://lists.sourceforge.net/lists/listinfo/wix-users

-Original Message-
From: msanc...@specservices.com [mailto:msanc...@specservices.com]
Sent: Tuesday, August 27, 2013 18:26
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] UNSUBSCRIBE




Mark Sanchez
Systems Developer
SPEC Services, Inc.
--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] UNSUBSCRIBE

Your company blocks sourceforge.net? Huh.

There, I've just unsubscribed you. You should receive a confirmation e-mail 
probably asking you to click a link to confirm that hopefully your company 
doesn't block. If your company does block it, well then unless you can make a 
rule to route WiX-users mail directly into your trash, then I guess you're 
screwed, and you'll just have to enjoy our WiX technobabble. :-P


-Original Message-
From: msanc...@specservices.com [mailto:msanc...@specservices.com] 
Sent: Tuesday, August 27, 2013 18:53
To: afor...@cmu.edu; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] UNSUBSCRIBE

My company is blocking that site.

I didn't really need to unsubscribe but it seems as though I get an email for 
every entry added there.  It's as though I have been registered on a thread to 
receive replies, which I have never even posted anything.  How can this be 
turned off?


Mark Sanchez
Systems Developer
SPEC Services, Inc.


-Original Message-
From: Alain Forget [mailto:afor...@cmu.edu]
Sent: Tuesday, August 27, 2013 3:40 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] UNSUBSCRIBE

No.

Go here to unsubscribe yourself: 
https://lists.sourceforge.net/lists/listinfo/wix-users

-Original Message-
From: msanc...@specservices.com [mailto:msanc...@specservices.com]
Sent: Tuesday, August 27, 2013 18:26
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] UNSUBSCRIBE




Mark Sanchez
Systems Developer
SPEC Services, Inc.
--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] 64 bit version of MS build cannot find the WIX toolset

2013-08-27 Thread Rob Mensching

There's an issue open requesting WiX to write the AssemblySearchPaths in
64-bit hive. That isn't done today.


On Tue, Aug 27, 2013 at 12:27 PM, Edwin Castro 0ptikgh...@gmx.us wrote:

 MSBuild uses the AssemblySearchPaths property to determine the locations
 where it searches for assembly references. See
 http://msdn.microsoft.com/en-us/library/vstudio/bb629394.aspx

 You could either set the HintPath for the reference OR you could add the
 location of Microsoft.Deployment.WindowsInstaller.dll to
 AssemblySearchPaths with something like this:

 PropertyGroup
   AssemblySearchPaths
 C:\Program Files (x86)\WiX Toolset v3.6\bin;
 $(AssemblySearchPaths)
   /AssemblySearchPaths
 /PropertyGroup

 Note that you could possibly shadow other assemblies you depend on if
 they exist in WiX's bin directory (or whatever appropriate directory you
 use).

 My guess as to why 32-bit MSBuild (on the command line, not through
 Visual Studio) is that AssemblySearchPaths must be getting set with
 32-bit only path. Perhaps something like C:\Program Files\WiX Toolset
 v3.6\bin which would only resolve for 32-bit processes... You can use
 the /verbose:diagnostic command line option to show you property values
 and a lot of other stuff you never cared about too!


 On 8/27/13 11:59 AM, John Cooper wrote:
  That doesn't look right.  Bearing in mind that we're still using WiX 3.6
 RTM, my HintPath looks like:
 
  lt;Reference Include=Microsoft.Deployment.WindowsInstaller,
 Version=3.0.0.0, Culture=neutral, PublicKeyToken=ce35f76fcda82bad,
 processorArchitecture=MSILgt;
lt;HintPathgt;..\..\..\..\..\Program Files (x86)\WiX Toolset
 v3.6\bin\Microsoft.Deployment.WindowsInstaller.dlllt;/HintPathgt;
  lt;/Referencegt;
 
  I don't think you're going to resolve an assembly without a hint path
 unless it's in the GAC.
  --
  John Merryweather Cooper
  Build  Install Engineer -- ESA
  Jack Henry  Associates, Inc.(r)
  Shawnee Mission, KS  66227
  Office:  913-341-3434 x791011
  jocoo...@jackhenry.com
  www.jackhenry.com
 
 
 
 
  -Original Message-
  From: Skildum, Mathew [mailto:mathew.skil...@aspect.com]
  Sent: Tuesday, August 27, 2013 1:45 PM
  To: General discussion for Windows Installer XML toolset.
  Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX
 toolset
 
  The Microsoft.Deployment.WindowsInstaller assembly is located in the
 default installation location.  No customization has been done to the
 system or the projects.
 
  Here is the project file section that lists the above assembly
 refference:
ItemGroup
  Reference Include=System /
  Reference Include=System.Core
RequiredTargetFramework3.5/RequiredTargetFramework
  /Reference
  Reference Include=System.Management.Automation, Version=1.0.0.0,
 Culture=neutral, PublicKeyToken=31bf3856ad364e35,
 processorArchitecture=MSIL
SpecificVersionFalse/SpecificVersion
 
 HintPath..\..\Assemblies\Powershell\System.Management.Automation.dll/HintPath
PrivateTrue/Private
  /Reference
  Reference Include=System.Windows.Forms /
  Reference Include=Microsoft.Deployment.WindowsInstaller /
/ItemGroup
 
  Mat Skildum
 
 
 
 
  -Original Message-
  From: Edwin Castro [mailto:0ptikgh...@gmx.us]
  Sent: Tuesday, August 27, 2013 1:13 PM
  To: wix-users@lists.sourceforge.net
  Subject: Re: [WiX-users] 64 bit version of MS build cannot find the WIX
 toolset
 
  On 8/27/13 11:03 AM, Skildum, Mathew wrote:
  All hint paths are correct as everything build correctly in Visual
 Studio (2010 and 2012).  The only time it fails is when I use the 64 bit
 version of MS Build.
  Can you provide the reference XML from the project file? I assume you
 have not modified them manually, correct?
 
  --
  Edwin G. Castro
 
 
 
 --
  Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
  Discover the easy way to master current and previous Microsoft
 technologies and advance your career. Get an incredible 1,500+ hours of
 step-by-step tutorial videos with LearnDevNow. Subscribe today and save!
 
 http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
  ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users
 
 
 --
  Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
  Discover the easy way to master current and previous Microsoft
 technologies and advance your career. Get an incredible 1,500+ hours of
 step-by-step tutorial videos with LearnDevNow. Subscribe today and save!
 
 http://pubads.g.doubleclick.net/gampad/clk?id=58040911iu=/4140/ostg.clktrk
  ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net

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