[WiX-users] instaling a bundle to install an older msi

[jo...@msli.com]

Can I make a bundle that always uninstalls the previous msi before
installing the new one?

I have a bundle that installed an msi.

The bundle Version= 2013.07.01.0,
the msi Version = 3.0.1 
the program build 3699.

There was a problem with build 3699 so I must release build 3698, in a
way that is easy on the users.

May I create a bundle that will install the build 3698 some how?

I tried to increment the bundle Version= 2013.07.02.0, 
and build using the older msi, 
and install the bundle, 
"Programs and Feactures" increments the bundle version,
but the msi was not downgrade to build 3698.

How can I deal with this situation?

My bundle.wxs

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

  





  
















  
  http://www.winpcap.org/install/bin/WinPcap_4_1_3.exe";
InstallCondition="NOT WinPcapInstalled OR ( 4 > WinPcapVersionMajor AND 
1 > WinPcapVersionMinor)"
Permanent="yes"
  >

  
  
  http://support.apple.com/downloads/DL999/en_US/BonjourPSSetup.exe";
InstallCondition="NOT BonjourDLL OR v2.0.2.0 > BonjourVersion"
Permanent="yes"
  >

  
  
  
  
  

  




NOTICE: This email may contain confidential information.  Please see 
http://www.meyersound.com/confidential/ for our complete policy.

--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] instaling a bundle to install an older msi

[jo...@msli.com]

That's the only way?

Isn't there a way to force the user to uninstall one bundle before
installing a new one?

The reason I'm resistant to a custom BA is that I don't know how to
approach programming a BA correctly.  I know perl, python, bash, some C
(from a unix world).  I have made ant scripts to run wix commands, and I
have learned wix to make an msi and a basic bundle, but the bundle will
never pass QA as it is.

Are there no other options?

On Wed, 2013-07-03 at 02:13 -0700, Blair Murri wrote:
> The only way to do that today would be to write a custom BA that cycles 
> through plan and apply twice: once to remove the previous bundle and the 
> second time to install the MSI.
>  
> > From: jo...@msli.com
> > To: wix-users@lists.sourceforge.net
> > Date: Tue, 2 Jul 2013 18:13:45 -0700
> > Subject: [WiX-users] instaling a bundle to install an older msi
> > 
> > Can I make a bundle that always uninstalls the previous msi before
> > installing the new one?
> > 
> > I have a bundle that installed an msi.
> > 
> > The bundle Version= 2013.07.01.0,
> > the msi Version = 3.0.1 
> > the program build 3699.
> > 
> > There was a problem with build 3699 so I must release build 3698, in a
> > way that is easy on the users.
> > 
> > May I create a bundle that will install the build 3698 some how?
> > 
> > I tried to increment the bundle Version= 2013.07.02.0, 
> > and build using the older msi, 
> > and install the bundle, 
> > "Programs and Feactures" increments the bundle version,
> > but the msi was not downgrade to build 3698.
> > 
> > How can I deal with this situation?
> > 
> > My bundle.wxs
> > 
> > http://schemas.microsoft.com/wix/2006/wi";
> > xmlns:bal="http://schemas.microsoft.com/wix/BalExtension";
> > xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";
> > >
> > 
> >> Name="$(var.MyInstallerName)"
> > Version="$(var.BundleVersion)"
> > Manufacturer="$(var.MyCompanyName)"
> > Copyright="(c) All rights reserved."
> > UpgradeCode="$(var.Guid_Bundle)"
> > HelpTelephone="$(var.HelpPhone)"
> > HelpUrl="$(var.HelpUrl)"
> > UpdateUrl="$(var.UpdateUrl)"
> > AboutUrl="$(var.AboutUrl)"
> > Condition="((VersionNT >= v5.1) 
> > AND (ServicePackLevel >= 3)) 
> > OR ((VersionNT >= v5.2) 
> > AND (ServicePackLevel >= 2)) 
> > OR (VersionNT >= v6.0)"
> > IconSourceFile="$(var.ProdIcon)"
> >   >
> > 
> >  >   Id="WixUIBannerBmp"
> >   Value="../ProgramFiles/Resources/Images/InstallerHeaderImage.bmp"
> > />
> > 
> >  >   Id="WixStandardBootstrapperApplication.HyperlinkLicense"
> > >
> >> LicenseUrl="EULA.html"
> > LogoFile="$(var.ProdIcon)"
> > SuppressRepair="yes"
> > SuppressOptionsUI="yes"
> >   />  
> >   
> > 
> > 
> > 
> > 
> >  >   Id="RegistrySearchWinPcapHas" 
> >   Variable="WinPcapInstalled"
> >   Root="HKLM"
> > 
> > Key="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\WinPcapInst"
> >   Result="exists"
> > />
> >  >   Id="RegistrySearchWinPcapMajor" 
> >   Variable="WinPcapVersionMajor"
> >   Root="HKLM"
> > 
> > Key="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\WinPcapInst"
> >   Value="VersionMajor"
> >   Format="raw"
> >   Result="value"
> > />
> >  >   Id="RegistrySearchWinPcapMinor" 
> >   Variable="WinPcapVersionMinor"
> >   Root="HKLM"
> > 
> > Key="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\WinPcapInst"
> >   Value="VersionMinor"
> >   Format="raw"
> >   Result="value"
> > />
> > 
> >  >   Id="RegistrySearchBonjourHas" 
> >   Variable="BonjourDLL"
> >   Root="HKLM"
> > Key="SOFTWARE\Classes\AppID\Bonjour.DLL"
> >   Result="exists"
> >

[WiX-users] need complete file association example where heat is used

[jo...@msli.com]

I need help creating a file association though a wix installer, where
heat generates the file list wxs (so ID's are dynamic), and I don't want
to rely on transforming that file.

I understand I am effectively adding a  area to the component
area for my exe in the heat generated wxs.

I haven't found a concise complete example on the Internet, mailing
list, stackoverlow, or the book: "Wix 3.6 A developer's guide to windows
Installer XML", but this is a popular issue.

Many would benefit form a real world complete automated example.

In my heat generated wxs file I see:

  

  


How do I go from that to a valid  file association?

I have tried so many things incorrectly, I'm shoud just ask for the
right solution, rather than post the wrong thing.

I tried to set a property 


Then use the property to update the exe component, but I must be missing
some context, due to a lack of complete examples on line:


  

  


Things seem to bulid, but the registry doesn't look right
and .fooProject files don't open.



NOTICE: This email may contain confidential information.  Please see 
http://www.meyersound.com/confidential/ for our complete policy.

--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Use a TargetProperty in a Verb in a ProgId, for file association

[jo...@msli.com]

I am using wix-3.7 on windows7, to associate my program (Compass.exe)
with file-names ending in galileoGlobalProject.

I can build the msi and install it, but double clicking a file raises
error dialog: "Windows cannot access the specified device, path, or
file.  You may not have the appropriate permissions to access the item."

How do I populate the correct path to my program?

Details:

Heat generates my list of files using the following syntax:
heat.exe dir dist -dr INSTALLDIR -cg group_ProductFiles -alias .\ 
-norootdirectory -ext .WXS -ext .wixobj -ext .wxi MyProgram.resource_list.wxs

The auto-generated section is as follows:








I add this to the Project element:


I try to use the TargetProperty in a Verb in order to create an
Extension in a ProgId:






After installing I search the registry for my extension
HKEY_CLASSES_ROOT\.galileoGlobalProject
  (default)   REG)SZ   CompassgalileoGlobalProject
HKEY_CLASSES_ROOT\CompassgalileoGlobalProject\shell\open\command
  "[group_ProductFiles:Compass.exe]" "%1"
HKEY_CURRENT_USER\Software\Classes\.galileoGlobalProject
HKEY_CURRENT_USER\Software\Classes\CompassgalileoGlobalProject\shell\open\command
  "[group_ProductFiles:Compass.exe]" "%1"
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.galileoGlobalProject\OpenWithList
  (value not set)
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.galileoGlobalProject\OpenWithProgids
  CompassGalileoProjectREG_NONE  (zero-length binary value)

Have I done everything right?
My previous post got no love, so I'm trying to rephrase the question.


NOTICE: This email may contain confidential information.  Please see 
http://www.meyersound.com/confidential/ for our complete policy.

--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Use a TargetProperty in a Verb in a ProgId, for file association

[jo...@msli.com]

Affirmative
On Wed, 2013-08-14 at 14:27 -0700, Phill Hogland wrote:
> Question ?
> 
> 
> Is "galileoGlobalProject"  your file extension like .doc or .png (without
> the period)?
> 
> 
> 
> --
> View this message in context: 
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Use-a-TargetProperty-in-a-Verb-in-a-ProgId-for-file-association-tp7588039p7588042.html
> Sent from the wix-users mailing list archive at Nabble.com.
> 
> --
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead. 
> Download for free and get started troubleshooting in minutes. 
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users



NOTICE: This email may contain confidential information.  Please see 
http://www.meyersound.com/confidential/ for our complete policy.

--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] how to reference an element in heat generated file?

[jo...@msli.com]

If heat generates a file with unique identifiers for each element, is it
true that the Id of a particular element can't be referenced elsewhere,
as there is no way to determine the correct name?

I am facing this situation by trying to create a file association, where
my exe has an Id that changes every time I run heat, yet creating a file
association requires a TargetFile and Icon that refer to an Id, and not
the name of the file it self.

The following is a file association, but the '?' are the areas of
interest:

  

  


A hack is calling heat.exe with argument -suid, which sets the Id = file
name, and I simply use the file name in TargetFile="file_name.exe", but
it has issues if two files have the same name in different areas (i
think).

Since heat is part of wix it seems like in the design of how all the
parts fit together there must be a better way.


NOTICE: This email may contain confidential information.  Please see 
http://www.meyersound.com/confidential/ for our complete policy.

--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] how to reference an element in heat generated file?

[jo...@msli.com]

OK.  I'll construct a transform, but this seems like a daunting task.

I always have to run heat after every check out.  The developers can
change anything over time, branches, and releases, and the build isn't
supposed to break, so the smoothest policy for me is to limit
assumptions by always running heat against what ever is present.

I couldn't figure out how to modify the Component in the heat generated
file, so my transform chops it out, and I manually create the Component
in another file, with file associations.  This seems to be the easiest
way to solve the problem and I don't have to be an xslt wizard.

First, my Product element contains:

  
  



  

  
  

  


Second, another .wxs file contains the Component for my exe and file
associations:

  

  
  
  

  

  

  


My xslt transformation file cuts out the exe Component from the 

http://www.w3.org/1999/XSL/Transform";
xmlns:wix="http://schemas.microsoft.com/wix/2006/wi";>
  
  

  

  
  
  
  
  



Commands:

heat.exe dir dist -dr INSTALLDIR -cg group_ProductFiles -gg -g1 -sf -srd -var 
env.dist -t .\wix_project\MyProgram.filter2.xsl -out 
.\wix_project\MyProgram.resource_list.wxs 

candle.exe -dwxi_variables=MyProgram.variables.wxi -i MyProgram.variables.wxi 
-v -arch x86 -trace -out wixobj/ .\wix_project\MyProgram.wxs 
.\wix_project\MyProgram.resource_list.wxs .\wix_project\MyProgram.shortcuts.wxs 

light.exe -out foo.msi -b dist -ext WixUIExtension wixobj/MyProgram.wixobj 
wixobj/MyProgram.resource_list.wixobj wixobj/MyProgram.shortcuts.wixobj 

And it all worked.

I think the documentation could really benefit from a practical example
like this, so people don't have to search though the mailing list
threads.

On Thu, 2013-08-15 at 16:27 -0700, Blair Murri wrote:
> That's why I use a transform to insert the file association code under the 
> file element and I don't harvest my icons.
> 
> To ne fair, harvesting was originally intended to be performed just once, not 
> each build. Most projects don't need to be harvested each time, but there are 
> systems that do require it.
> 
> 
> "jo...@msli.com"  wrote:
> 
> If heat generates a file with unique identifiers for each element, is it
> true that the Id of a particular element can't be referenced elsewhere,
> as there is no way to determine the correct name?
> 
> I am facing this situation by trying to create a file association, where
> my exe has an Id that changes every time I run heat, yet creating a file
> association requires a TargetFile and Icon that refer to an Id, and not
> the name of the file it self.
> 
> The following is a file association, but the '?' are the areas of
> interest:
>  Icon="?" IconIndex="0" >
>   
> 
>   
> 
> 
> A hack is calling heat.exe with argument -suid, which sets the Id = file
> name, and I simply use the file name in TargetFile="file_name.exe", but
> it has issues if two files have the same name in different areas (i
> think).
> 
> Since heat is part of wix it seems like in the design of how all the
> parts fit together there must be a better way.
> 
> 
> NOTICE: This email may contain confidential information.  Please see 
> http://www.meyersound.com/confidential/ for our complete policy.
> 
> --
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> --
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead. 
> Download for free and get started troubleshooting in minutes. 
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users



--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for p

[WiX-users] disassemble a bundle

[jo...@msli.com]

Is there a way to disassemble a bundle?



NOTICE: This email may contain confidential information.  Please see 
http://www.meyersound.com/confidential/ for our complete policy.

--
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=48897511&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] disassemble a bundle

[jo...@msli.com]

I ask because dark didn't work for me.

$ dark  MyProgram-3.1.0-3776-Installer.exe
Windows Installer Xml Decompiler version 3.7.1224.0
Copyright (C) Outercurve Foundation. All rights reserved.

MyProgram-3.1.0-3776-Installer.exe
dark.exe : error DARK0001 : Value cannot be null.
Parameter name: path1

Exception Type: System.ArgumentNullException

Stack Trace:
   at System.IO.Path.Combine(String path1, String path2)
   at Microsoft.Tools.WindowsInstallerXml.Unbinder.UnbindBundle(String
bundleFile, String exportBasePath)
   at Microsoft.Tools.WindowsInstallerXml.Unbinder.Unbind(String file,
OutputType outputType, String exportBasePath)
   at Microsoft.Tools.WindowsInstallerXml.Tools.Dark.Run(String[] args)


On Mon, 2013-08-19 at 11:55 -0700, Rob Mensching wrote:
> Just like everything else: dark.exe.
> 
> 
> On Mon, Aug 19, 2013 at 11:44 AM, jo...@msli.com  wrote:
> 
> > Is there a way to disassemble a bundle?
> >
> >
> >
> > NOTICE: This email may contain confidential information.  Please see
> > http://www.meyersound.com/confidential/ for our complete policy.
> >
> >
> > --
> > 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=48897511&iu=/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=48897511&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users



NOTICE: This email may contain confidential information.  Please see 
http://www.meyersound.com/confidential/ for our complete policy.

--
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=48897511&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] disassemble a bundle

[jo...@msli.com]

I see I had to make a directory and extract into it
dark.exe -x foo MyProgram-3.1.0-3776-Installer.exe

On Mon, 2013-08-19 at 13:52 -0700, jo...@msli.com wrote:
> I ask because dark didn't work for me.
> 
> $ dark  MyProgram-3.1.0-3776-Installer.exe
> Windows Installer Xml Decompiler version 3.7.1224.0
> Copyright (C) Outercurve Foundation. All rights reserved.
> 
> MyProgram-3.1.0-3776-Installer.exe
> dark.exe : error DARK0001 : Value cannot be null.
> Parameter name: path1
> 
> Exception Type: System.ArgumentNullException
> 
> Stack Trace:
>at System.IO.Path.Combine(String path1, String path2)
>at Microsoft.Tools.WindowsInstallerXml.Unbinder.UnbindBundle(String
> bundleFile, String exportBasePath)
>at Microsoft.Tools.WindowsInstallerXml.Unbinder.Unbind(String file,
> OutputType outputType, String exportBasePath)
>at Microsoft.Tools.WindowsInstallerXml.Tools.Dark.Run(String[] args)
> 
> 
> On Mon, 2013-08-19 at 11:55 -0700, Rob Mensching wrote:
> > Just like everything else: dark.exe.
> > 
> > 
> > On Mon, Aug 19, 2013 at 11:44 AM, jo...@msli.com  wrote:
> > 
> > > Is there a way to disassemble a bundle?
> > >
> > >
> > >
> > > NOTICE: This email may contain confidential information.  Please see
> > > http://www.meyersound.com/confidential/ for our complete policy.
> > >
> > >
> > > --
> > > 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=48897511&iu=/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=48897511&iu=/4140/ostg.clktrk
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 
> 
> NOTICE: This email may contain confidential information.  Please see 
> http://www.meyersound.com/confidential/ for our complete policy.
> 
> --
> 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=48897511&iu=/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=48897511&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] bundle error if I build though automated system

[jo...@msli.com]

I am trying to figure out what is wrong with a bundle created in my
auto-build system.

I have created 2 bundles with the same scripts and files files, that
differ only in how the scripts where run.

The bundle created by the auto-build system has error 0x80004005
-Unspecified error (see attached log).

The bundle created from a console works.

They are almost the same in size.
If I exclude MyProgram msi from the bundle it appears to work.

I used dark to disassemble each, and diff'ed the output, to see they
only differ.  

BootstrapperApplicationData.xml different only in 'Id'.

manifest.xml differ in 'Hash', 'ProviderKey', 'DisplayVersion',
'CacheId', 'ProductCode' but everything else is identical.

Is the answer in the log?

NOTICE: This email may contain confidential information.  Please see 
http://www.meyersound.com/confidential/ for our complete policy.
--
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=48897511&iu=/4140/ostg.clktrk___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] bundle error if I build though automated system

[jo...@msli.com]

0F0C:07F4][2013-08-19T14:44:59]i360: Creating a system restore point.
[0F0C:07F4][2013-08-19T14:45:05]i361: Created a system restore point.
[0F0C:07F4][2013-08-19T14:45:05]i000: Caching bundle from: 
'C:\Users\build\AppData\Local\Temp\{0738b243-a7de-4229-8123-de7e99343c3d}\.be\MyProgram-3.1.0-3776-Installer.exe'
 to: 'C:\ProgramData\Package 
Cache\{0738b243-a7de-4229-8123-de7e99343c3d}\MyProgram-3.1.0-3776-Installer.exe'
[0F0C:07F4][2013-08-19T14:45:05]i320: Registering bundle dependency provider: 
{0738b243-a7de-4229-8123-de7e99343c3d}, version: 2013.819.1414.14
[0EA8:0D14][2013-08-19T14:45:05]i336: Acquiring container: 
WixAttachedContainer, copy from: 
C:\Users\build\Desktop\MyProgram-3.1.0-3776-Installer.exe
[0EA8:0D14][2013-08-19T14:45:05]i000: Setting string variable 
'WixBundleLastUsedSource' to value 'C:\Users\build\Desktop\'
[0EA8:0A88][2013-08-19T14:45:05]e000: Error 0x80004005: Failed to extract all 
files from container.
[0EA8:0D14][2013-08-19T14:45:05]e000: Error 0x80004005: Failed to wait for 
operation complete.
[0EA8:0D14][2013-08-19T14:45:05]e000: Error 0x80004005: Failed to open 
container.
[0EA8:0D14][2013-08-19T14:45:05]e000: Error 0x80004005: Failed to open 
container: WixAttachedContainer.
[0EA8:0D14][2013-08-19T14:45:05]e312: Failed to extract payloads from 
container: WixAttachedContainer to working path: 
C:\Users\build\AppData\Local\Temp\{0738b243-a7de-4229-8123-de7e99343c3d}\05F520C359D62113041D1724863E4A04B8A4844B,
 error: 0x80004005.
[0EA8:0208][2013-08-19T14:45:05]e000: Error 0x80004005: Failed while caching, 
aborting execution.
[0F0C:07F4][2013-08-19T14:45:05]i330: Removed bundle dependency provider: 
{0738b243-a7de-4229-8123-de7e99343c3d}
[0F0C:07F4][2013-08-19T14:45:05]i352: Removing cached bundle: 
{0738b243-a7de-4229-8123-de7e99343c3d}, from path: C:\ProgramData\Package 
Cache\{0738b243-a7de-4229-8123-de7e99343c3d}\
[0EA8:0208][2013-08-19T14:45:06]i399: Apply complete, result: 0x80004005, 
restart: None, ba requested restart:  No


On Mon, 2013-08-19 at 15:09 -0700, jo...@msli.com wrote:
> I am trying to figure out what is wrong with a bundle created in my
> auto-build system.
> 
> I have created 2 bundles with the same scripts and files files, that
> differ only in how the scripts where run.
> 
> The bundle created by the auto-build system has error 0x80004005
> -Unspecified error (see attached log).
> 
> The bundle created from a console works.
> 
> They are almost the same in size.
> If I exclude MyProgram msi from the bundle it appears to work.
> 
> I used dark to disassemble each, and diff'ed the output, to see they
> only differ.  
> 
> BootstrapperApplicationData.xml different only in 'Id'.
> 
> manifest.xml differ in 'Hash', 'ProviderKey', 'DisplayVersion',
> 'CacheId', 'ProductCode' but everything else is identical.
> 
> Is the answer in the log?
> 
> NOTICE: This email may contain confidential information.  Please see 
> http://www.meyersound.com/confidential/ for our complete policy.
> --
> 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=48897511&iu=/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=48897511&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] bundle error if I build though automated system

[jo...@msli.com]

I sign the bundle I get this error.
An unsigned bundle seems to work.

On Mon, 2013-08-19 at 15:36 -0700, jo...@msli.com wrote:
> Looks like my log file was stripped out
> 
> [0EA8:0208][2013-08-19T14:44:54]i001: Burn v3.7.1224.0, Windows v6.1 (Build 
> 7601: Service Pack 1), path: 
> C:\Users\build\Desktop\MyProgram-3.1.0-3776-Installer.exe, cmdline: 
> '-burn.unelevated BurnPipe.{A7261C75-BACC-4401-B5F3-42EEC22098B5} 
> {F94F9B48-9AB8-4C18-969A-9AAF3E9BB205} 3852'
> [0EA8:0208][2013-08-19T14:44:54]i000: Setting string variable 'WixBundleLog' 
> to value 
> 'C:\Users\build\AppData\Local\Temp\My_Company_MyProgram_3.1.0_Bundle_20130819144454.log'
> [0EA8:0208][2013-08-19T14:44:54]i000: Setting string variable 
> 'WixBundleOriginalSource' to value 
> 'C:\Users\build\Desktop\MyProgram-3.1.0-3776-Installer.exe'
> [0EA8:0208][2013-08-19T14:44:55]i052: Condition '( (VersionNT >= v5.1) AND 
> (ServicePackLevel >= 3)) OR ( (VersionNT >= v5.2) AND (ServicePackLevel >= 
> 2)) OR (VersionNT >= v6.0)' evaluates to true.
> [0EA8:0208][2013-08-19T14:44:55]i000: Setting string variable 'WixBundleName' 
> to value 'Meyer Sound MyProgram 3.1.0 Bundle'
> [0EA8:0208][2013-08-19T14:44:55]i100: Detect begin, 4 packages
> [0EA8:0208][2013-08-19T14:44:55]i000: Setting numeric variable 'BonjourDLL' 
> to value 1
> [0EA8:0208][2013-08-19T14:44:55]i000: Setting string variable 
> 'BounjourVersion' to value '2.0.2.0'
> [0EA8:0208][2013-08-19T14:44:55]i000: Setting numeric variable 
> 'ProxyInstalled' to value 1
> [0EA8:0208][2013-08-19T14:44:55]i000: Setting numeric variable 
> 'WinPcapInstalled' to value 1
> [0EA8:0208][2013-08-19T14:44:55]i000: Setting string variable 
> 'WinPcapVersionMajor' to value '4'
> [0EA8:0208][2013-08-19T14:44:55]i000: Setting string variable 
> 'WinPcapVersionMinor' to value '1'
> [0EA8:0208][2013-08-19T14:44:55]i103: Detected related package: 
> {03D789F3-42D5-4FEC-BCDA-0F5BAC51B535}, scope: PerMachine, version: 1.0.3.0, 
> language: 0 operation: Downgrade
> [0EA8:0208][2013-08-19T14:44:55]i101: Detected package: WinPcap, state: 
> Absent, cached: None
> [0EA8:0208][2013-08-19T14:44:55]i101: Detected package: BonjourPSSetup, 
> state: Absent, cached: None
> [0EA8:0208][2013-08-19T14:44:55]i101: Detected package: MyProxy, state: 
> Obsolete, cached: None
> [0EA8:0208][2013-08-19T14:44:55]i104: Detected package: MyProxy, feature: 
> DefaultFeature, state: Absent
> [0EA8:0208][2013-08-19T14:44:55]i101: Detected package: MyProgramInstaller, 
> state: Absent, cached: None
> [0EA8:0208][2013-08-19T14:44:55]i104: Detected package: MyProgramInstaller, 
> feature: Complete, state: Absent
> [0EA8:0208][2013-08-19T14:44:55]i199: Detect complete, result: 0x0
> [0EA8:0208][2013-08-19T14:44:59]i200: Plan begin, 4 packages, action: Install
> [0EA8:0208][2013-08-19T14:44:59]i052: Condition 'NOT WinPcapInstalled OR ( 4 
> > WinPcapVersionMajor AND 1 > WinPcapVersionMinor)' evaluates to false.
> [0EA8:0208][2013-08-19T14:44:59]w321: Skipping dependency registration on 
> package with no dependency providers: WinPcap
> [0EA8:0208][2013-08-19T14:44:59]i052: Condition 'NOT BonjourDLL OR v2.0.2.0 > 
> BonjourVersion' evaluates to false.
> [0EA8:0208][2013-08-19T14:44:59]w321: Skipping dependency registration on 
> package with no dependency providers: BonjourPSSetup
> [0EA8:0208][2013-08-19T14:44:59]i204: Plan 1 msi features for package: 
> MyProgramInstaller
> [0EA8:0208][2013-08-19T14:44:59]i203: Planned feature: Complete, state: 
> Absent, default requested: Unknown, ba requested: Unknown, execute action: 
> None, rollback action: None
> [0EA8:0208][2013-08-19T14:44:59]i000: Setting string variable 
> 'WixBundleRollbackLog_MyProgramInstaller' to value 
> 'C:\Users\build\AppData\Local\Temp\My_Company_MyProgram_3.1.0_Bundle_20130819144454_0_MyProgramInstaller_rollback.log'
> [0EA8:0208][2013-08-19T14:44:59]i000: Setting string variable 
> 'WixBundleLog_MyProgramInstaller' to value 
> 'C:\Users\build\AppData\Local\Temp\My_Company_MyProgram_3.1.0_Bundle_20130819144454_0_MyProgramInstaller.log'
> [0EA8:0208][2013-08-19T14:44:59]i201: Planned package: WinPcap, state: 
> Absent, default requested: Absent, ba requested: Absent, execute: None, 
> rollback: None, cache: No, uncache: No, dependency: None
> [0EA8:0208][2013-08-19T14:44:59]i201: Planned package: BonjourPSSetup, state: 
> Absent, default requested: Absent, ba requested: Absent, execute: None, 
> rollback: None, cache: No, uncache: No, dependency: None
> [0EA8:0208][2013-08-19T14:44:59]i201: Planned p

Re: [WiX-users] bundle error if I build though automated system

[jo...@msli.com]

It is a bundle signing problem so the email thread title is wrong, but I
didn't know that at the time.  Should start a new thread?

The documentation?  I don't see the word insignia mentioned in, "WIX
3.6: A Developer's Guild to Windows Installer XML".  Maybe there should
be a errata?  Wix documentation needs a searchable work flow oriented
index of how-to's in addition to a man page on each tool.  

Since code signing is a necessary evil in Windows8, wix needs a tool
called "scorch.exe" that knows how to handle any files it can generate,
so this isn't so convoluted.

Looks like you mean:
  http://wix.sourceforge.net/manual-wix3/insignia.htm
this procedure:
1. Detach engine from bundle
COMMAND: insignia.exe -ib MyBundle.exe -o engine.exe
2. Sign engine
COMMAND: signtool.exe sign /v /f my.pfx /p cert_passwd /t ${CERT_TIME_URL} /du 
mydomain.com /d MyProgram engine.exe
3. Re-attach the burn engine from a bundle
insignia -ab engine.exe MyBundle.exe -o MyBundle.exe
4. Sign bundle
COMMAND: signtool.exe sign /v /f my.pfx /p cert_passwd /t ${CERT_TIME_URL} /du 
mydomain.com /d MyProgram MyBundle.exe


On Tue, 2013-08-20 at 08:17 -0700, Rob Mensching wrote: 
> Did you sign the bundle according to the documentation on the Insignia page?
> 
> 
> On Mon, Aug 19, 2013 at 4:57 PM, jo...@msli.com  wrote:
> 
> > I sign the bundle I get this error.
> > An unsigned bundle seems to work.
> >
> > On Mon, 2013-08-19 at 15:36 -0700, jo...@msli.com wrote:
> > > Looks like my log file was stripped out
> > >
> > > [0EA8:0208][2013-08-19T14:44:54]i001: Burn v3.7.1224.0, Windows v6.1
> > (Build 7601: Service Pack 1), path:
> > C:\Users\build\Desktop\MyProgram-3.1.0-3776-Installer.exe, cmdline:
> > '-burn.unelevated BurnPipe.{A7261C75-BACC-4401-B5F3-42EEC22098B5}
> > {F94F9B48-9AB8-4C18-969A-9AAF3E9BB205} 3852'
> > > [0EA8:0208][2013-08-19T14:44:54]i000: Setting string variable
> > 'WixBundleLog' to value
> > 'C:\Users\build\AppData\Local\Temp\My_Company_MyProgram_3.1.0_Bundle_20130819144454.log'
> > > [0EA8:0208][2013-08-19T14:44:54]i000: Setting string variable
> > 'WixBundleOriginalSource' to value
> > 'C:\Users\build\Desktop\MyProgram-3.1.0-3776-Installer.exe'
> > > [0EA8:0208][2013-08-19T14:44:55]i052: Condition '( (VersionNT >= v5.1)
> > AND (ServicePackLevel >= 3)) OR ( (VersionNT >= v5.2) AND (ServicePackLevel
> > >= 2)) OR (VersionNT >= v6.0)' evaluates to true.
> > > [0EA8:0208][2013-08-19T14:44:55]i000: Setting string variable
> > 'WixBundleName' to value 'Meyer Sound MyProgram 3.1.0 Bundle'
> > > [0EA8:0208][2013-08-19T14:44:55]i100: Detect begin, 4 packages
> > > [0EA8:0208][2013-08-19T14:44:55]i000: Setting numeric variable
> > 'BonjourDLL' to value 1
> > > [0EA8:0208][2013-08-19T14:44:55]i000: Setting string variable
> > 'BounjourVersion' to value '2.0.2.0'
> > > [0EA8:0208][2013-08-19T14:44:55]i000: Setting numeric variable
> > 'ProxyInstalled' to value 1
> > > [0EA8:0208][2013-08-19T14:44:55]i000: Setting numeric variable
> > 'WinPcapInstalled' to value 1
> > > [0EA8:0208][2013-08-19T14:44:55]i000: Setting string variable
> > 'WinPcapVersionMajor' to value '4'
> > > [0EA8:0208][2013-08-19T14:44:55]i000: Setting string variable
> > 'WinPcapVersionMinor' to value '1'
> > > [0EA8:0208][2013-08-19T14:44:55]i103: Detected related package:
> > {03D789F3-42D5-4FEC-BCDA-0F5BAC51B535}, scope: PerMachine, version:
> > 1.0.3.0, language: 0 operation: Downgrade
> > > [0EA8:0208][2013-08-19T14:44:55]i101: Detected package: WinPcap, state:
> > Absent, cached: None
> > > [0EA8:0208][2013-08-19T14:44:55]i101: Detected package: BonjourPSSetup,
> > state: Absent, cached: None
> > > [0EA8:0208][2013-08-19T14:44:55]i101: Detected package: MyProxy, state:
> > Obsolete, cached: None
> > > [0EA8:0208][2013-08-19T14:44:55]i104: Detected package: MyProxy,
> > feature: DefaultFeature, state: Absent
> > > [0EA8:0208][2013-08-19T14:44:55]i101: Detected package:
> > MyProgramInstaller, state: Absent, cached: None
> > > [0EA8:0208][2013-08-19T14:44:55]i104: Detected package:
> > MyProgramInstaller, feature: Complete, state: Absent
> > > [0EA8:0208][2013-08-19T14:44:55]i199: Detect complete, result: 0x0
> > > [0EA8:0208][2013-08-19T14:44:59]i200: Plan begin, 4 packages, action:
> > Install
> > > [0EA8:0208][2013-08-19T14:44:59]i052: Condition 'NOT WinPcapInstalled OR
> > ( 4 > WinPcapVersionMajor AND 1 

Re: [WiX-users] disassemble a bundle

[jo...@msli.com]

How do I file a bug?

I get "Oops, looks like something went wrong." no matter how I try to
reach your bug tracking system.

>From http://wixtoolset.org
 I click 'Bugs', which points to  http://wixtoolset.org/bugs

>From http://wix.sourceforge.net/ On the right under Support -> Bug
Database also points to http://wixtoolset.org/bugs

I also tried to reach: http://sourceforge.net/p/wix/bugs/

>From https://sourceforge.net/projects/wix/
I clicked on Tickets -> Bugs

What is the correct way?

On Mon, 2013-08-19 at 22:36 -0700, Blair Murri wrote:
> I think we should make that error message more clear. Please file a bug.
>  
> > From: jo...@msli.com
> > To: wix-users@lists.sourceforge.net
> > Date: Mon, 19 Aug 2013 14:00:08 -0700
> > Subject: Re: [WiX-users] disassemble a bundle
> > 
> > I see I had to make a directory and extract into it
> > dark.exe -x foo MyProgram-3.1.0-3776-Installer.exe
> > 
> > On Mon, 2013-08-19 at 13:52 -0700, jo...@msli.com wrote:
> > > I ask because dark didn't work for me.
> > > 
> > > $ dark  MyProgram-3.1.0-3776-Installer.exe
> > > Windows Installer Xml Decompiler version 3.7.1224.0
> > > Copyright (C) Outercurve Foundation. All rights reserved.
> > > 
> > > MyProgram-3.1.0-3776-Installer.exe
> > > dark.exe : error DARK0001 : Value cannot be null.
> > > Parameter name: path1
> > > 
> > > Exception Type: System.ArgumentNullException
> > > 
> > > Stack Trace:
> > >at System.IO.Path.Combine(String path1, String path2)
> > >at Microsoft.Tools.WindowsInstallerXml.Unbinder.UnbindBundle(String
> > > bundleFile, String exportBasePath)
> > >at Microsoft.Tools.WindowsInstallerXml.Unbinder.Unbind(String file,
> > > OutputType outputType, String exportBasePath)
> > >at Microsoft.Tools.WindowsInstallerXml.Tools.Dark.Run(String[] args)
> > > 
> > > 
> > > On Mon, 2013-08-19 at 11:55 -0700, Rob Mensching wrote:
> > > > Just like everything else: dark.exe.
> > > > 
> > > > 
> > > > On Mon, Aug 19, 2013 at 11:44 AM, jo...@msli.com  wrote:
> > > > 
> > > > > Is there a way to disassemble a bundle?
> > > > >
> > > > >
> > > > >
> > > > > NOTICE: This email may contain confidential information.  Please see
> > > > > http://www.meyersound.com/confidential/ for our complete policy.
> > > > >
> > > > >
> > > > > --
> > > > > 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=48897511&iu=/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=48897511&iu=/4140/ostg.clktrk
> > > > ___
> > > > WiX-users mailing list
> > > > WiX-users@lists.sourceforge.net
> > > > https://lists.sourceforge.net/lists/listinfo/wix-users
> > > 
> > > 
> > > 
> > > NOTICE: This email may contain confidential information.  Please see 
> > > http://www.meyersound.com/confidential/ for our complete policy.
> > > 
> > > --
> > > Introducing Performance Central, a new site from SourceForge and 
> > > AppDynamics. Performance Central is your source for news, insights, 
> > > analysis and resources for efficient Application 

[WiX-users] wild card search in registry

[jo...@msli.com]

My bundle needs to perform a conditional install if a 3rd party program
if the version installed is none or less than a particular version.

The problem is the 3rd party program stores the installed version number
in a dynamic guid section of HKLM, so I don't have a deterministic path
to the information.

Has anyone developed a wild card search method for elusive targets like
this?

The information on one system is in:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer
\UserData\S-1-5-18\Products\043899F85CE10A14BA724F736669840C
\InstallProperties
Contains: Key:DisplayVersion   Value:1.0.4

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion
\Uninstall\{8F998340-1EC5-41A0-AB27-F437669648C0}
  Contains: Key:DisplayVersion   Value:1.0.4

What are my options?


NOTICE: This email may contain confidential information.  Please see 
http://www.meyersound.com/confidential/ for our complete policy.

--
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=48897511&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] using WixUI_Advanced

[jo...@msli.com]

In my wix msi I am giving the user a choice of per-user vs.
system-wide.  

What is the best way to indicate a nested directory structure in
ApplicationFolderName?

Examples do not show how to do a nested directory structure.  

My directory structure looks like this, where the product is nested
inside a folder named for the company, as there are many other products.


 
  
   
   
  
 


In  I added
 

Can ApplicationFolderName look like this, where I spell out the directory 
nesting?
 

Is this the right way to do it or is there something better?

Additionally, the dialog does not look exactly like a drop in
replacement for the simple radio selection bettween per-user vs
system-wide provided in the  Visual Studio Setup Project.  Is there a
way to get that behavior?



NOTICE: This email may contain confidential information.  Please see 
http://www.meyersound.com/confidential/ for our complete policy.

--
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=58040911&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] using WixUI_Advanced

[jo...@msli.com]

Has anyone had success copying WixUI_Advanced.wxs to a
Custom_Advanced.wxs and using it in your msi installer?

I end up with lots of errors like these:

 [exec] 
C:\cygwin\home\build\current\EUROPA\Source\wix_project\Custom_Advanced.wxs(37) 
: error LGHT0091 : Duplicate symbol 'CustomAction:WixSetDefaultPerUserFolder' 
found. This typically means that an Id is duplicated. Check to make sure all 
your identifiers of a given type (File, Component, Feature) are unique.
 [exec] 
E:\delivery\Dev\wix37_public\src\ext\UIExtension\wixlib\WixUI_Advanced.wxs(37) 
: error LGHT0092 : Location of symbol related to previous error.
 [exec] 
E:\delivery\Dev\wix37_public\src\ext\UIExtension\wixlib\WixUI_Advanced.wxs(38) 
: error LGHT0091 : Duplicate symbol 
'CustomAction:WixSetDefaultPerMachineFolder' found. This typically means that 
an Id is duplicated. Check to make sure all your identifiers of a given type 
(File, Component, Feature) are unique.
 [exec] 
C:\cygwin\home\build\current\EUROPA\Source\wix_project\Custom_Advanced.wxs(38) 
: error LGHT0092 : Location of symbol related to previous error.
 [exec] 
C:\cygwin\home\build\current\EUROPA\Source\wix_project\Custom_Advanced.wxs(37) 
: error LGHT0091 : Duplicate symbol 'CustomAction:WixSetDefaultPerUserFolder' 
found. This typically means that an Id is duplicated. Check to make sure all 
your identifiers of a given type (File, Component, Feature) are unique.
 [exec] 
E:\delivery\Dev\wix37_public\src\ext\UIExtension\wixlib\WixUI_Advanced.wxs(37) 
: error LGHT0092 : Location of symbol related to previous error.

I copied WixUI_Advanced.wxs to my project directory as
Custom_Advanced.wxs, and changed 
From:
< 
To:
> 

And in my Product element I added 


What Am I missing?  I'm following the Wix 3.6: A Developer's guide to
windows Installer XML.

On Thu, 2013-08-29 at 09:31 -0700, jo...@msli.com wrote:
> In my wix msi I am giving the user a choice of per-user vs.
> system-wide.  
> 
> What is the best way to indicate a nested directory structure in
> ApplicationFolderName?
> 
> Examples do not show how to do a nested directory structure.  
> 
> My directory structure looks like this, where the product is nested
> inside a folder named for the company, as there are many other products.
> 
> 
>  
>   
>
>
>   
>  
> 
> 
> In  I added
>  
> 
> Can ApplicationFolderName look like this, where I spell out the directory 
> nesting?
>   Value="$(var.MyCompanyName)\$(var.MyProductName) $(var.Version)" />
> 
> Is this the right way to do it or is there something better?
> 
> Additionally, the dialog does not look exactly like a drop in
> replacement for the simple radio selection bettween per-user vs
> system-wide provided in the  Visual Studio Setup Project.  Is there a
> way to get that behavior?
> 
> 
> 
> NOTICE: This email may contain confidential information.  Please see 
> http://www.meyersound.com/confidential/ for our complete policy.
> 
> --
> 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=58040911&iu=/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=58040911&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] using WixUI_Advanced

[jo...@msli.com]

Tracking the UIRef

MyProject.wxs: line 63:   

Custom_Advanced.wxs: line 121: 

Wix source:
src/ext/UIExtension/wixlib/Common.wxs: line 20: 

So should I comment out the WixUI_Common reference?

On Thu, 2013-08-29 at 22:08 +, John Cooper wrote:
> Well, since you've got both the standard and the custom file referenced in 
> your error messages, it looks like you're linking in both UI's.  Find the 
> duplicate UIRef element and remove it.
> 
> --
> 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: jo...@msli.com [mailto:jo...@msli.com] 
> Sent: Thursday, August 29, 2013 4:47 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] using WixUI_Advanced
> 
> Has anyone had success copying WixUI_Advanced.wxs to a Custom_Advanced.wxs 
> and using it in your msi installer?
> 
> I end up with lots of errors like these:
> 
>  [exec] 
> C:\cygwin\home\build\current\EUROPA\Source\wix_project\Custom_Advanced.wxs(37)
>  : error LGHT0091 : Duplicate symbol 
> 'CustomAction:WixSetDefaultPerUserFolder' found. This typically means that an 
> Id is duplicated. Check to make sure all your identifiers of a given type 
> (File, Component, Feature) are unique.
>  [exec] 
> E:\delivery\Dev\wix37_public\src\ext\UIExtension\wixlib\WixUI_Advanced.wxs(37)
>  : error LGHT0092 : Location of symbol related to previous error.
>  [exec] 
> E:\delivery\Dev\wix37_public\src\ext\UIExtension\wixlib\WixUI_Advanced.wxs(38)
>  : error LGHT0091 : Duplicate symbol 
> 'CustomAction:WixSetDefaultPerMachineFolder' found. This typically means that 
> an Id is duplicated. Check to make sure all your identifiers of a given type 
> (File, Component, Feature) are unique.
>  [exec] 
> C:\cygwin\home\build\current\EUROPA\Source\wix_project\Custom_Advanced.wxs(38)
>  : error LGHT0092 : Location of symbol related to previous error.
>  [exec] 
> C:\cygwin\home\build\current\EUROPA\Source\wix_project\Custom_Advanced.wxs(37)
>  : error LGHT0091 : Duplicate symbol 
> 'CustomAction:WixSetDefaultPerUserFolder' found. This typically means that an 
> Id is duplicated. Check to make sure all your identifiers of a given type 
> (File, Component, Feature) are unique.
>  [exec] 
> E:\delivery\Dev\wix37_public\src\ext\UIExtension\wixlib\WixUI_Advanced.wxs(37)
>  : error LGHT0092 : Location of symbol related to previous error.
> 
> I copied WixUI_Advanced.wxs to my project directory as Custom_Advanced.wxs, 
> and changed
> From:
> < 
> To:
> > 
> 
> And in my Product element I added 
> 
> 
> What Am I missing?  I'm following the Wix 3.6: A Developer's guide to
> windows Installer XML.
> 
> On Thu, 2013-08-29 at 09:31 -0700, jo...@msli.com wrote:
> > In my wix msi I am giving the user a choice of per-user vs.
> > system-wide.  
> > 
> > What is the best way to indicate a nested directory structure in
> > ApplicationFolderName?
> > 
> > Examples do not show how to do a nested directory structure.  
> > 
> > My directory structure looks like this, where the product is nested
> > inside a folder named for the company, as there are many other products.
> > 
> > 
> >  
> >   
> >
> >
> >   
> >  
> > 
> > 
> > In  I added
> >  
> > 
> > Can ApplicationFolderName look like this, where I spell out the directory 
> > nesting?
> >   > Value="$(var.MyCompanyName)\$(var.MyProductName) $(var.Version)" />
> > 
> > Is this the right way to do it or is there something better?
> > 
> > Additionally, the dialog does not look exactly like a drop in
> > replacement for the simple radio selection bettween per-user vs
> > system-wide provided in the  Visual Studio Setup Project.  Is there a
> > way to get that behavior?
> > 
> > 
> > 
> > NOTICE: This email may contain confidential information.  Please see 
> > http://www.meyersound.com/confidential/ for our complete policy.
> > 
> > --
> > 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!
> > ht

Re: [WiX-users] using WixUI_Advanced

[jo...@msli.com]

Yes.  Commenting out WixUI_Common reference did not help.

On Thu, 2013-08-29 at 19:09 -0400, Alain Forget wrote:
> You can try, but I'm thinking a lot of references to things in the Commons 
> are going to break.
> 
> -Original Message-----
> From: jo...@msli.com [mailto:jo...@msli.com] 
> Sent: Thursday, August 29, 2013 18:35
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] using WixUI_Advanced
> 
> Tracking the UIRef
> 
> MyProject.wxs: line 63:   
> 
> Custom_Advanced.wxs: line 121: 
> 
> Wix source:
> src/ext/UIExtension/wixlib/Common.wxs: line 20: 
> 
> So should I comment out the WixUI_Common reference?
> 
> On Thu, 2013-08-29 at 22:08 +, John Cooper wrote:
> > Well, since you've got both the standard and the custom file referenced in 
> > your error messages, it looks like you're linking in both UI's.  Find the 
> > duplicate UIRef element and remove it.
> > 
> > --
> > 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: jo...@msli.com [mailto:jo...@msli.com] 
> > Sent: Thursday, August 29, 2013 4:47 PM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] using WixUI_Advanced
> > 
> > Has anyone had success copying WixUI_Advanced.wxs to a Custom_Advanced.wxs 
> > and using it in your msi installer?
> > 
> > I end up with lots of errors like these:
> > 
> >  [exec] 
> > C:\cygwin\home\build\current\EUROPA\Source\wix_project\Custom_Advanced.wxs(37)
> >  : error LGHT0091 : Duplicate symbol 
> > 'CustomAction:WixSetDefaultPerUserFolder' found. This typically means that 
> > an Id is duplicated. Check to make sure all your identifiers of a given 
> > type (File, Component, Feature) are unique.
> >  [exec] 
> > E:\delivery\Dev\wix37_public\src\ext\UIExtension\wixlib\WixUI_Advanced.wxs(37)
> >  : error LGHT0092 : Location of symbol related to previous error.
> >  [exec] 
> > E:\delivery\Dev\wix37_public\src\ext\UIExtension\wixlib\WixUI_Advanced.wxs(38)
> >  : error LGHT0091 : Duplicate symbol 
> > 'CustomAction:WixSetDefaultPerMachineFolder' found. This typically means 
> > that an Id is duplicated. Check to make sure all your identifiers of a 
> > given type (File, Component, Feature) are unique.
> >  [exec] 
> > C:\cygwin\home\build\current\EUROPA\Source\wix_project\Custom_Advanced.wxs(38)
> >  : error LGHT0092 : Location of symbol related to previous error.
> >  [exec] 
> > C:\cygwin\home\build\current\EUROPA\Source\wix_project\Custom_Advanced.wxs(37)
> >  : error LGHT0091 : Duplicate symbol 
> > 'CustomAction:WixSetDefaultPerUserFolder' found. This typically means that 
> > an Id is duplicated. Check to make sure all your identifiers of a given 
> > type (File, Component, Feature) are unique.
> >  [exec] 
> > E:\delivery\Dev\wix37_public\src\ext\UIExtension\wixlib\WixUI_Advanced.wxs(37)
> >  : error LGHT0092 : Location of symbol related to previous error.
> > 
> > I copied WixUI_Advanced.wxs to my project directory as Custom_Advanced.wxs, 
> > and changed
> > From:
> > < 
> > To:
> > > 
> > 
> > And in my Product element I added 
> > 
> > 
> > What Am I missing?  I'm following the Wix 3.6: A Developer's guide to
> > windows Installer XML.
> > 
> > On Thu, 2013-08-29 at 09:31 -0700, jo...@msli.com wrote:
> > > In my wix msi I am giving the user a choice of per-user vs.
> > > system-wide.  
> > > 
> > > What is the best way to indicate a nested directory structure in
> > > ApplicationFolderName?
> > > 
> > > Examples do not show how to do a nested directory structure.  
> > > 
> > > My directory structure looks like this, where the product is nested
> > > inside a folder named for the company, as there are many other products.
> > > 
> > > 
> > >  
> > >   
> > >
> > >
> > >   
> > >  
> > > 
> > > 
> > > In  I added
> > >  
> > > 
> > > Can ApplicationFolderName look like this, where I spell out the directory 
> > > nesting?
> > >   > > Value="$(var.MyCompanyName)\$(var.

Re: [WiX-users] using WixUI_Advanced

[jo...@msli.com]

I grep'ed for it and found only one UIRef in my code.

I'm trying to follow this with wix 3.7:
http://wixtoolset.org/documentation/manual/v3/wixui/wixui_customizations.html
Changing the UI sequence of a built-in dialog set

But just copying WixUI_Advanced.wxs to a new file name in my project and
changing the UI Id leads to this error:

  
E:\delivery\Dev\wix37_public\src\ext\UIExtension\wixlib\WixUI_Advanced.wxs(37) 
: error LGHT0091 : Duplicate symbol 'CustomAction:WixSetDefaultPerUserFolder' 
found. This typically means that an Id is duplicated. Check to make sure all 
your identifiers of a given type (File, Component, Feature) are unique.
  
C:\cygwin\home\build\current\EUROPA\Source\wix_project\MyProgram.WixUI_MyAdvanced.wxs(37)
 : error LGHT0092 : Location of symbol related to previous error.
  ...


If I change my light.exe command line, by removing
   -ext WixUIExtension
I get Unresolved reference to symbol errors:
  error LGHT0094 : Unresolved reference to symbol 'Dialog:BrowseDlg' 
  
but no duplicates.

If I comment out my modified WixUI_Advanced
  
I get no errors, but I don't get the dialogs.

My modified WixUI_Advanced.wxs  (named MyProgram.WixUI_MyAdvanced.wxs)
has one change:
from:

to:


This is myProgram.wxs:


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








  

  
  

  




  
  
  
  
  
  


























  
  

  

On Thu, 2013-08-29 at 16:55 -0700, Edwin Castro wrote:
> There must be a  somewhere in your project
> OR in a wixlib you are referencing... You might try grep WixUI_Advanced
> (or equivalent) on all the files in your project and all referenced WiX
> projects.
> 
> --
> Edwin G. Castro
> 
> On 8/29/13 3:34 PM, jo...@msli.com wrote:
> > Tracking the UIRef
> >
> > MyProject.wxs: line 63:   
> >
> > Custom_Advanced.wxs: line 121: 
> >
> > Wix source:
> > src/ext/UIExtension/wixlib/Common.wxs: line 20: 
> >
> > So should I comment out the WixUI_Common reference?
> >
> > On Thu, 2013-08-29 at 22:08 +, John Cooper wrote:
> >> Well, since you've got both the standard and the custom file referenced in 
> >> your error messages, it looks like you're linking in both UI's.  Find the 
> >> duplicate UIRef element and remove it.
> >>
> >> --
> >> 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: jo...@msli.com [mailto:jo...@msli.com] 
> >> Sent: Thursday, August 29, 2013 4:47 PM
> >> To: General discussion for Windows Installer XML toolset.
> >> Subject: Re: [WiX-users] using WixUI_Advanced
> >>
> >> Has anyone had success copying WixUI_Advanced.wxs to a Custom_Advanced.wxs 
> >> and using it in your msi installer?
> >>
> >> I end up with lots of errors like these:
> >>
> >>  [exec] 
> >> C:\cygwin\home\build\current\EUROPA\Source\wix_project\Custom_Advanced.wxs(37)
> >>  : error LGHT0091 : Duplicate symbol 
> >> 'CustomAction:WixSetDefaultPerUserFolder' found. This typically means that 
> >> an Id is duplicated. Check to make sure all your identifiers of a given 
> >> type (File, Component, Feature) are unique.
> >>  [exec] 
> >> E:\delivery\Dev\wix37_public\src\ext\UIExtension\wixlib\WixUI_Advanced.wxs(37)
> >>  : error LGHT0092 : Location of symbol related to previous error.
> >>  [exec] 
> >> E:\delivery\Dev\wix37_public\src\ext\UIExtension\wixlib\WixUI_Advanced.wxs(38)
> >>  : error LGHT0091 : Duplicate symbol 
> >> 'CustomAction:WixSetDefaultPerMachineFolder' found. This typically means 
> >> that an Id is duplicated. Check to make sure all your identifiers of a 
> >> given type (File, Component, Feature) are unique.
> >>  [exec] 
> >> C:\cygwin\home\build\current\EUROPA\Source\wix_project\Custom_Advanced.wxs(38)
> &g

Re: [WiX-users] using WixUI_Advanced

[jo...@msli.com]

Found and Solved the issue modifying WixUI_Advanced.wxs

A comment by MarcusUA in the following URL states the issue:
 http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html

The 'CustomAction's in WixUI_Advanced.wxs must be renamed or else they
will result in conflicting names in the original WixUI_Advanced.wxs, so
it's some sort of scope issue with CustomAction.

I stopped having issues after making the following replacements through
out the file:
WixSetDefaultPerUserFolder  to WixSetDefaultPerUserFolder2
WixSetDefaultPerMachineFolder to WixSetDefaultPerMachineFolder2
WixSetPerUserFolder to WixSetPerUserFolder2
WixSetPerMachineFolder to WixSetPerMachineFolder2

Now I can change things around.

On Thu, 2013-08-29 at 18:50 -0700, jo...@msli.com wrote:
> I grep'ed for it and found only one UIRef in my code.
> 
> I'm trying to follow this with wix 3.7:
> http://wixtoolset.org/documentation/manual/v3/wixui/wixui_customizations.html
> Changing the UI sequence of a built-in dialog set
> 
> But just copying WixUI_Advanced.wxs to a new file name in my project and
> changing the UI Id leads to this error:
> 
>   
> E:\delivery\Dev\wix37_public\src\ext\UIExtension\wixlib\WixUI_Advanced.wxs(37)
>  : error LGHT0091 : Duplicate symbol 
> 'CustomAction:WixSetDefaultPerUserFolder' found. This typically means that an 
> Id is duplicated. Check to make sure all your identifiers of a given type 
> (File, Component, Feature) are unique.
>   
> C:\cygwin\home\build\current\EUROPA\Source\wix_project\MyProgram.WixUI_MyAdvanced.wxs(37)
>  : error LGHT0092 : Location of symbol related to previous error.
>   ...
> 
> 
> If I change my light.exe command line, by removing
>-ext WixUIExtension
> I get Unresolved reference to symbol errors:
>   error LGHT0094 : Unresolved reference to symbol 'Dialog:BrowseDlg' 
>   
> but no duplicates.
> 
> If I comment out my modified WixUI_Advanced
>   
> I get no errors, but I don't get the dialogs.
> 
> My modified WixUI_Advanced.wxs  (named MyProgram.WixUI_MyAdvanced.wxs)
> has one change:
> from:
> 
> to:
> 
> 
> This is myProgram.wxs:
> 
> 
> http://schemas.microsoft.com/wix/2006/wi";
> xmlns:bal="http://schemas.microsoft.com/wix/BalExtension";
> xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";
> >
>  Id="*"
>   Language="1033"
>   Manufacturer="$(var.MyCompanyName)"
>   Name="$(var.MyInstallerName)"
>   UpgradeCode="{$(var.Guid_Upgrade)}"
>   Version="$(var.Version)"
>   >
>   
>Comments="My Products - $(var.MyProductName) $(var.Version) 
> Installation"
> Compressed="yes"
> Description="$(var.MyDescription)"
> InstallerVersion="301"
>   />
>   
>   
>   
> 
>   
>   
> 
>ShortName="livl8li5">
> 
> 
>   
> 
>   
> 
>   
>   
> 
> 
> 
> 
> 
> 
>   
> 
>   
>   
>   
>   
>   
> 
>   
>   
>   
>   
> 
>   
>   
> 
>Value="$(var.MyCompanyNameShort)\$(var.MyProductName) $(var.Version)" />
> 
>   
> 
> 
>   
>AllowDowngrades="yes"
> Schedule="afterInstallValidate" />
> 
>   
>   
> Minimum="$(var.Version)"
>OnlyDetect="yes"
>Property="NEWERVERSIONDETECTED"
>   />
> Minimum="0.0.0"
>Maximum="$(var.Version)"
>IncludeMinimum="no"
>IncludeMaximum="no"
>Property="OLDERVERSIONBEINGUPGRADED"
> />
>   
>   
> 
> On Thu, 2013-08-29 at 16:55 -0700, Edwin Castro wrote:
> > There must be a  somewhere in your project
> > OR in a wixlib you are referencing... You might try grep WixUI_Advanced
> > (or equivalent) on all the files in your project and all referenced WiX
> > projects.
> > 
> > --
> > Edwin G. Castro
> > 
> > On 8/29/13 3:34 PM, jo...@msli.com wrote:
> > > Tracking the UIRef
> > >
> > > MyProject.wxs: line 63:   
> > >
> > > Custom_Advanced.wxs: line 121: 
> > >
> > > Wix 

Re: [WiX-users] Add install InstallScopeDlg to WixUI_InstallDir.wxs

[jo...@msli.com]

Thank you for your concern, but Yes, I do want the per-user/per-machine
choice in my installer.
- Only clients Windows 7 or higher are to be supported.
- I only perform major upgrades.
- The Setup Project msi allows this choice and thats what I'm replacing,
so it must also offer the choice.

Have you a WixUI_*.xml that adds to WixUI_InstallDir.wxs a
per-user/per-machine choice?

On Fri, 2013-08-30 at 18:18 +, John Cooper wrote:
> Although being able to specify perUser or perMachine is superficially very 
> appealing, it has significant implications for patching and upgrading that 
> are unacceptable in many deployment scenarios.
> 
> Make sure you're will to live with ALL of those implications.  In my 
> experience, too many products are deployed perMachine, but network 
> administrators have certain expectations about who can patch and upgrade 
> across a network or over a farm that perUser breaks (in particular, there's a 
> nearly universal expectation that they can see all installed products from an 
> appropriately permissioned user).
> 
> Also, I believe this is only really going to work if you limited yourself to 
> installing on Windows Installer Service 5.0 or later.  Will that work for 
> you?  For example, that will totally cut out support for XP and Server 2003.
> 
> --
> 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: jo...@msli.com [mailto:jo...@msli.com] 
> Sent: Friday, August 30, 2013 12:59 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] Add install InstallScopeDlg to WixUI_InstallDir.wxs
> 
> Hay anyone modified WixUI_InstallDir.wxs to enable a per-user vs.
> per-machine install?
> 
> I really like the flow of WixUI_InstallDir, but I need to add an install 
> scope (per-user vs per-machine), to make it more like the old VS Setup 
> Project.
> 
> I am trying to take pars of WixUI_Advanced.wxs and add them to a copy of 
> WixUI_InstallDir.wxs, but before I go too deep, I'm wondering if anyone else 
> has done this, or is there a better way?  
> 
> 
> NOTICE: This email may contain confidential information.  Please see 
> http://www.meyersound.com/confidential/ for our complete policy.
> 
> --
> 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=58040911&iu=/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=58040911&iu=/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=58040911&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Add install InstallScopeDlg to WixUI_InstallDir.wxs

[jo...@msli.com]

Hay anyone modified WixUI_InstallDir.wxs to enable a per-user vs.
per-machine install?

I really like the flow of WixUI_InstallDir, but I need to add an install
scope (per-user vs per-machine), to make it more like the old VS Setup
Project.

I am trying to take pars of WixUI_Advanced.wxs and add them to a copy of
WixUI_InstallDir.wxs, but before I go too deep, I'm wondering if anyone
else has done this, or is there a better way?  


NOTICE: This email may contain confidential information.  Please see 
http://www.meyersound.com/confidential/ for our complete policy.

--
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=58040911&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Add install InstallScopeDlg to WixUI_InstallDir.wxs

[jo...@msli.com]

I think that's 4 reasons. :)

I am trying to make an installer that replaces the VS2010 Setup Project
installer, as stated in my first post, and it allows one to set the path
and offers both the per-user/per-machine install on the same dialog.

So does anyone know how wix differs from VS2010 setup project for the
per-user vs. per-machine install choice?

Are they equivalent?

I have spent a bit of time to make my wix dialog look like the setup
project version, but now the functionality seems totally wonky, as no
matter what the user puts into their path, this per-user setup will
change the path to something different.  Ar!

On Fri, 2013-08-30 at 20:24 +, John Cooper wrote:
> Well conceptually, you don't need the InstallDir dialog if you're installing 
> perUser as it's always going into the LocalAppData tree anyway.  It's a 
> pretty straight forward translation of WixUI_Advanced.  Even the somewhat 
> troublesome custom actions could be moved to another file since they run 
> scheduled in both the Execute and UI sequences.
> 
> About two hours of work and most of it to verify functionality.
> 
> No, I don't have ready-made source for you.
> 
> I've modified FeatureTree, Mondo, and InstallDir extensively, but I've never 
> done.  Advanced.  Two reasons:  1) management wants compatibility with 
> Windows Installer Service 4.5 and the ability to install on late service 
> packs of XP and Server 2003 (with Windows Installer Service 4.5 installed on 
> them); 2) management wants 100% visibility of all installed products on all 
> machines by one account; 3) management wants patching and upgrading to behave 
> in the same manner (e.g., under one account); and 4) management wants GPO 
> deployability.
> 
> Just because software has a capability doesn't mean it should be used.  There 
> should be a business justification for it.
> 
> --
> 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: jo...@msli.com [mailto:jo...@msli.com] 
> Sent: Friday, August 30, 2013 2:16 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Add install InstallScopeDlg to WixUI_InstallDir.wxs
> 
> Thank you for your concern, but Yes, I do want the per-user/per-machine 
> choice in my installer.
> - Only clients Windows 7 or higher are to be supported.
> - I only perform major upgrades.
> - The Setup Project msi allows this choice and thats what I'm replacing, so 
> it must also offer the choice.
> 
> Have you a WixUI_*.xml that adds to WixUI_InstallDir.wxs a 
> per-user/per-machine choice?
> 
> On Fri, 2013-08-30 at 18:18 +, John Cooper wrote:
> > Although being able to specify perUser or perMachine is superficially very 
> > appealing, it has significant implications for patching and upgrading that 
> > are unacceptable in many deployment scenarios.
> > 
> > Make sure you're will to live with ALL of those implications.  In my 
> > experience, too many products are deployed perMachine, but network 
> > administrators have certain expectations about who can patch and upgrade 
> > across a network or over a farm that perUser breaks (in particular, there's 
> > a nearly universal expectation that they can see all installed products 
> > from an appropriately permissioned user).
> > 
> > Also, I believe this is only really going to work if you limited yourself 
> > to installing on Windows Installer Service 5.0 or later.  Will that work 
> > for you?  For example, that will totally cut out support for XP and Server 
> > 2003.
> > 
> > --
> > 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: jo...@msli.com [mailto:jo...@msli.com]
> > Sent: Friday, August 30, 2013 12:59 PM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: [WiX-users] Add install InstallScopeDlg to 
> > WixUI_InstallDir.wxs
> > 
> > Hay anyone modified WixUI_InstallDir.wxs to enable a per-user vs.
> > per-machine install?
> > 
> > I really like the flow of WixUI_InstallDir, but I need to add an install 
> > scope (per-user vs per-machine), to make it more like the old VS Setup 
> > Project.
> > 
> > I am trying to 

[WiX-users] my icon absent from add/remove programs

[jo...@msli.com]

My .wxs file contains the following line:
  

which is supposed to set the icon seen in add/remove program, but I only
see the default icon for my application.

Are there requirements on MyApp.ico for it to be used in add/remove
program? 


Currently I use an ImageMagick tool to convert it from a tiff to a ico.
convert "MyApp.tiff" -format "ICON" "MyApp.ico"
 
Another ImageMagick tool shows the icon file details.
MyApp.ico ICO 32x32 32x32+0+0 DirectClass 8-bit 4.18555kb


I imagine if the icon could not be found candle would die, but it does
not.


NOTICE: This email may contain confidential information.  Please see 
http://www.meyersound.com/confidential/ for our complete policy.

--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] my icon absent from add/remove programs

[jo...@msli.com]

On Fri, 2010-02-26 at 10:47 +0530, Lisa Gracias wrote:
> On Fri, Feb 26, 2010 at 5:26 AM, jo...@msli.com  wrote:
> 
> > My .wxs file contains the following line:
> >  
> >
> 
> 
> You need to set the path to the icon inside an  element and give it a
> unique id. Then use the icon id inside your property tag.
> 
> 

That worked!  Thank you!

In several places I get away with just using a path without creating a
special element and id.  I did come across what you propose in searching
for help, but I guessed the  element was not significant to make
this work.  I was wrong.


NOTICE: This email may contain confidential information.  Please see 
http://www.meyersound.com/confidential/ for our complete policy.

--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] error: system cannot open the device or file specified

[jo...@msli.com]

I am trying to setup a new wix project, but I am running into a few
problems and would love some help.

Below I include links to my wxs, wxi, ant build, and install logs so
that you may save me from this fiery hell.

Link to resources:https://gist.github.com/johnstile/5595744
It includes:
 build.xml : ant script calling heat, candle, light, and msiexec.
 MyProgram.wxs : wix project file
 MyProgram.variables.wxi - variables file
 msi_install_log.txt - my failing install log
 build_log.txt - output from running: ant light

First issue: 

All my installers fail with error:

 "The system cannot open the device or file specified."

 See: msi_install_log.txt 
 it isn't empty, and the paths look sane.
 What's the problem?

Second issue:

 heat warns about 5 files files, with errors like:

heat.exe : warning HEAT5150 : Could not harvest data from a file that
was expected to be a SelfReg DLL: C:\cygwin\home\build\current\EUROPA
\ProgramFiles\WinPcap_4_1_2.exe. If this file does not support SelfReg
you can ignore this warning. Otherwise, this error detail may be helpful
to diagnose the failure: Unable to load file: C:\cygwin\home\build
\current\EUROPA\ProgramFiles\WinPcap_4_1_2.exe, error: 5

 See: build_log.txt

 I need to distribute this exe as part of my installer, and there are
other exe's as well.  My installer will have to offer to install the
other programs if they are not installed already.

Third issue:

  I can't get preprocessor includes to read my wxi files.
  Either it errors with a path problem: 

C:\cygwin\home\build\current\EUROPA\Source\Compass.wxs(2) : error
CNDL0103 : The system cannot find the file 'Source/Compass.variables.wxi
' with type 'include'.Source trace:
C:\cygwin\home\build\current\EUROPA\Source\Compass.wxs: line 2

  Or it says my file is invalid.
  See: MyProgram.variables.wxi

Fourth issue:

  I can't get find a wild card for light to use all wixobj files under
the wixobj directory generated by candle.

Thank you for taking a look.


NOTICE: This email may contain confidential information.  Please see 
http://www.meyersound.com/confidential/ for our complete policy.

--
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] error: system cannot open the device or file specified

[jo...@msli.com]

Nothing is encrypted, so the link didn't help, though I did see that
'solution' before.

Per your request, I removed all the variables, simplified the problem to
one wxs file, packaging 2 text files, no variables, and I still get the
error system cannot open the device or file specified.

The command line:
 candle -v -trace MyProgram.wxs 
 light -o MyProgram.msi MyProgram.wixobj 
 msiexec.exe /i MyProgram.msi /l*v msi_install_log.txt

My MyProgram.wxs:
-

http://schemas.microsoft.com/wix/2006/wi";>
  








  

  
  

  




  
  


  





  

  



  

  


 

  




On Fri, 2013-05-17 at 11:05 +0100, David Watson wrote:
> 1) This http://support.microsoft.com/kb/834549 ?
> 2) Heat thinks the .exe is a com server, as it is another installer you can
> ignore it. If you are bundling several packages together you may want to look
> at the burn bootstrapper which will handle this much better than embedding
> the sub installers in an msi.
> 3&4) Try manually running the compilation from the command line and
> hardcoding some values until you work out which bit is wrong, or add
> everything to a wixproj / solution if you have that option.
> 
> 
> -Original Message-
> From: jo...@msli.com [mailto:jo...@msli.com] 
> Sent: 17 May 2013 00:16
> To: WixUsers
> Subject: [WiX-users] error: system cannot open the device or file specified
> 
> I am trying to setup a new wix project, but I am running into a few problems
> and would love some help.
> 
> Below I include links to my wxs, wxi, ant build, and install logs so that you
> may save me from this fiery hell.
> 
> Link to resources:https://gist.github.com/johnstile/5595744
> It includes:
>  build.xml : ant script calling heat, candle, light, and msiexec.
>  MyProgram.wxs : wix project file
>  MyProgram.variables.wxi - variables file  msi_install_log.txt - my failing
> install log  build_log.txt - output from running: ant light
> 
> First issue: 
> 
> All my installers fail with error:
> 
>  "The system cannot open the device or file specified."
> 
>  See: msi_install_log.txt
>  it isn't empty, and the paths look sane.
>  What's the problem?
> 
> Second issue:
> 
>  heat warns about 5 files files, with errors like:
> 
> heat.exe : warning HEAT5150 : Could not harvest data from a file that was
> expected to be a SelfReg DLL: C:\cygwin\home\build\current\EUROPA
> \ProgramFiles\WinPcap_4_1_2.exe. If this file does not support SelfReg you
> can ignore this warning. Otherwise, this error detail may be helpful to
> diagnose the failure: Unable to load file: C:\cygwin\home\build
> \current\EUROPA\ProgramFiles\WinPcap_4_1_2.exe, error: 5
> 
>  See: build_log.txt
> 
>  I need to distribute this exe as part of my installer, and there are other
> exe's as well.  My installer will have to offer to install the other programs
> if they are not installed already.
> 
> Third issue:
> 
>   I can't get preprocessor includes to read my wxi files.
>   Either it errors with a path problem: 
> 
> C:\cygwin\home\build\current\EUROPA\Source\Compass.wxs(2) : error
> CNDL0103 : The system cannot find the file 'Source/Compass.variables.wxi '
> with type 'include'.Source trace:
> C:\cygwin\home\build\current\EUROPA\Source\Compass.wxs: line 2
> 
>   Or it says my file is invalid.
>   See: MyProgram.variables.wxi
> 
> Fourth issue:
> 
>   I can't get find a wild card for light to use all wixobj files under the
> wixobj directory generated by candle.
> 
> Thank you for taking a look.
> 
> 
> NOTICE: This email may contain confidential information.  Please see
> http://www.meyersound.com/confidential/ for our complete policy.
> 
> -
> -
> AlienVault Unified Security Management (USM) platform delivers complete
> security visibility with the essential security capabilities. Easily and
> efficiently configure, manage, and operate all of your security controls from
> a single console and one unified framework. Download a free trial.
> http://p.sf.net/sfu/alienvault_d2d
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> SDL PLC confidential, all rights reserved.
> If you are not the intended recipient of this mail SDL requests and requires 
> that you delete it without acting upon or copying any of its contents, and we 
> further request that you advise u

Re: [WiX-users] error: system cannot open the device or file specified

[jo...@msli.com]

Phil, 
  You are a genius!  I dragged the MyProgram.msi to the desktop, double
clicked the msi, and it installed! Happy Day.
  Permissions address issue 1.

  So why are the permissions wrong, and how to I solve this?

  From cygwin or cmd, built via ant or calling wix commands directly,
trying to run the msi (by double-click in Explorer, or msiexec.exe from
cmd) results in this error.  If I copy the file to the desktop it does
not have this problem.  

Permissions of original product of wix light.exe:
cacls MyProgram.msli
  MyProgram.msi build-PC\build:(ID)F
build-PC\None:(ID)(special access:)
  READ_CONTROL
  SYNCHRONIZE
  FILE_READ_ATTRIBUTES
  Everyone:(ID)F

Permissions of copy to the desktop:
  MyProgram.msi NT AUTHORITY\SYSTEM:F
BUILTIN\Administrators:F
build-PC\build:F

>From cygwin if I set permissions, I can install the file:
  chmod 777 MyProgram.msli
Permissions after chmod:
MyProgram.msi build-PC\build:(special access:)
 STANDARD_RIGHTS_ALL
 DELETE
 READ_CONTROL
 WRITE_DAC
 WRITE_OWNER
 SYNCHRONIZE
 STANDARD_RIGHTS_REQUIRED
 FILE_GENERIC_READ
 FILE_GENERIC_WRITE
 FILE_GENERIC_EXECUTE
 FILE_READ_DATA
 FILE_WRITE_DATA
 FILE_APPEND_DATA
 FILE_READ_EA
 FILE_WRITE_EA
 FILE_EXECUTE
 FILE_READ_ATTRIBUTES
 FILE_WRITE_ATTRIBUTES

  build-PC\None:(special access:)
READ_CONTROL
SYNCHRONIZE
FILE_GENERIC_READ
FILE_GENERIC_WRITE
FILE_GENERIC_EXECUTE
FILE_READ_DATA
FILE_WRITE_DATA
FILE_APPEND_DATA
FILE_READ_EA
FILE_WRITE_EA
FILE_EXECUTE
FILE_READ_ATTRIBUTES
FILE_WRITE_ATTRIBUTES

  Everyone:(special access:)
   READ_CONTROL
   SYNCHRONIZE
   FILE_GENERIC_READ
   FILE_GENERIC_WRITE
   FILE_GENERIC_EXECUTE
   FILE_READ_DATA
   FILE_WRITE_DATA
   FILE_APPEND_DATA
   FILE_READ_EA
   FILE_WRITE_EA
   FILE_EXECUTE
   FILE_READ_ATTRIBUTES
   FILE_WRITE_ATTRIBUTES

On Fri, 2013-05-17 at 09:09 -0700, Phil Wilson wrote:
> Take a look at that folder and the file at
> C:\cygwin\home\build\current\EUROPA\MyProgram.msi .
> 
> That looks like a user-created folder, and it seems that the install fails
> as soon as it switches to the service to do the install. That file/folder
> may not allow access by the SYSTEM account. 
> 
> Phil 
> 
> -----Original Message-
> From: jo...@msli.com [mailto:jo...@msli.com] 
> Sent: Friday, May 17, 2013 8:08 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] error: system cannot open the device or file
> specified
> 
> Nothing is encrypted, so the link didn't help, though I did see that
> 'solution' before.
> 
> Per your request, I removed all the variables, simplified the problem to one
> wxs file, packaging 2 text files, no variables, and I still get the error
> system cannot open the device or file specified.
> 
> The command line:
>  candle -v -trace MyProgram.wxs
>  light -o MyProgram.msi MyProgram.wixobj  msiexec.exe /i MyProgram.msi /l*v
> msi_install_log.txt
> 
> My MyProgram.wxs:
> -
> 
> http://schemas.microsoft.com/wix/2006/wi";>
>Id="*"
> Language="1033"
> Manufacturer="My Company, Inc."
> Name="MyProgram 1.0.0"
> UpgradeCode="{759DF56C-50E2-49B7-AFFF-296826685B58}"
> Version="1.0.0"
>   >
> 
>Comments="My Products - MyProgram 1.0.0 Installation"
>   Compressed="yes"
>   Description="MyProgram 1.0.0 digital product view and control program"
>   InstallerVersion="301"
>   InstallScope=&qu

Re: [WiX-users] error: system cannot open the device or file specified

[jo...@msli.com]

Found a workaround to permissions issues.
  icalcs MyProgram.msli /grant Everyone:(F)
Not sure why it's an issue, but this gets around it. 

On Fri, 2013-05-17 at 13:03 -0700, jo...@msli.com wrote:
> Phil, 
>   You are a genius!  I dragged the MyProgram.msi to the desktop, double
> clicked the msi, and it installed! Happy Day.
>   Permissions address issue 1.
> 
>   So why are the permissions wrong, and how to I solve this?
> 
>   From cygwin or cmd, built via ant or calling wix commands directly,
> trying to run the msi (by double-click in Explorer, or msiexec.exe from
> cmd) results in this error.  If I copy the file to the desktop it does
> not have this problem.  
> 
> Permissions of original product of wix light.exe:
> cacls MyProgram.msli
>   MyProgram.msi build-PC\build:(ID)F
> build-PC\None:(ID)(special access:)
>   READ_CONTROL
>   SYNCHRONIZE
>   FILE_READ_ATTRIBUTES
>   Everyone:(ID)F
> 
> Permissions of copy to the desktop:
>   MyProgram.msi NT AUTHORITY\SYSTEM:F
> BUILTIN\Administrators:F
> build-PC\build:F
> 
> >From cygwin if I set permissions, I can install the file:
>   chmod 777 MyProgram.msli
> Permissions after chmod:
> MyProgram.msi build-PC\build:(special access:)
>  STANDARD_RIGHTS_ALL
>  DELETE
>  READ_CONTROL
>  WRITE_DAC
>  WRITE_OWNER
>  SYNCHRONIZE
>  STANDARD_RIGHTS_REQUIRED
>  FILE_GENERIC_READ
>  FILE_GENERIC_WRITE
>  FILE_GENERIC_EXECUTE
>  FILE_READ_DATA
>  FILE_WRITE_DATA
>  FILE_APPEND_DATA
>  FILE_READ_EA
>  FILE_WRITE_EA
>  FILE_EXECUTE
>  FILE_READ_ATTRIBUTES
>  FILE_WRITE_ATTRIBUTES
> 
>   build-PC\None:(special access:)
> READ_CONTROL
> SYNCHRONIZE
> FILE_GENERIC_READ
> FILE_GENERIC_WRITE
> FILE_GENERIC_EXECUTE
> FILE_READ_DATA
> FILE_WRITE_DATA
> FILE_APPEND_DATA
> FILE_READ_EA
> FILE_WRITE_EA
> FILE_EXECUTE
> FILE_READ_ATTRIBUTES
> FILE_WRITE_ATTRIBUTES
> 
>   Everyone:(special access:)
>READ_CONTROL
>SYNCHRONIZE
>FILE_GENERIC_READ
>FILE_GENERIC_WRITE
>FILE_GENERIC_EXECUTE
>FILE_READ_DATA
>FILE_WRITE_DATA
>FILE_APPEND_DATA
>FILE_READ_EA
>FILE_WRITE_EA
>FILE_EXECUTE
>FILE_READ_ATTRIBUTES
>FILE_WRITE_ATTRIBUTES
> 
> On Fri, 2013-05-17 at 09:09 -0700, Phil Wilson wrote:
> > Take a look at that folder and the file at
> > C:\cygwin\home\build\current\EUROPA\MyProgram.msi .
> > 
> > That looks like a user-created folder, and it seems that the install fails
> > as soon as it switches to the service to do the install. That file/folder
> > may not allow access by the SYSTEM account. 
> > 
> > Phil 
> > 
> > -Original Message-
> > From: jo...@msli.com [mailto:jo...@msli.com] 
> > Sent: Friday, May 17, 2013 8:08 AM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] error: system cannot open the device or file
> > specified
> > 
> > Nothing is encrypted, so the link didn't help, though I did see that
> > 'solution' before.
> > 
> > Per your request, I removed all the variables, simplified the problem to one
> > wxs file, packaging 2 text files, no variables, and I still get the error
> > system cannot open the device or file specified.
> > 
> > The command line:
> >  candle -v -trace MyProgram.wxs
> >  light -o MyProgram.msi MyProgram.wixobj  msiexec.exe /i MyProgram.ms

[WiX-users] bootstrap a proxy install

[jo...@msli.com]

I am looking for a boiler plate example of using wix to make an
installer than can conditionally run another msi installer, to ease the
user experience.

I am making an installer for a program that has a run-time requirement
for a proxy, and I bundle the proxy msi in my wix installer.  If the
proxy is not installed, I would like the wix installer to run the proxy
msi, and optimally allow the user to choose weather or not to run the
proxy msi. 

I haven't made it all the way thought the documentation or book, "Wix
3.6: A Developer's Guide to Windows Installer XML", but I am pretty far,
and can't see the light at the end of the tulle.

Can anyone post a boiler plate example of this popular question?


NOTICE: This email may contain confidential information.  Please see 
http://www.meyersound.com/confidential/ for our complete policy.

--
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] help controlling uninstall bundle behavior

[jo...@msli.com]

I need some help finding a good behavior for uninstalling using bundles.

My bundle installs 4 things (wxs at end of this message):
 Two ExePackage, 
 Two MsiPackage

>From "Control Panel"->"Programs and Features", 
I see an entry for each item in my chain, which I like.

I also see multiple entries for my bundle, which I don't like as it
could confuse the users.

Additionally, Uninstalling the bundle does not uninstall the items in
the chain, it simply removes the bundle from "Control Panel"->"Programs
and Features" which seems like busy work.

My ignorant view, and please correct me if I'm wrong, thinks users will
be confused by seeing bundle in "Control Panel"->"Programs and
Features", in addition to the chained packages, so maybe it should not
be there, as it has no functional purpose.

I see two Bundle attributes:
 DisableModify  
 DisableRemove
which seem to address hiding my bundle in "Control Panel"->"Programs and
Features", but not cleanly?

http://wix.sourceforge.net/manual-wix3/wix_xsd_bundle.htm
says I just find some other way to clean out my bundle, but no examples
given.

Has anyone found a nice recipe for dealing with bundles?

My Wxs for the Bundle follows:


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

  https://mycopany.com/software/compass?section=support";
UpdateUrl="https://mycompany.com/software/compass?section=download";
AboutUrl="https://mycompany.com/software/compass?section=overview";

SplashScreenSourceFile="../ProgramFiles/Resources/Images/InstallerHeaderImage.bmp"
  >



  https://www.meyersound.com/software/compass?section=download";
LogoFile="../Source/Resources/Images/AboutCompass.png"
  />
















  
  http://www.winpcap.org/install/bin/WinPcap_4_1_3.exe";
InstallCondition="NOT WinPcapInstalled OR ( 4 >
WinPcapVersionMajor AND 1 > WinPcapVersionMinor)"
  >

  
  
  http://support.apple.com/downloads/DL999/en_US/BonjourPSSetup.exe";
InstallCondition="NOT BonjourDLL OR v2.0.2.0 > BonjourVersion"
  >

  
  
  
  
  

  




NOTICE: This email may contain confidential information.  Please see 
http://www.meyersound.com/confidential/ for our complete policy.

--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] help controlling uninstall bundle behavior

[jo...@msli.com]

After much reading, I am trying to use bundle the wrong way.  

By design the bundle is the unified user interface to the stuff
installed.

Instead I will simply let the bundle appear in "Programs and Features",
and hide everything that will be uninsulated by the bundle.

Some 3rd party ExePackages don't want to uninstall via the bundle
anyway.

On Thu, 2013-06-13 at 09:34 -0700, jo...@msli.com wrote:
> I need some help finding a good behavior for uninstalling using bundles.
> 
> My bundle installs 4 things (wxs at end of this message):
>  Two ExePackage, 
>  Two MsiPackage
> 
> >From "Control Panel"->"Programs and Features", 
> I see an entry for each item in my chain, which I like.
> 
> I also see multiple entries for my bundle, which I don't like as it
> could confuse the users.
> 
> Additionally, Uninstalling the bundle does not uninstall the items in
> the chain, it simply removes the bundle from "Control Panel"->"Programs
> and Features" which seems like busy work.
> 
> My ignorant view, and please correct me if I'm wrong, thinks users will
> be confused by seeing bundle in "Control Panel"->"Programs and
> Features", in addition to the chained packages, so maybe it should not
> be there, as it has no functional purpose.
> 
> I see two Bundle attributes:
>  DisableModify  
>  DisableRemove
> which seem to address hiding my bundle in "Control Panel"->"Programs and
> Features", but not cleanly?
> 
> http://wix.sourceforge.net/manual-wix3/wix_xsd_bundle.htm
> says I just find some other way to clean out my bundle, but no examples
> given.
> 
> Has anyone found a nice recipe for dealing with bundles?
> 
> My Wxs for the Bundle follows:
> 
> 
> http://schemas.microsoft.com/wix/2006/wi";
> xmlns:bal="http://schemas.microsoft.com/wix/BalExtension";
> xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";
> >
> 
>Name="$(var.BundleExe)"
> Version="1.0.0.0"
> Manufacturer="$(var.MyCompanyName)"
> Copyright="(c) All rights reserved."
> UpgradeCode="{$(var.Guid_Bundle)}"
> HelpTelephone="1 234 567 8910"
> HelpUrl="https://mycopany.com/software/compass?section=support";
> UpdateUrl="https://mycompany.com/software/compass?section=download";
> AboutUrl="https://mycompany.com/software/compass?section=overview";
> 
> SplashScreenSourceFile="../ProgramFiles/Resources/Images/InstallerHeaderImage.bmp"
>   >
> 
> 
>Id="WixStandardBootstrapperApplication.HyperlinkLicense">
>
> LicenseUrl="https://www.meyersound.com/software/compass?section=download";
> LogoFile="../Source/Resources/Images/AboutCompass.png"
>   />
> 
> 
> 
> 
>Id="RegistrySearchWinPcapHas" 
>   Variable="WinPcapInstalled"
>   Root="HKLM"
> Key="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
> \WinPcapInst"
>   Result="exists"
> />
>Id="RegistrySearchWinPcapMajor" 
>   Variable="WinPcapVersionMajor"
>   Root="HKLM"
> Key="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
> \WinPcapInst"
>   Value="VersionMajor"
>   Format="raw"
>   Result="value"
> />
>Id="RegistrySearchWinPcapMinor" 
>   Variable="WinPcapVersionMinor"
>   Root="HKLM"
> Key="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
> \WinPcapInst"
>   Value="VersionMinor"
>   Format="raw"
>   Result="value"
> />
> 
>Id="RegistrySearchBonjourHas" 
>   Variable="BonjourDLL"
>   Root="HKLM"
> Key="SOFTWARE\Classes\AppID\Bonjour.DLL"
>   Result="exists"
> />
>Id="RegistrySearchBonjourValue" 
>   Variable="BounjourVersion"
>   Root="HKLM"
> Key="SOFTWARE\Apple Inc.\Bonjour"
>   Value="Version"
>   Format="raw"
>   Result="value"
> />
> 
>Id="RegistrySearchProxyHas" 
>   Variable="ProxyInstalled"
>   Root="HKLM"
> Key="SOFTWARE\Meyer Sound\AVDECC Proxy"
>   Result="exists"
&g

[WiX-users] bundle installed multiple times

[jo...@msli.com]

Is there a way to prevent a bundle from being installed multiple times?
I see many entries in "Programs and Features".

My bundle wxs:

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

  




  
















  
  http://www.winpcap.org/install/bin/WinPcap_4_1_3.exe";
InstallCondition="NOT WinPcapInstalled OR ( 4 > WinPcapVersionMajor AND 
1 > WinPcapVersionMinor)"
Permanent="yes"
  >

  
  
  http://support.apple.com/downloads/DL999/en_US/BonjourPSSetup.exe";
InstallCondition="NOT BonjourDLL OR v2.0.2.0 > BonjourVersion"
Permanent="yes"
  >

  
  
  
  
  

  




NOTICE: This email may contain confidential information.  Please see 
http://www.meyersound.com/confidential/ for our complete policy.

--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] bundle installed multiple times

[jo...@msli.com]

Incrementing Version for every single bundle is going to be problematic.
Everyone will have to track and increment this Version or suffer
duplicate entries in "Programs and Features".

If I build and install my bundle (with version=1.0.0), then build and
install my bundle again (with version=1.0.0), I get duplicate entries in
"Programs and Features", even though the second bundle did not install
anything since everything is already installed, and all of the payload
remains the same.

My msi has a guid that prevents this form happening.

Is there no way to prevent duplicate entries?

On Fri, 2013-06-14 at 21:27 -0700, Rob Mensching wrote:
> Increment the version so the new ones remove the old ones?
> 
> 
> On Fri, Jun 14, 2013 at 6:17 PM, jo...@msli.com  wrote:
> 
> > Is there a way to prevent a bundle from being installed multiple times?
> > I see many entries in "Programs and Features".
> >
> > My bundle wxs:
> > 
> > http://schemas.microsoft.com/wix/2006/wi";
> > xmlns:bal="http://schemas.microsoft.com/wix/BalExtension";
> > xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";
> > >
> >
> >> Name="$(var.MyInstallerName)"
> > Version="$(var.Version)"
> > Manufacturer="$(var.MyCompanyName)"
> > Copyright="(c) All rights reserved."
> > UpgradeCode="{$(var.Guid_Bundle)}"
> > HelpTelephone="$(var.HelpPhone)"
> > HelpUrl="$(var.HelpUrl)"
> > UpdateUrl="$(var.UpdateUrl)"
> > AboutUrl="$(var.AboutUrl)"
> > Condition="((VersionNT >= v5.1) AND (ServicePackLevel >= 3)) OR
> > ((VersionNT >= v5.2) AND (ServicePackLevel >= 2)) OR (VersionNT >= v6.0)"
> > IconSourceFile="$(var.ProdIcon)"
> >   >
> >
> > 
> >  >   Id="WixStandardBootstrapperApplication.HyperlinkLicense"
> > >
> >> LicenseUrl="EULA.html"
> > LogoFile="$(var.ProdIcon)"
> > SuppressRepair="yes"
> > SuppressOptionsUI="yes"
> >   />
> >   
> > 
> >
> > 
> > 
> >  >   Id="RegistrySearchWinPcapHas"
> >   Variable="WinPcapInstalled"
> >   Root="HKLM"
> >
> > Key="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\WinPcapInst"
> >   Result="exists"
> > />
> >  >   Id="RegistrySearchWinPcapMajor"
> >   Variable="WinPcapVersionMajor"
> >   Root="HKLM"
> >
> > Key="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\WinPcapInst"
> >   Value="VersionMajor"
> >   Format="raw"
> >   Result="value"
> > />
> >  >   Id="RegistrySearchWinPcapMinor"
> >   Variable="WinPcapVersionMinor"
> >   Root="HKLM"
> >
> > Key="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\WinPcapInst"
> >   Value="VersionMinor"
> >   Format="raw"
> >   Result="value"
> > />
> > 
> >  >   Id="RegistrySearchBonjourHas"
> >   Variable="BonjourDLL"
> >   Root="HKLM"
> > Key="SOFTWARE\Classes\AppID\Bonjour.DLL"
> >   Result="exists"
> > />
> >  >   Id="RegistrySearchBonjourValue"
> >   Variable="BounjourVersion"
> >   Root="HKLM"
> > Key="SOFTWARE\Apple Inc.\Bonjour"
> >   Value="Version"
> >   Format="raw"
> >   Result="value"
> > />
> > 
> >  >   Id="RegistrySearchProxyHas"
> >   Variable="ProxyInstalled"
> >   Root="HKLM"
> > Key="SOFTWARE\Meyer Sound\AVDECC Proxy"
> >   Result="exists"
> > />
> > 
> >
> > 
> > 
> >   
> >> Id="WinPcap"
> > Name="WinPcap_4_1_3.exe"
> > Vital="no"
> > Compressed="no"
> > DownloadUrl="http://www.winpcap.org/install/bin/WinPcap_4_1_3.exe";
> > InstallCondition="NOT WinPcapInstalled OR ( 4 >

Re: [WiX-users] bundle installed multiple times

[jo...@msli.com]

I don't understand. 

If a bundle fails to install everything in the chain, why does it add it
self to "Programs and Features"?

If I already have Version 1.0.0 of a bundle installed, why would it add
another entry for Version 1.0.0?

Is there some way to use WixBundleInstalle to reject the install of
another Version 1.0.0?

Part of the development cycle is making the bundle at some version, and
incrementing Version on each attempt seems too easy to result in
duplicate entries to "Programs and Features".  There seems to be no way
to protect against this eventuality.

On Mon, 2013-06-17 at 11:21 -0700, Rob Mensching wrote:
> The general expectation is that when you make a new build, you'll increment
> the version. The WiX toolset's Bundle increments based on the date (we
> don't do multiple builds in the same day).
> 
> You could write a custom BA to allow "same version upgrades". Burn engine
> doesn't have support for that yet today.
> 
> The current experience is identical to the MSI behavior if you don't set
> allow same version upgrades.
> 
> 
> On Mon, Jun 17, 2013 at 10:55 AM, jo...@msli.com  wrote:
> 
> > Incrementing Version for every single bundle is going to be problematic.
> > Everyone will have to track and increment this Version or suffer
> > duplicate entries in "Programs and Features".
> >
> > If I build and install my bundle (with version=1.0.0), then build and
> > install my bundle again (with version=1.0.0), I get duplicate entries in
> > "Programs and Features", even though the second bundle did not install
> > anything since everything is already installed, and all of the payload
> > remains the same.
> >
> > My msi has a guid that prevents this form happening.
> >
> > Is there no way to prevent duplicate entries?
> >
> > On Fri, 2013-06-14 at 21:27 -0700, Rob Mensching wrote:
> > > Increment the version so the new ones remove the old ones?
> > >
> > >
> > > On Fri, Jun 14, 2013 at 6:17 PM, jo...@msli.com  wrote:
> > >
> > > > Is there a way to prevent a bundle from being installed multiple times?
> > > > I see many entries in "Programs and Features".
> > > >
> > > > My bundle wxs:
> > > > 
> > > > http://schemas.microsoft.com/wix/2006/wi";
> > > > xmlns:bal="http://schemas.microsoft.com/wix/BalExtension";
> > > > xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";
> > > > >
> > > >
> > > >> > > Name="$(var.MyInstallerName)"
> > > > Version="$(var.Version)"
> > > > Manufacturer="$(var.MyCompanyName)"
> > > > Copyright="(c) All rights reserved."
> > > > UpgradeCode="{$(var.Guid_Bundle)}"
> > > > HelpTelephone="$(var.HelpPhone)"
> > > > HelpUrl="$(var.HelpUrl)"
> > > > UpdateUrl="$(var.UpdateUrl)"
> > > > AboutUrl="$(var.AboutUrl)"
> > > > Condition="((VersionNT >= v5.1) AND (ServicePackLevel >= 3)) OR
> > > > ((VersionNT >= v5.2) AND (ServicePackLevel >= 2)) OR (VersionNT >=
> > v6.0)"
> > > > IconSourceFile="$(var.ProdIcon)"
> > > >   >
> > > >
> > > > 
> > > >  > > >   Id="WixStandardBootstrapperApplication.HyperlinkLicense"
> > > > >
> > > >> > > LicenseUrl="EULA.html"
> > > > LogoFile="$(var.ProdIcon)"
> > > > SuppressRepair="yes"
> > > > SuppressOptionsUI="yes"
> > > >   />
> > > >   
> > > > 
> > > >
> > > > 
> > > > 
> > > >  > > >   Id="RegistrySearchWinPcapHas"
> > > >   Variable="WinPcapInstalled"
> > > >   Root="HKLM"
> > > >
> > > > Key="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\WinPcapInst"
> > > >   Result="exists"
> > > > />
> > > >  > > >   Id="RegistrySearchWinPcapMajor"
> > > >   Variable="WinPcapVersionMajor"
> > > >   Root="HKLM"
> > > >
> > > > Key="SOFTWARE\Mi

Re: [WiX-users] bundle installed multiple times

[jo...@msli.com]

I built my bundle, and ran it, which installed everything in the chain.
Then I rebuilt my bundle, and ran it, without incrementing Version,
which installed nothing, except it did add itself to "Programs and
Features".  I now see two entries for the same Version of the installer:
one that actually installed stuff, one that installed nothing.

Are you are saying it should have rolled back or not added an entry?

Although not normal, since I did not manually increment Version, it
should not have add a second entry in "Programs and Features", so it
sounds like it is broken.  When would that ever be a useful behavior?  I
am using the standard WixStandardBootstrapperApplication.  Seems like
the WixStandardBootstrapperApplication should know better.

My Version policy for bundles doesn't exist yet, as I am learning to
work with wix bundles.  Normally I have a version for my application,
and it does not change from the target release name.  Wix seems to
require a Version for the bundle it self, which seems like a strange
maintenance step, and I don't see the usefulness yet.  I would rather
just create bundles, and have logic in each bundle to decide what to
install, and if nothing installs, not add an entry for the bundle in
"Programs and Features".

On Mon, 2013-06-17 at 12:20 -0700, Rob Mensching wrote:
> 1. If a Bundle fails to install everything in the chain, it should rollback
> and not have anything left in ARP.
> 
> 2. If you want it to block, your BA would need to do that. If you're using
> wixstdba, I think it automatically blocks downgrades. IIRC, it doesn't
> block same versions because that's not a normal user scenario. It should
> only happen in dev scenarios where one forgot to accidentally remove
> previous build.
> 
> 3. It depends on what BA you are using.
> 
> You can do whatever you want with your versioning policy in a BA. It isn't
> quite clear to me what versioning policy you're using. When do you change
> the version number?
> 
> 
> On Mon, Jun 17, 2013 at 11:41 AM, jo...@msli.com  wrote:
> 
> > I don't understand.
> >
> > If a bundle fails to install everything in the chain, why does it add it
> > self to "Programs and Features"?
> >
> > If I already have Version 1.0.0 of a bundle installed, why would it add
> > another entry for Version 1.0.0?
> >
> > Is there some way to use WixBundleInstalle to reject the install of
> > another Version 1.0.0?
> >
> > Part of the development cycle is making the bundle at some version, and
> > incrementing Version on each attempt seems too easy to result in
> > duplicate entries to "Programs and Features".  There seems to be no way
> > to protect against this eventuality.
> >
> > On Mon, 2013-06-17 at 11:21 -0700, Rob Mensching wrote:
> > > The general expectation is that when you make a new build, you'll
> > increment
> > > the version. The WiX toolset's Bundle increments based on the date (we
> > > don't do multiple builds in the same day).
> > >
> > > You could write a custom BA to allow "same version upgrades". Burn engine
> > > doesn't have support for that yet today.
> > >
> > > The current experience is identical to the MSI behavior if you don't set
> > > allow same version upgrades.
> > >
> > >
> > > On Mon, Jun 17, 2013 at 10:55 AM, jo...@msli.com  wrote:
> > >
> > > > Incrementing Version for every single bundle is going to be
> > problematic.
> > > > Everyone will have to track and increment this Version or suffer
> > > > duplicate entries in "Programs and Features".
> > > >
> > > > If I build and install my bundle (with version=1.0.0), then build and
> > > > install my bundle again (with version=1.0.0), I get duplicate entries
> > in
> > > > "Programs and Features", even though the second bundle did not install
> > > > anything since everything is already installed, and all of the payload
> > > > remains the same.
> > > >
> > > > My msi has a guid that prevents this form happening.
> > > >
> > > > Is there no way to prevent duplicate entries?
> > > >
> > > > On Fri, 2013-06-14 at 21:27 -0700, Rob Mensching wrote:
> > > > > Increment the version so the new ones remove the old ones?
> > > > >
> > > > >
> > > > > On Fri, Jun 14, 2013 at 6:17 PM, jo...@msli.com 
> > wrote:
> > > > >
> > > > > > Is there a way to prevent a bundle from being in

[WiX-users] Finding previous install in the registry from a bundle

[jo...@msli.com]

I am trying to create a bundle to install an msi that does not support
upgrades, but no warning is shown to the user.  If I try to run the msi
by hand, I see the error "Another version of ... ", but running the
bundle just shows a random guid for the msi is being processed, the
bundle completes without error, and the application remains at it's
previous version.

How can I alert the user, or better ... uninstall the previous version
before installing the new one?

There is nothing I can easily search for in the registry, as the msi
uses a random guid for each revision.  While the upgrade code remains
the same, I searched the registry and did not find neither hide nor hair
of it.  If I am to detect the previous installed version I need a way to
find the current installation.


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

  




  
















  
  http://www.winpcap.org/install/bin/WinPcap_4_1_3.exe";
InstallCondition="NOT WinPcapInstalled OR ( 4 > WinPcapVersionMajor AND 
1 > WinPcapVersionMinor)"
Permanent="yes"
  >

  
  
  http://support.apple.com/downloads/DL999/en_US/BonjourPSSetup.exe";
InstallCondition="NOT BonjourDLL OR v2.0.2.0 > BonjourVersion"
Permanent="yes"
  >

  
  
  
  
  

  




NOTICE: This email may contain confidential information.  Please see 
http://www.meyersound.com/confidential/ for our complete policy.

--
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] reinstall major upgrade removes files yet installed

[jo...@msli.com]

For the longest time I have had a wix msi and bundle that I could
upgrade or downgrade without having to uninstall first, before
installing the version I want to test.

Now it seems if a previous install exists, the bundle (or msi) will
remove the files from the previous install, and mark the program
installed in ARP.  In this state, I have to uninstall and then reinstall
in order to get the files and mark the program installed in ARP.

If I install on a system without the program, everything installs as
expected.

This behavior change seems to coenside with my building the program with
dynamic linking (vs. static linking), which called for the inclusion of
Microsoft Redistributables.

It is very handy for a user to just install without having to un-install
first, so i would like to keep that experience.

Bellow find my msi and bundle wxs files.
---
MyProgram.wxs   (msi)
---


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








  
  

  
  

  








  
  
  
  
  
  









INSTALLDIR


















  
  

  

-
MyProgram.bundle.wxs (burn bundle)
--


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








  
















  
  http://support.apple.com/downloads/DL999/en_US/BonjourPSSetup.exe";
InstallCondition="NOT BonjourDLL OR v2.0.2.0 > BonjourVersion"
Permanent="yes"
  >

  
  
  http://www.winpcap.org/install/bin/WinPcap_4_1_3.exe";
InstallCondition="NOT WinPcapInstalled OR ( 4 >
WinPcapVersionMajor AND 1 > WinPcapVersionMinor)"
Permanent="yes"
  >

  
  

  




NOTICE: This email may contain confidential information.  Please see 
http://www.meyersound.com/confidential/ for our complete policy.

--
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] reinstall major upgrade removes files yet installed

[jo...@msli.com]

I have posted the logs
https://gist.github.com/johnstile/aed128a3dd268b008f4a


On Tue, 2014-07-22 at 03:21 +, Hoover, Jacob wrote:
> Posting links to logs of the downgrade (both the uninstall and the install 
> logs) would help deduce the actual problem. The bundle logs detect and 
> planning sections of the logs would be the first place to look.
> 
> -Original Message-
> From: jo...@msli.com [mailto:jo...@msli.com] 
> Sent: Monday, July 21, 2014 6:09 PM
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: [WiX-users] reinstall major upgrade removes files yet installed
> 
> For the longest time I have had a wix msi and bundle that I could upgrade or 
> downgrade without having to uninstall first, before installing the version I 
> want to test.
> 
> Now it seems if a previous install exists, the bundle (or msi) will remove 
> the files from the previous install, and mark the program installed in ARP.  
> In this state, I have to uninstall and then reinstall in order to get the 
> files and mark the program installed in ARP.
> 
> If I install on a system without the program, everything installs as expected.
> 
> This behavior change seems to coenside with my building the program with 
> dynamic linking (vs. static linking), which called for the inclusion of 
> Microsoft Redistributables.
> 
> It is very handy for a user to just install without having to un-install 
> first, so i would like to keep that experience.
> 
> Bellow find my msi and bundle wxs files.
> ---
> MyProgram.wxs   (msi)
> ---
> 
> 
> http://schemas.microsoft.com/wix/2006/wi";
> xmlns:bal="http://schemas.microsoft.com/wix/BalExtension";
> xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";
> >
>Id="*"
> Language="1033"
> Manufacturer="$(var.MyCompanyName)"
> Name="$(var.MyInstallerName)"
> UpgradeCode="{$(var.Guid_Upgrade)}"
> Version="$(var.Version)"
>   >
> 
>Comments="$(var.MyCompanyNameShort) - $(var.MyProductName)
> $(var.Version) Installation"
>   Compressed="yes"
>   Description="$(var.MyDescription)"
>   InstallerVersion="301"
> />
> 
> 
> 
> 
> 
> 
>src="$(env.CommonProgramFiles(x86))\Merge Modules 
> \Microsoft_VC100_CRT_x86.msm"/>
>   
>  Name="$(var.MyCompanyNameShort)" ShortName="livl8li5">
>   
>   
> 
>   
> 
> 
>  AllowAdvertise="no" Display="hidden" Level="1">
> 
> 
> 
> 
> 
>   
>   
>   
>   
>   
>   
> 
> 
> 
> 
> 
> 
> 
> 
> 
> INSTALLDIR
> 
> 
> 
> 
> 
> 
> 
>  Value="$(var.MyCompanyNameShort)\$(var.MyProductName) $(var.Version)" />
> 
> 
> 
> 
> 
> 
>AllowDowngrades="yes"
>   Schedule="afterInstallValidate" />
> 
> 
> 
> Minimum="$(var.Version)"
>  OnlyDetect="yes"
>  Property="NEWERVERSIONDETECTED"
> />
> Minimum="0.0.0"
>  Maximum="$(var.Version)"
>  IncludeMinimum="no"
>  IncludeMaximum="no"
>  Property="OLDERVERSIONBEINGUPGRADED"
>   />
> 
>   
> 
> -
> MyProgram.bundle.wxs (burn bundle)
> --
> 
> 
> http://schemas.microsoft.com/wix/2006/wi";
> xmlns:bal="http://schemas.microsoft.com/wix/BalExtension";
> xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";
> >
>Name="$(var.MyInstallerName)"
> Version="$(var.BundleVersion)"
> Manufacturer="$(var.MyCompanyName)"
> Copyright="$(var.Copyright)"
> UpgradeCode="$(var.Guid_Bundle)"
> HelpTelephone="$(var.HelpPhone)"
> HelpUrl="$(v

[WiX-users] Unresolved reference to symbol 'WixUI:WixUI_ErrorProgressText

[jo...@msli.com]

I newbie using wix3.0.5419.0, and I am having a problem finding the Wix
UI library.  I have read WixUIExtension.dll is in the directory where I
installed Wix, and all I need to do is run light.exe, and the library
will be found.  Some say A full path to light.exe might be required.
 
In my wxs, in the  tag, I have:
INSTALLDIR



These are the incantations:
candle.exe MyApp.wxs  MyApp.fragment.wxs-ext  WixUtilExtension
light.exe -sval MyApp.wixobj MyApp.fragment.wixobj -ext  WixUtilExtension -o 
MyApp.msi

The error:
MyApp.wxs(24) : error LGHT0094 : Unresolved reference to symbol 
'WixUI:WixUI_InstallDir' in section 'Product:*'.
MyApp.wxs(25) : error LGHT0094 : Unresolved reference to symbol 
'WixUI:WixUI_ErrorProgressText' in section 'Product:*'.

I tried from cygwin and cmd, with full paths to Wix directory and
without full paths, but the outcome is always the same.

It would be great if there was some environment variable I could set.

Can you see anything wrong with what I am trying to do?


CONFIDENTIALITY NOTICE:  This electronic mail message and any attachment hereto 
may contain confidential information of Meyer Sound Laboratories, Incorporated 
and is intended for the personal and confidential use of the designated 
recipient(s) only.  If you are not the intended recipient (or responsible for 
delivering the message to the intended recipient), you have received this 
message in error and any review, distribution, or copying of this message or 
any attachment hereto is prohibited.  If you have received this message in 
error, please promptly notify the sender and permanently delete it from your 
computer.

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] end up with emtpy msi

[jo...@msli.com]

I am using wix3.0.5419.0 to generate an msi from 2 wxs files (first sets
project, second sets files in a  tag), but the resulting msi
is too small and doesn't work.

Incantations to generate msi in my build product directory:
Paraffin.exe -dir '.\.' -custom "MyApp" -g -alias '.\' -ext '.WXS' 
MyApp.fragment.wxs
candle.exe MyApp.wxs MyApp.fragment.wxs' -ext WixUIExtension.dll
light -sval  MyApp.wixobj MyApp.fragment.wixobj -o MyApp.msi -ext  
WixUIExtension.dll

I used dark to de-construct the resulting msi into wxs, which only
contains the first wxs and none of the second wxs.  I also used dark's
-x, and the resulting File directory is empty, so I am missing some step
to load files into the msi.

The first wxs is created by hand, and the second wxs is created by
Paraffin3.0, and contains all my files.  As an experiment, I joined both
into one wxs file and then tried to build, which errors:
MyApp.wxs(2310) : error LGHT0094 : Unresolved reference to symbol 'Media:1' in 
section 'Product:{20A1EE0E-832E-4541-9C9B-6527AB358F76}'.

Incantation:  
candle.exe MyApp.wxs  -cultures:en-us  -ext WixUIExtension.dll
light -sval MyApp.wixobj -o MyApp.msi -cultures:en-us -ext  WixUIExtension.dll


I am new to wix, but looking at other people's wxs files, I see a line 

What makes this cab file?
Is it necessary?
Is this why i get the error above?

In the wix docs, and searching the net,  I don't see a step in the
procedure to create a cab file, and my msi is definitely empty.

I feel like I need to be steered in the right direction.  
Is there a wix tool that makes the cab? 
Or am I supposed to deal with wix after making the cab file?  



CONFIDENTIALITY NOTICE:  This electronic mail message and any attachment hereto 
may contain confidential information of Meyer Sound Laboratories, Incorporated 
and is intended for the personal and confidential use of the designated 
recipient(s) only.  If you are not the intended recipient (or responsible for 
delivering the message to the intended recipient), you have received this 
message in error and any review, distribution, or copying of this message or 
any attachment hereto is prohibited.  If you have received this message in 
error, please promptly notify the sender and permanently delete it from your 
computer.

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] end up with emtpy msi

[jo...@msli.com]

I had to learn to pull in the fragments.
Thank you very much.
I didn't have to create my own cab file.

In MyApp.wxs, I added to 

  


In MyApp.fragment.wxs, group_MyApp is defined as a 
  
and hold all the files.

Finally, I had to add to MyApp.wxs









The installer does install. :))
But it doesn't un-install all the directories, and the App doesn't work once 
installed, so I have more learning.

On Wed, 2009-07-22 at 13:56 -0700, Alexander Shevchuk wrote:
> As far as Media element, this can help:
> http://blogs.technet.com/alexshev/archive/2008/04/04/from-msi-to-wix-part-16
> -installable-items-handling-installation-media.aspx 
> 
> I have suspicion that wxs files created by Paraffin contain fragments and in
> order to include content of fragment to resulting msi you need to reference
> something from fragment in your main wxs file. Search for elements like
> FeatureRef, ComponentRef, PropertyRef, etc.
> 
> Alex
> 
> 
> 
> 
> 
> -Original Message-
> From: jo...@msli.com [mailto:jo...@msli.com] 
> Sent: Wednesday, July 22, 2009 1:38 PM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] end up with emtpy msi
> 
> I am using wix3.0.5419.0 to generate an msi from 2 wxs files (first sets
> project, second sets files in a  tag), but the resulting msi
> is too small and doesn't work.
> 
> Incantations to generate msi in my build product directory:
> Paraffin.exe -dir '.\.' -custom "MyApp" -g -alias '.\' -ext '.WXS'
> MyApp.fragment.wxs
> candle.exe MyApp.wxs MyApp.fragment.wxs' -ext WixUIExtension.dll
> light -sval  MyApp.wixobj MyApp.fragment.wixobj -o MyApp.msi -ext
> WixUIExtension.dll
> 
> I used dark to de-construct the resulting msi into wxs, which only
> contains the first wxs and none of the second wxs.  I also used dark's
> -x, and the resulting File directory is empty, so I am missing some step
> to load files into the msi.
> 
> The first wxs is created by hand, and the second wxs is created by
> Paraffin3.0, and contains all my files.  As an experiment, I joined both
> into one wxs file and then tried to build, which errors:
> MyApp.wxs(2310) : error LGHT0094 : Unresolved reference to symbol 'Media:1'
> in section 'Product:{20A1EE0E-832E-4541-9C9B-6527AB358F76}'.
> 
> Incantation:  
> candle.exe MyApp.wxs  -cultures:en-us  -ext WixUIExtension.dll
> light -sval MyApp.wixobj -o MyApp.msi -cultures:en-us -ext
> WixUIExtension.dll
> 
> 
> I am new to wix, but looking at other people's wxs files, I see a line 
>  />
> What makes this cab file?
> Is it necessary?
> Is this why i get the error above?
> 
> In the wix docs, and searching the net,  I don't see a step in the
> procedure to create a cab file, and my msi is definitely empty.
> 
> I feel like I need to be steered in the right direction.  
> Is there a wix tool that makes the cab? 
> Or am I supposed to deal with wix after making the cab file?  
> 
> 
> 
> CONFIDENTIALITY NOTICE:  This electronic mail message and any attachment
> hereto may contain confidential information of Meyer Sound Laboratories,
> Incorporated and is intended for the personal and confidential use of the
> designated recipient(s) only.  If you are not the intended recipient (or
> responsible for delivering the message to the intended recipient), you have
> received this message in error and any review, distribution, or copying of
> this message or any attachment hereto is prohibited.  If you have received
> this message in error, please promptly notify the sender and permanently
> delete it from your computer.
> 
> 
> --
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 
> --
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users


CONFIDENTIALITY NOTICE:  This electronic mail message and any attachment hereto 
may contain confidential information of Meyer Sound Laboratories, Incorporated 
and is intended for the personal and confidential use of the designated 
recipient(s) only.  If you are not the intended recipient (or responsible for 
delivering the message to the intended recipient), you have received this 
message in error and any review, distribution, or copying of this 

[WiX-users] how to force uninstall before install

[jo...@msli.com]

I am going thought the process of making msi's for new versions of my
software.
I would like to force the user to uninstall before installing the new
version, so I would like some install dialog to stop them there.
Where can I find some info on doing this?


CONFIDENTIALITY NOTICE:  This electronic mail message and any attachment hereto 
may contain confidential information of Meyer Sound Laboratories, Incorporated 
and is intended for the personal and confidential use of the designated 
recipient(s) only.  If you are not the intended recipient (or responsible for 
delivering the message to the intended recipient), you have received this 
message in error and any review, distribution, or copying of this message or 
any attachment hereto is prohibited.  If you have received this message in 
error, please promptly notify the sender and permanently delete it from your 
computer.

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] correctly define preprocessor var in wxs?

[jo...@msli.com]

I have been struggling to find one simple example of defining a
preprocessor variable in the wxs file.

Currently, If I Append this to my candle command line:
   -dMyVar='foo.exe'
then references to $(var.MyVar) in wxs work.
But no matter how I define MyVar in the main wxs, they are not found.

Why does this not work, defined in my main project wxs?



Until that works, I can't hope to reach my goal of using an environment
variable (ExeName):







CONFIDENTIALITY NOTICE:  This electronic mail message and any attachment hereto 
may contain confidential information of Meyer Sound Laboratories, Incorporated 
and is intended for the personal and confidential use of the designated 
recipient(s) only.  If you are not the intended recipient (or responsible for 
delivering the message to the intended recipient), you have received this 
message in error and any review, distribution, or copying of this message or 
any attachment hereto is prohibited.  If you have received this message in 
error, please promptly notify the sender and permanently delete it from your 
computer.

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] correctly define preprocessor var in wxs?

[jo...@msli.com]

I have also tried:


And


  

  


But nothing works.

On Fri, 2009-07-24 at 11:47 -0700, jo...@msli.com wrote:
> I have been struggling to find one simple example of defining a
> preprocessor variable in the wxs file.
> 
> Currently, If I Append this to my candle command line:
>-dMyVar='foo.exe'
> then references to $(var.MyVar) in wxs work.
> But no matter how I define MyVar in the main wxs, they are not found.
> 
> Why does this not work, defined in my main project wxs?
> 
> 
> 
> Until that works, I can't hope to reach my goal of using an environment
> variable (ExeName):
> 
> 
> 
> 
> 
> 
> 
> CONFIDENTIALITY NOTICE:  This electronic mail message and any attachment 
> hereto may contain confidential information of Meyer Sound Laboratories, 
> Incorporated and is intended for the personal and confidential use of the 
> designated recipient(s) only.  If you are not the intended recipient (or 
> responsible for delivering the message to the intended recipient), you have 
> received this message in error and any review, distribution, or copying of 
> this message or any attachment hereto is prohibited.  If you have received 
> this message in error, please promptly notify the sender and permanently 
> delete it from your computer.
> 
> --
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users


CONFIDENTIALITY NOTICE:  This electronic mail message and any attachment hereto 
may contain confidential information of Meyer Sound Laboratories, Incorporated 
and is intended for the personal and confidential use of the designated 
recipient(s) only.  If you are not the intended recipient (or responsible for 
delivering the message to the intended recipient), you have received this 
message in error and any review, distribution, or copying of this message or 
any attachment hereto is prohibited.  If you have received this message in 
error, please promptly notify the sender and permanently delete it from your 
computer.

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] correctly define preprocessor var in wxs?

[jo...@msli.com]

In my main wxs, I have



  


which does cause candle to fail if I comment out the define.

And in a Component, I have 
   Target="[INSTALLDIR]$(var.MyVar)"

If I run candle with out:
  -dMyVar="foo.exe"
I get the error: 
  Undefined preprocessor variable '$(var.MyVar)'.

If I run candle with:
  -dMyVar="foo.exe"
Candle succeeds.

What is my malfunction?

On Fri, 2009-07-24 at 20:00 +0100, Russell Hind wrote:
> To define pre-processor variables (equivelant to -d passed to  
> Candle.exe) use
> 
> 
> 
> Cheers
> 
> Russell
> 
> On 24 Jul 2009, at 19:47, jo...@msli.com wrote:
> 
> > I have been struggling to find one simple example of defining a
> > preprocessor variable in the wxs file.
> >
> > Currently, If I Append this to my candle command line:
> >   -dMyVar='foo.exe'
> > then references to $(var.MyVar) in wxs work.
> > But no matter how I define MyVar in the main wxs, they are not found.
> >
> > Why does this not work, defined in my main project wxs?
> > 
> >
> >
> > Until that works, I can't hope to reach my goal of using an  
> > environment
> > variable (ExeName):
> > 
> > 
> > 
> > 
> > 
> >
> >
> > CONFIDENTIALITY NOTICE:  This electronic mail message and any  
> > attachment hereto may contain confidential information of Meyer  
> > Sound Laboratories, Incorporated and is intended for the personal  
> > and confidential use of the designated recipient(s) only.  If you  
> > are not the intended recipient (or responsible for delivering the  
> > message to the intended recipient), you have received this message  
> > in error and any review, distribution, or copying of this message or  
> > any attachment hereto is prohibited.  If you have received this  
> > message in error, please promptly notify the sender and permanently  
> > delete it from your computer.
> >
> > --
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 
> --
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users


CONFIDENTIALITY NOTICE:  This electronic mail message and any attachment hereto 
may contain confidential information of Meyer Sound Laboratories, Incorporated 
and is intended for the personal and confidential use of the designated 
recipient(s) only.  If you are not the intended recipient (or responsible for 
delivering the message to the intended recipient), you have received this 
message in error and any review, distribution, or copying of this message or 
any attachment hereto is prohibited.  If you have received this message in 
error, please promptly notify the sender and permanently delete it from your 
computer.

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] correctly define preprocessor var in wxs?

[jo...@msli.com]

yes.  specifically I used it as:
  Target="[INSTALLDIR]$(var.MyVar)"

On Fri, 2009-07-24 at 20:07 +0100, Russell Hind wrote:
> On 24 Jul 2009, at 19:59, jo...@msli.com wrote:
> 
> > I have also tried:
> > 
> >
> 
> When you did this, do you use it as:
> 
> $(var.MyVar)
> 
> where you need it?
> 
> Cheers
> 
> Russell
> 
> --
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users


CONFIDENTIALITY NOTICE:  This electronic mail message and any attachment hereto 
may contain confidential information of Meyer Sound Laboratories, Incorporated 
and is intended for the personal and confidential use of the designated 
recipient(s) only.  If you are not the intended recipient (or responsible for 
delivering the message to the intended recipient), you have received this 
message in error and any review, distribution, or copying of this message or 
any attachment hereto is prohibited.  If you have received this message in 
error, please promptly notify the sender and permanently delete it from your 
computer.

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] correctly define preprocessor var in wxs?

[jo...@msli.com]

I appreciate all the help, and I am sorry for not getting.
Based on what I understand your advice to be,
I have moved the preprocessor variables  to a wxi,


 
   
 
 

 


And the second line of each wxs file now contains an include statement:


But I still get the same result.

What seems to work is calling candle.exe using the environment
variables: 
candle.exe MyApp.wxs MyApp.fragment.wxs -ext WixUIExtension.dll -d
-dMyVar="${ExeName}"

But I thought this is supposed to also work:
candle.exe MyApp.wxs MyApp.fragment.wxs -ext WixUIExtension.dll

On Fri, 2009-07-24 at 13:41 -0700, Blair wrote:
> Is your component in main.wxs or in some other file. If it is in main.wxs,
> is it above or below your definition?
> 
>  in wxs works like #define in cpp: you have to define it before
> you use it, and the definition exists for the file it is in (unless included
> in other files). That is why .wxi files exist (see the help for
> ).
> 
> -Original Message-
> From: jo...@msli.com [mailto:jo...@msli.com] 
> Sent: Friday, July 24, 2009 12:19 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] correctly define preprocessor var in wxs?
> 
> In my main wxs, I have
> 
> 
> 
>   
> 
> 
> which does cause candle to fail if I comment out the define.
> 
> And in a Component, I have 
>Target="[INSTALLDIR]$(var.MyVar)"
> 
> If I run candle with out:
>   -dMyVar="foo.exe"
> I get the error: 
>   Undefined preprocessor variable '$(var.MyVar)'.
> 
> If I run candle with:
>   -dMyVar="foo.exe"
> Candle succeeds.
> 
> What is my malfunction?
> 
> On Fri, 2009-07-24 at 20:00 +0100, Russell Hind wrote:
> > To define pre-processor variables (equivelant to -d passed to  
> > Candle.exe) use
> > 
> > 
> > 
> > Cheers
> > 
> > Russell
> > 
> > On 24 Jul 2009, at 19:47, jo...@msli.com wrote:
> > 
> > > I have been struggling to find one simple example of defining a
> > > preprocessor variable in the wxs file.
> > >
> > > Currently, If I Append this to my candle command line:
> > >   -dMyVar='foo.exe'
> > > then references to $(var.MyVar) in wxs work.
> > > But no matter how I define MyVar in the main wxs, they are not found.
> > >
> > > Why does this not work, defined in my main project wxs?
> > > 
> > >
> > >
> > > Until that works, I can't hope to reach my goal of using an  
> > > environment
> > > variable (ExeName):
> > > 
> > > 
> > > 
> > > 
> > > 
> > >
> > >
> > > CONFIDENTIALITY NOTICE:  This electronic mail message and any  
> > > attachment hereto may contain confidential information of Meyer  
> > > Sound Laboratories, Incorporated and is intended for the personal  
> > > and confidential use of the designated recipient(s) only.  If you  
> > > are not the intended recipient (or responsible for delivering the  
> > > message to the intended recipient), you have received this message  
> > > in error and any review, distribution, or copying of this message or  
> > > any attachment hereto is prohibited.  If you have received this  
> > > message in error, please promptly notify the sender and permanently  
> > > delete it from your computer.
> > >
> > >
> 
> --
> > > ___
> > > WiX-users mailing list
> > > WiX-users@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/wix-users
> > 
> > 
> >
> 
> --
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 
> CONFIDENTIALITY NOTICE:  This electronic mail message and any attachment
> hereto may contain confidential information of Meyer Sound Laboratories,
> Incorporated and is intended for the personal and confidential use of the
> designated recipient(s) only.  If you are not the intended recipient (or
> responsible for delivering the message to the intended recipient), you have
> received this message in error and any review, distribution, or copying of
> this message or any attachment hereto is prohibited.  If you have received
> this message in error, please promptly notify the sender and permanently
> delete it from your com

Re: [WiX-users] correctly define preprocessor var in wxs?

[jo...@msli.com]

I meant to say MyApp.variables.wxi, not MyApp.variables.wxs. Sorry. 
I have been working on this too long, my eyes are crossed, and I am
making more type-o's.  I'm trying to sanitize my problem and keep it
concise and problem specific.

When I run the following (all one-line)(run from bash cygwin shell): 
candle.exe
  MyApp.wxs
  MyApp.fragment.wxs
  -ext  WixUIExtension.dll

Results in the error:
MyApp.variables.wxi(12) : error CNDL0250 : MyVar must be defined

But the following (all one-line) (run from bash cygwin shell)
candle.exe
  MyApp.wxs
  MyApp.fragment.wxs
  -ext  WixUIExtension.dll
  -dMyVar="${ExeName}"
It works.

The same is true even if I use cmd shell and 'set ExeName='foo.exe' and
then run candle.exe

The lines in MyApp.variables.wxi







I'm not sure what your last line means.
"...needs to specify the wix namespace..."
I will try to explain.

In my each wxs file, just below line 1 
(the line: 

In the main MyApp.wxs file, I pull in the namespace in my fragment
(generate by Paraffin.exe) MyApp.fragment.wxs




Does that help?

On Fri, 2009-07-24 at 18:17 -0700, Blair wrote:
> Which error are you getting now? ("MyVar must be defined" or "Undefined
> preprocessor variable '$(var.MyVar)'")
> 
> Sorry to ask the obvious, but you appear to be including MyApp.variables.wxs
> but you mention creating a wxi file. Is the wxi file named
> MyApp.variables.wxs? Most of the time wxi files end in ".wxi" not ".wxs".
> 
> Also, IIRC, the Include (since it is the root element) needs to specify the
> wix namespace (not shown in your example).
> 
> -Original Message-
> From: jo...@msli.com [mailto:jo...@msli.com] 
> Sent: Friday, July 24, 2009 4:14 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] correctly define preprocessor var in wxs?
> 
> I appreciate all the help, and I am sorry for not getting.
> Based on what I understand your advice to be,
> I have moved the preprocessor variables  to a wxi,
> 
> 
>  
>
>  
>  
> 
>  
> 
> 
> And the second line of each wxs file now contains an include statement:
> 
> 
> But I still get the same result.
> 
> What seems to work is calling candle.exe using the environment
> variables: 
> candle.exe MyApp.wxs MyApp.fragment.wxs -ext WixUIExtension.dll -d
> -dMyVar="${ExeName}"
> 
> But I thought this is supposed to also work:
> candle.exe MyApp.wxs MyApp.fragment.wxs -ext WixUIExtension.dll
> 
> On Fri, 2009-07-24 at 13:41 -0700, Blair wrote:
> > Is your component in main.wxs or in some other file. If it is in main.wxs,
> > is it above or below your definition?
> > 
> >  in wxs works like #define in cpp: you have to define it before
> > you use it, and the definition exists for the file it is in (unless
> included
> > in other files). That is why .wxi files exist (see the help for
> > ).
> > 
> > -Original Message-
> > From: jo...@msli.com [mailto:jo...@msli.com] 
> > Sent: Friday, July 24, 2009 12:19 PM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] correctly define preprocessor var in wxs?
> > 
> > In my main wxs, I have
> > 
> > 
> > 
> >   
> > 
> > 
> > which does cause candle to fail if I comment out the define.
> > 
> > And in a Component, I have 
> >Target="[INSTALLDIR]$(var.MyVar)"
> > 
> > If I run candle with out:
> >   -dMyVar="foo.exe"
> > I get the error: 
> >   Undefined preprocessor variable '$(var.MyVar)'.
> > 
> > If I run candle with:
> >   -dMyVar="foo.exe"
> > Candle succeeds.
> > 
> > What is my malfunction?
> > 
> > On Fri, 2009-07-24 at 20:00 +0100, Russell Hind wrote:
> > > To define pre-processor variables (equivelant to -d passed to  
> > > Candle.exe) use
> > > 
> > > 
> > > 
> > > Cheers
> > > 
> > > Russell
> > > 
> > > On 24 Jul 2009, at 19:47, jo...@msli.com wrote:
> > > 
> > > > I have been struggling to find one simple example of defining a
> > > > preprocessor variable in the wxs file.
> > > >
> > > > Currently, If I Append this to my candle command line:
> > > >   -dMyVar='foo.exe'
> > > > then references to $(var.MyVar) in wxs work.
> > > > But no matter how I define MyVar in the main wxs, they are not found.
> > > >
> > > > Why does this not work, defined in my main project wxs?
>

Re: [WiX-users] correctly define preprocessor var in wxs?

[jo...@msli.com]

Perfect!  That solved my problem. Thank you.

On Sat, 2009-07-25 at 14:19 -0400, Bob Arnson wrote:
> jo...@msli.com wrote:
> > The lines in MyApp.variables.wxi
> > 
> >   
> 
> Try dropping the $() surrounding it; the $() syntax tells the 
> preprocessor to insert the value but  is expecting a symbol not 
> a value.
> 


CONFIDENTIALITY NOTICE:  This electronic mail message and any attachment hereto 
may contain confidential information of Meyer Sound Laboratories, Incorporated 
and is intended for the personal and confidential use of the designated 
recipient(s) only.  If you are not the intended recipient (or responsible for 
delivering the message to the intended recipient), you have received this 
message in error and any review, distribution, or copying of this message or 
any attachment hereto is prohibited.  If you have received this message in 
error, please promptly notify the sender and permanently delete it from your 
computer.

--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Can ProgId look at header of file to determin file association?

[jo...@msli.com]

My application uses an xml data file, but it seems wrong to use ProgId
to associate all xml files with my app.

Is there some method to use the header in the xml to associate my some
xml files with may app?


CONFIDENTIALITY NOTICE:  This electronic mail message and any attachment hereto 
may contain confidential information of Meyer Sound Laboratories, Incorporated 
and is intended for the personal and confidential use of the designated 
recipient(s) only.  If you are not the intended recipient (or responsible for 
delivering the message to the intended recipient), you have received this 
message in error and any review, distribution, or copying of this message or 
any attachment hereto is prohibited.  If you have received this message in 
error, please promptly notify the sender and permanently delete it from your 
computer.

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users