Re: [WiX-users] SqlScript with large schema setup

[Chad Petersen]

We've run into this. Luckily the one largest SQL script is also the last one we 
need to execute so we removed it from the installer and just have customers run 
that one manually using SQL Management Studio. About 34 seconds to run through 
there while the installer takes an hour and a half to run the same script.

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: Thursday, January 23, 2014 4:39 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SqlScript with large schema setup

Code was originally written sometime around 2001. It hasn't changed really 
since then.

-Original Message-
From: Levi Wilson [mailto:l...@leviwilson.com]
Sent: Thursday, January 23, 2014 2:31 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SqlScript with large schema setup

I'm actually looking at it now :-) I can live with the initial, since that's 
only going to happen the first time you run our installer and our schema is not 
there. On an update (doing major upgrades) we are going to have migration 
scripts run. Those should not be near what this initial one is.

Looking at the code (I just have 3.7, but it doesn't sounds like it's changed 
in awhile) I'm not seeing any tests for any of the parsing in scasqlstr.cpp, 
which intimidates me :-) It's doing a LOT, but mostly looks like it is just 
eating comments and removing "GO" statements to execute each command 
individually. I may fall into the group of living with it ;-)


On Thu, Jan 23, 2014 at 4:47 PM, Rob Mensching  wrote:

> I assume most people live with the perf since no one has ever bothered 
> to fix the bug.
>
> -Original Message-
> From: Levi Wilson [mailto:l...@leviwilson.com]
> Sent: Thursday, January 23, 2014 12:30 PM
> To: General discussion about the WiX toolset.
> Subject: Re: [WiX-users] SqlScript with large schema setup
>
> What are other ways that people have gotten around it? It doesn't seem 
> desirable to execute `sqlcmd` from a CA.
>
>
> On Thu, Jan 23, 2014 at 2:26 PM, Rob Mensching 
> wrote:
>
> > You'll want to think about security with that second option. I don't 
> > think the MSI property is the issue. I think it's the SQLCA code 
> > itself that is slow parsing. IIRC, there is a (very old) bug about 
> > the perf problem. Maybe you'd like to tackle it?
> >
> > -Original Message-
> > From: Levi Wilson [mailto:l...@leviwilson.com]
> > Sent: Thursday, January 23, 2014 10:41 AM
> > To: wix-users@lists.sourceforge.net
> > Subject: Re: [WiX-users] SqlScript with large schema setup
> >
> > Sorry I didn't mention this before, but the database is already 
> > going to exist. Our customers create this beforehand. The installer 
> > will just be running the SQL script for the initial schema to create 
> > all of our tables, triggers, sprocs, etc.
> >
> > When looking at the installer log, I see two lines that jump out at me:
> >
> > MSI (s) (C4!BC) [11:44:00:998]: Closing MSIHANDLE (45) of type
> > 790540 for thread 12732 MSI (s) (C4!BC) [11:50:33:616]: PROPERTY CHANGE:
> > Adding ExecuteSqlStrings property. Its value is '**'.
> >
> > So it looks like it takes 6 minutes to take the 144k lines of my SQL 
> > script that is stored in a  to create the 
> > ExecuteSqlStrings property.
> > Seems like I'm holding it wrong :-)
> >
> > Would a better option be to create a CA that reads the SQL out of a 
> > binary record and execute it myself? Rather than having the 
> > intermediate step of creating an MSI property?
> >
> > Levi
> >
> >
> >
> > > Why not right click on the DB, tasks and generate in MS? What 
> > > version of SQL?
> > >
> >
> >
> > On Thu, Jan 23, 2014 at 10:52 AM, Levi Wilson  wrote:
> > > > I am using a  to create our database schema. I 
> > > > exported the schema using RedGate. The file is 10MB (I know, I
> know...).
> > > > Everything works as expected, but during the installation the 
> > > > "Configuring SQL
> > > Server"
> > > > takes forever.
> > > >
> > > > I know, 10MB file with 144k lines of SQL to parse is a lot...is 
> > > > there a better alternative to getting this initial script created?
> > > >
> > > > Thanks in advance,
> > > >
> > > > Levi
> > > >
> > > >
> > > --
> > > --
> > > --
> > > 
> > > > CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> > > > Learn Why More Businesses Are Choosing CenturyLink Cloud For 
> > > > Critical Workloads, Development Environments & Everything In Between.
> > > > Get a Quote or Start a Free Trial Today.
> > > >
> > > >
> > > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.
> > > clktrk
> > > > ___
> > > > WiX-users mailing list
> > > > WiX-users@...
> > > > https://lists.sourceforge.net/lists/listinfo/wix-users
> > > >
> > > --
> > > "They may forget what you said but they will never forget how you 
> > > made them feel." -- Anonym

Re: [WiX-users] Enable/Disable IIS AppPool's LogEventOnRecycle using WiX

[Chad Petersen]

For things IIS related not directly authored in WiX code I've found APPCMD.EXE 
to be a useful substitute in a custom action for those sorts of things. These 
are older and may be supported natively now, but some examples.




-Original Message-
From: Tony [mailto:yellowjacketl...@gmail.com] 
Sent: Friday, November 22, 2013 1:05 PM
To: WiX Users
Subject: [WiX-users] Enable/Disable IIS AppPool's LogEventOnRecycle using WiX

Is it possible to set an AppPool's LogEventOnRecycle bitmask using WiX?  I 
don't see it, but maybe missed it.

--
Tony
--
Shape the Mobile Experience: Free Subscription Software experts and developers: 
Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing 
conversations that shape the rapidly evolving mobile landscape. Sign up now. 
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing 
conversations that shape the rapidly evolving mobile landscape. Sign up now. 
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] help needed including directories

[Chad Petersen]

A Feature element can go inside of a Product element (as well as others). Look 
at the Example.wxs that you sent in your first inquiry. Add Jacob's extra line 
to it.


-Original Message-
From: Richard Silverstein [mailto:rsilverst...@conarc.com] 
Sent: Friday, July 12, 2013 12:55 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] help needed including directories

Thanks Jacob.  But I'm not sure where this code piece goes.

-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: Friday, July 12, 2013 2:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] help needed including directories

You need to reference the component/componentgroup from within a feature in 
order for Wix to include it.

  
 
 
  

-Original Message-
From: Richard Silverstein [mailto:rsilverst...@conarc.com]
Sent: Friday, July 12, 2013 1:04 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] help needed including directories

Thanks for looking at this...

Yes, Notepad.exe and Readme.txt are there.   I included the wrong example but 
in this case, I'm not getting fragment.txt either.

For the directory example, I have a folder called FOLDER and it has file called 
abc.txt.

The wxs, SampleHarvest.wxs,  for the FOLDER:


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














And the bat script:

"c:\program files (x86)\wix toolset v3.8\bin\candle" SampleHarvest.wxs 
example.wxs "c:\program files (x86)\wix toolset v3.8\bin\light"  -out ICD 
SampleHarvest.wixobj example.wixobj

With this, I do not get the FOLDER and abc.txt in the installed directory along 
with Notepad.exe and Readme.txt.

Rick


-----Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Friday, July 12, 2013 1:18 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] help needed including directories

I compiled and linked your example into an MSI and ran it and it works great. 
Notepad.exe and Readme.txt installed.  Remember if you are on a 64-bit system 
you need to look in C:\Program Files (x86)\Example to find your installed files.



-Original Message-
From: Richard Silverstein [mailto:rsilverst...@conarc.com]
Sent: Friday, July 12, 2013 9:07 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] help needed including directories

I'm new to Wix and having trouble including directories.  I read about Heat and 
Fragments and it appears I'm doing it by the example, but my directory and its 
files are not getting included after the install.

My install.bat has:

"c:\program files (x86)\wix toolset v3.8\bin\candle" fragment.wxs example.wxs 
"c:\program files (x86)\wix toolset v3.8\bin\light"  -out ICD fragment.wixobj 
example.wixobj

Fragment.wxs:

 
  

  

  

  


  



Example.wxs:


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

   
  
  
   

 
  
  
 
  
   


Thank you
Rick SIlverstein
Conarc, Inc.


--
See everything from the browser to the database with AppDynamics Get end-to-end 
visibility with application monitoring from AppDynamics Isolate bottlenecks and 
diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
See everything from the browser to the database with AppDynamics Get end-to-end 
visibility with application monitoring from AppDynamics Isolate bottlenecks and 
diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
See everything from the browser to the database with AppDynamics Get end-to-end 
visibility with application monitoring from AppDynamics Isolate bottlenecks and 
diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
___

Re: [WiX-users] help needed including directories

[Chad Petersen]

I'll give that a quick try. I did notice the  instead of   which might 
have an impact. 

-Original Message-
From: Richard Silverstein [mailto:rsilverst...@conarc.com] 
Sent: Friday, July 12, 2013 11:04 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] help needed including directories

Thanks for looking at this...

Yes, Notepad.exe and Readme.txt are there.   I included the wrong example but 
in this case, I'm not getting fragment.txt either.

For the directory example, I have a folder called FOLDER and it has file called 
abc.txt.

The wxs, SampleHarvest.wxs,  for the FOLDER:


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














And the bat script:

"c:\program files (x86)\wix toolset v3.8\bin\candle" SampleHarvest.wxs 
example.wxs "c:\program files (x86)\wix toolset v3.8\bin\light"  -out ICD 
SampleHarvest.wixobj example.wixobj

With this, I do not get the FOLDER and abc.txt in the installed directory along 
with Notepad.exe and Readme.txt.

Rick


-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Friday, July 12, 2013 1:18 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] help needed including directories

I compiled and linked your example into an MSI and ran it and it works great. 
Notepad.exe and Readme.txt installed.  Remember if you are on a 64-bit system 
you need to look in C:\Program Files (x86)\Example to find your installed files.



-Original Message-
From: Richard Silverstein [mailto:rsilverst...@conarc.com]
Sent: Friday, July 12, 2013 9:07 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] help needed including directories

I'm new to Wix and having trouble including directories.  I read about Heat and 
Fragments and it appears I'm doing it by the example, but my directory and its 
files are not getting included after the install.

My install.bat has:

"c:\program files (x86)\wix toolset v3.8\bin\candle" fragment.wxs example.wxs 
"c:\program files (x86)\wix toolset v3.8\bin\light"  -out ICD fragment.wixobj 
example.wixobj

Fragment.wxs:

 
  

  

  

  


  



Example.wxs:


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

   
  
  
   

 
  
  
 
  
   


Thank you
Rick SIlverstein
Conarc, Inc.


--
See everything from the browser to the database with AppDynamics Get end-to-end 
visibility with application monitoring from AppDynamics Isolate bottlenecks and 
diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
See everything from the browser to the database with AppDynamics Get end-to-end 
visibility with application monitoring from AppDynamics Isolate bottlenecks and 
diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
See everything from the browser to the database with AppDynamics Get end-to-end 
visibility with application monitoring from AppDynamics Isolate bottlenecks and 
diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] help needed including directories

[Chad Petersen]

I compiled and linked your example into an MSI and ran it and it works great. 
Notepad.exe and Readme.txt installed.  Remember if you are on a 64-bit system 
you need to look in C:\Program Files (x86)\Example to find your installed files.



-Original Message-
From: Richard Silverstein [mailto:rsilverst...@conarc.com] 
Sent: Friday, July 12, 2013 9:07 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] help needed including directories

I'm new to Wix and having trouble including directories.  I read about Heat and 
Fragments and it appears I'm doing it by the example, but my directory and its 
files are not getting included after the install.

My install.bat has:

"c:\program files (x86)\wix toolset v3.8\bin\candle" fragment.wxs example.wxs 
"c:\program files (x86)\wix toolset v3.8\bin\light"  -out ICD fragment.wixobj 
example.wixobj

Fragment.wxs:

 
  

  

  

  


  



Example.wxs:


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

   
  
  
   

 
  
  
 
  
   


Thank you
Rick SIlverstein
Conarc, Inc.


--
See everything from the browser to the database with AppDynamics Get end-to-end 
visibility with application monitoring from AppDynamics Isolate bottlenecks and 
diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Response file for silent installation

[Chad Petersen]

Look at what you pointed to. It's an article from 2006 dealing with 
InstallSheild 12 (NOT 2012) so it is very old. Some of it still applies to 
older projects but I don't think that applies to a Basic MSI project.

If you run your MSI with MSIEXEC.EXE command line parameters to generate a 
verbose log file the COMMANDLINE that is executed by the engine is logged. You 
can grab that from the log file and use it as a basis for other command lines 
but that's the way I know of. Probably just haven't run across anything better 
and it works but others will be along to share their techniques if there's 
something better.

-Original Message-
From: Marco Tognacci [mailto:mark...@live.it] 
Sent: Wednesday, May 15, 2013 10:35 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Response file for silent installation

Is there any way for recording user choise, to generate a file to use for 
running the setup in silent mode like InstallShield do with -r command line 
parameter? as explained in the help reported in the link
http://kb.flexerasoftware.com/doc/Helpnet/installshield12helplib/CreatetheResponseFile.htm

--
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



--
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] Hide/blank out Passwords in MSI log file

[Chad Petersen]

If possible paste in a snippet of your log file around where the password is 
seen. I tried for a long time to hide passwords using the same method. But it 
was some built-in custom actions that were logging my passwords rather than 
code I'd written myself.




These were two entries that I made to make those extensions hide the data 
passed to them, such as my password.

-Original Message-
From: Jeremiahf [mailto:jeremi...@gmail.com] 
Sent: Thursday, May 02, 2013 2:38 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Hide/blank out Passwords in MSI log file

I have tried that and no luck. My MSI is installed via command line.

I've even tried to give the property Id a value in case I missed something and 
still doesn't work.



My test system is running Server 2003 R2 SP 2 windows installer version 4.5 
6001.22159

I've upgraded from WIX 3.6 TO 3.7 in case it was a bug as I have found in 
hundreds of blogs online but every time I see that a fix was submitted, I can't 
tell what version it was submitted in. (sorry for the run on
sentence.)

J


On Thu, May 2, 2013 at 4:24 PM, Steven Ogilvie wrote:

> I declare the property:
>  This is 
> how I use my password controls:
>  Y="152" Property="WEBAPPPOOL_PASSWORD" Password="yes" TabSkip="no" />
>
> Logfile:
> MSI (c) (70:1C) [14:50:59:778]: PROPERTY CHANGE: Adding 
> WEBAPPPOOL_PASSWORD property. Its value is '**'
>
>
> -Original Message-
> From: Jeremiahf [mailto:jeremi...@gmail.com]
> Sent: May-02-13 5:08 PM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Hide/blank out Passwords in MSI log file
>
> Has anyone had luck with this?
>
>
>
> I have tried using Hidden, HideTarget  and I still see the password in 
> my logs. Is this still a bug in windows installer?
>
>
>
> Thanks in advance,
>
> --
>  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://p.sf.net/sfu/appdyn_d2d_ap2
> ___
> 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://p.sf.net/sfu/appdyn_d2d_ap2
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



--
"They may forget what you said but they will never forget how you made them 
feel." -- Anonymous
--
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://p.sf.net/sfu/appdyn_d2d_ap2
___
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://p.sf.net/sfu/appdyn_d2d_ap2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Hide/blank out Passwords in MSI log file

[Chad Petersen]

Try setting this



-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com] 
Sent: Thursday, May 02, 2013 2:56 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Hide/blank out Passwords in MSI log file

Aha I checked my log again and I see what you mean...

I am using a custom action to set the property I see the password:

MSI (s) (D8:60) [17:35:47:010]: PROPERTY CHANGE: Adding CA_WebAppPoolPassword. 
property. Its value is 'WEBAPPPOOL_PASSWORD=astring'.
Property(S): WEBAPPPOOL_PASSWORD = **
Property(S): CA_WebAppPoolPassword. = WEBAPPPOOL_PASSWORD=astring

It is during the setting of the property using a custom action that it displays 
it... I will see later if I really need to call a custom action to set the 
property...

Steve

-Original Message-
From: Jeremiahf [mailto:jeremi...@gmail.com]
Sent: May-02-13 5:38 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Hide/blank out Passwords in MSI log file

I have tried that and no luck. My MSI is installed via command line.

I've even tried to give the property Id a value in case I missed something and 
still doesn't work.



My test system is running Server 2003 R2 SP 2 windows installer version 4.5 
6001.22159

I've upgraded from WIX 3.6 TO 3.7 in case it was a bug as I have found in 
hundreds of blogs online but every time I see that a fix was submitted, I can't 
tell what version it was submitted in. (sorry for the run on
sentence.)

J


On Thu, May 2, 2013 at 4:24 PM, Steven Ogilvie wrote:

> I declare the property:
>  This is 
> how I use my password controls:
>  Y="152" Property="WEBAPPPOOL_PASSWORD" Password="yes" TabSkip="no" />
>
> Logfile:
> MSI (c) (70:1C) [14:50:59:778]: PROPERTY CHANGE: Adding 
> WEBAPPPOOL_PASSWORD property. Its value is '**'
>
>
> -Original Message-
> From: Jeremiahf [mailto:jeremi...@gmail.com]
> Sent: May-02-13 5:08 PM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Hide/blank out Passwords in MSI log file
>
> Has anyone had luck with this?
>
>
>
> I have tried using Hidden, HideTarget  and I still see the password in 
> my logs. Is this still a bug in windows installer?
>
>
>
> Thanks in advance,
>
> --
>  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://p.sf.net/sfu/appdyn_d2d_ap2
> ___
> 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://p.sf.net/sfu/appdyn_d2d_ap2
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



--
"They may forget what you said but they will never forget how you made them 
feel." -- Anonymous
--
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://p.sf.net/sfu/appdyn_d2d_ap2
___
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://p.sf.net/sfu/appdyn_d2d_ap2
___
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://p.sf.net/sfu/appdyn_d2d_ap2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lis

Re: [WiX-users] Cannot create major upgrade installer

[Chad Petersen]

I'd bet you haven't changed this variable.

Id="$(var.ProductCode)"

While in there make sure this is set to what you want also.

Version="$(var.VersionNumber)"

Make sure you do keep this one the same (it is if you get the message you 
mentioned)

UpgradeCode="$(var.UpgradeCode)"



-Original Message-
From: Tim Hawes [mailto:haw...@anx.com] 
Sent: Thursday, March 28, 2013 7:25 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Cannot create major upgrade installer

I have been wracking my brain on this for a day and a half. I am trying to make 
an installer that will uninstall the older version of the software and install 
the new. The old version is in the registry as 2.1 and the new one I am trying 
to install is 2.2.1

For the life of me, I cannot create an msi file that uninstalls the old version 
and installs the new. I have worked through the tutorial linked from 
wixtoolset.org, and have googled around the net looking for a solution to this. 
It keeps coming back and telling me:

"Another version of this product is already installed. Installation of this 
version cannot continue. To configure or remove the existing version of this 
product, use Add/Remove Programs on the Control Panel."

(I am using a Windows 2003 server instance as my development environment).

I have a wxs file that begins with:

   

 

 

 
 
 

 
   
 

--
Tim Hawes
Programmer
haw...@anx.com
Direct: 919-695-4282
Cell: 919-656-2135


--
Own the Future-Intel® Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest.
Compete for recognition, cash, and the chance to get your game 
on Steam. $5K grand prize plus 10 genre and skill prizes. 
Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Own the Future-Intel® Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest.
Compete for recognition, cash, and the chance to get your game 
on Steam. $5K grand prize plus 10 genre and skill prizes. 
Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Remove Existing Products

[Chad Petersen]

Check to see if the InstallShield is a "Per-user" or "Per-machine" install and 
compare that to your WiX installer. A per-user install can't be removed by a 
per-machine install. If ALLUSERS isn't set or is set to 0 then that's per-user. 
If ALLUSERS is set to 1 then it's per-machine.

-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com] 
Sent: Friday, February 15, 2013 7:44 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Remove Existing Products

For a major upgrade you MUST change the product GUID, increase your version 
number (Minor version) i.e. from 1.0.0.1 to 1.1.0.1 and use the MajorUpgrade 
element.
I just use:

Did you change the Product Id="some GUID">



Comment OUT all of this:

  
  
  





That should work...

Steve

-Original Message-
From: Helge Kruse [mailto:helge.kr...@gmx.net]
Sent: February-15-13 10:34 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Remove Existing Products

I want to install my first major upgrade. The older product MSI version 1.05.02 
has been build with InstallShield. Let's say the UpgradeCode of the old product 
is ---5-6.

My new installer has the same UpgradeCode as the old product version.



The upgrade should be determined by the following fragment, that is based on 
the WiX book of Nick Ramirez:
  
  
  





I have checked that the UpgradeCode and the Language match with the former 
product version. When I install the new MSI does not remove the existing 
product. When running msiexec with /l*v I get this log
(excerpt):

Action ended 15:51:41: InstallValidate. Return value 1.
MSI (s) (E0:DC) [15:51:41:910]: Doing action: RemoveExistingProducts Action 
15:51:41: RemoveExistingProducts. Removing applications Action start 15:51:41: 
RemoveExistingProducts.
Action ended 15:51:41: RemoveExistingProducts. Return value 1.
MSI (s) (E0:DC) [15:51:41:912]: Doing action: InstallInitialize Action 
15:51:41: InstallInitialize.
Action start 15:51:41: InstallInitialize.

AFAIK the return value 1 of RemoveExistingProducts indicates an error.
But I don't know what error.

The new files are installed, but I still see the old version of the product in 
the Programs and Features. When I uninstall the old MSI the product is removed.

How do I find the failure for the RemoveExistingProducts action? How do I fix 
my setup wxs?

Regards
Helge

--
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013 and get the 
hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013 and get the 
hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, 
is your hub for all things parallel software development, from weekly thought 
leadership blogs to news, videos, case studies, tutorials, tech docs, 
whitepapers, evaluation guides, and opinion stories. Check out the most 
recent posts - join the conversation now. http://goparallel.sourceforge.net/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] List of all InstallUISequence & InstallExecuteSequence actions/events

[Chad Petersen]

+1 for Orca. I use it a ton to inspect the resulting MSI and see if it looks 
like it built like I wanted it to. You can sort by Sequence number in those two 
tables to see what relative order things go in. Very handy.

-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com] 
Sent: Friday, January 18, 2013 1:49 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] List of all InstallUISequence & InstallExecuteSequence 
actions/events

For a given installer, open it in Orca and look at the appropriate table.

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




-Original Message-
From: The Ouizard [mailto:the.ouiz...@gmail.com]
Sent: Friday, January 18, 2013 3:38 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] List of all InstallUISequence & InstallExecuteSequence 
actions/events

Where can I find a complete list of all the InstallUISequence and 
InstallExecuteSequence, and the order in which they occur?

I'm having trouble figuring out where to put my dialogs in the installation 
sequence when I don't even know the possibilities.


--
Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get 
web development skills now with LearnDevNow -
350+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122812
___
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.


--
Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get 
web development skills now with LearnDevNow -
350+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122812
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and
much more. Get web development skills now with LearnDevNow -
350+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122812
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Changing DirectoryRef

[Chad Petersen]

The verbose log file will be your friend. It tells everything that the 
installer is doing. Then you just need to figure out from the symptoms what is 
wrong with your authoring. Sounds like you have something fundamentally wrong, 
but sounds easy to overcome.

I don't use Wix_Mondo or Wix_UIInstallDir. I was using WiX before those 
existed. I use one WXS file that has all of Microsofts common UI dialogs and 
then another one with our custom dialogs and I hooked them up years ago.

I think with those you are using you have to expose the WXS code so you can 
make a copy of it and use it instead of Wix_Mondo if you want to customize 
things. 

One thought would be to go back and follow the tutorial for a simple install 
based off of Wix_Mondo and see if you can control where it gets installed. Then 
compare that to your existing project.

Hopefully others will chime in if you have further questions since I'm not 
familiar with those built-in UI modules.

To gather a verbose log file you can use 

MSIEXEC.EXE /L*v [logfilename] /i [msifilename].MSI

Good luck!

-Original Message-
From: Chaitanya [mailto:chaita...@pointcross.com] 
Sent: Monday, January 07, 2013 9:20 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Changing DirectoryRef

Iam tried with all UI references like Wix_Mondo,Wix_UIinstallDir.
When I use Installdir,iam selecting c:drive but it is going to another drive 
which is having more free space.
When I use these various Windows folders in my DIRECTORYREF its not taking.
How can I overcome this problem.

-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: 07 January 2013 23:28
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Changing DirectoryRef

In addition to that you might want to read up on the ROOTDRIVE property as it 
appears it is somewhat involved in the symptoms you are describing.

http://msdn.microsoft.com/en-us/library/aa371372(VS.85).aspx


Also, don't forget about the well-known properties that identify various 
Windows folders. You get these for free.

[WindowsFolder]
[SystemFolder]
[System64Folder]
[ProgramFilesFolder]
[ProgramFiles64Folder]
[CommonFilesFolder]
[CommonFiles64Folder]
[FontsFolder]

Etc. There are a lot of predefined folders you can refer to in your WiX code 
like these.



-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Monday, January 07, 2013 9:17 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Changing DirectoryRef

The tutorial explains how to use WiXUI_InstallDir -> 
http://wix.tramontana.co.hu/tutorial/user-interface/ui-wizardry

Do you have an INSTALLDIR under your TARGETDIR or are you simply setting 
WiXUI_INSTALLDIR to TARGETDIR?

Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com 

**Design, Simulate + Innovate with the ** Integrated 
Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered 
Office - Helix Building, West Of Scotland Science Park, Glasgow
G20 0SP Email Disclaimer 


-Original Message-
From: Chaitanya [mailto:chaita...@pointcross.com]
Sent: 07 January 2013 06:39
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] Changing DirectoryRef

Hi,

I installing msi in my System.iam 2 drives.

1).When iam installing an msi.iam changing drive through WixUI_InstallDir.

I can change the location where I want.

But my msi is checking which drive is having more free space and it is 
installing there.

I overcome that problem by using the command line

Msiexec TARGETDIR="{DRIVENAME}  /I {MYAPPLICATION.MSI}

I can install my msi where I want.

2).here my problem is I want to install some of my files in 
c:\inetpub,c:\program files,c:\windows.

When I give command line it is going to that drive and creating program files 
folder in that drive.Its not installing in c:drive

How to change my DirectoryRef.to c:\drive

Regards,

Chaitanya.

 


--
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, 
Windows 8 Apps, JavaScript and much more. Keep your skills current with 
LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. 
SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, 
Windows 8 Apps, JavaScript and much more. Keep your skills current with 
LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. 
SALE $99.99 this month only -- learn more at:
htt

Re: [WiX-users] Changing DirectoryRef

[Chad Petersen]

In addition to that you might want to read up on the ROOTDRIVE property as it 
appears it is somewhat involved in the symptoms you are describing.

http://msdn.microsoft.com/en-us/library/aa371372(VS.85).aspx


Also, don't forget about the well-known properties that identify various 
Windows folders. You get these for free.

[WindowsFolder]
[SystemFolder]
[System64Folder]
[ProgramFilesFolder]
[ProgramFiles64Folder]
[CommonFilesFolder]
[CommonFiles64Folder]
[FontsFolder]

Etc. There are a lot of predefined folders you can refer to in your WiX code 
like these.



-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com] 
Sent: Monday, January 07, 2013 9:17 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Changing DirectoryRef

The tutorial explains how to use WiXUI_InstallDir -> 
http://wix.tramontana.co.hu/tutorial/user-interface/ui-wizardry

Do you have an INSTALLDIR under your TARGETDIR or are you simply setting 
WiXUI_INSTALLDIR to TARGETDIR?

Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com 

**Design, Simulate + Innovate with the ** Integrated 
Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered 
Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email 
Disclaimer 


-Original Message-
From: Chaitanya [mailto:chaita...@pointcross.com] 
Sent: 07 January 2013 06:39
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] Changing DirectoryRef

Hi,

I installing msi in my System.iam 2 drives.

1).When iam installing an msi.iam changing drive through WixUI_InstallDir.

I can change the location where I want.

But my msi is checking which drive is having more free space and it is 
installing there.

I overcome that problem by using the command line

Msiexec TARGETDIR="{DRIVENAME}  /I {MYAPPLICATION.MSI}

I can install my msi where I want.

2).here my problem is I want to install some of my files in 
c:\inetpub,c:\program files,c:\windows.

When I give command line it is going to that drive and creating program files 
folder in that drive.Its not installing in c:drive

How to change my DirectoryRef.to c:\drive

Regards,

Chaitanya.

 

--
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, 
Windows 8 Apps, JavaScript and much more. Keep your skills current with 
LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. 
SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Drive Problem

[Chad Petersen]

If you gather a verbose log file you might search it for the word ROOTDRIVE. 
This property can alter where an installation automatically goes.

You can set ROOTDRIVE manually in your WiX code, too.





-Original Message-
From: Chaitanya [mailto:chaita...@pointcross.com] 
Sent: Wednesday, January 02, 2013 3:38 AM
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] Drive Problem

Hi,

Iam writing silent installer(msi) to install in C Drive like(C:\Apps).



But msi checking drive which is having low space it is installing there.

Ex:if iam havng low space in my D:\ drive its installing there.

As per my customer requirement I want to install in C:\ drive.

Just help me what to do.

Regards,

Chaitanya.

 

--
Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery and 
much more. Keep your Java skills current with LearnJavaNow -
200+ hours of step-by-step video tutorials by Java experts.
SALE $49.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122612
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery
and much more. Keep your Java skills current with LearnJavaNow -
200+ hours of step-by-step video tutorials by Java experts.
SALE $49.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122612 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Propogating Environmnet variables

[Chad Petersen]

That Windows for you. Existing CMD consoles don't get updated environment 
variables. Happens with no installer involved, too. For example, open a CMD 
Prompt. Then go to your Environment variables and alter your Path. The altered 
Path won't show up in the running CMD Prompt, but new CMD Prompts will show the 
altered path.

It's worked like this as long as I can remember. I don't believe an installer 
can overcome these Windows limitations, if you will.

-Original Message-
From: Mita Patel [mailto:mpa...@esri.com] 
Sent: Monday, December 17, 2012 4:31 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Propogating Environmnet variables

We are having issues propagating the environment variables. The setup has a 
custom action that propagates the environment using  the SendMessageTimeOut api

  SendMessageTimeout(HWND_BROADCAST, WM_SETTINGCHANGE, 0,(LPARAM) 
"Environment", SMTO_ABORTIFHUNG, 5000, NULL);

On a 64 bit OS, both 32 and 64 bit consoles were opened before the install.  
Ran the install with the above custom action. If a console window is open one 
doesn't see the custom Environment.  But open a new console session and the 
varaible is listed (for both 32 and 64 bit cosole).  Is this the correct 
behavior?  Is there a way for the console window opened before the install to 
see the custom environment variable.

Thanks
Mita

--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely 
access PCs and mobile devices and provide instant support Improve your 
efficiency, and focus on delivering more value-add services Discover what IT 
Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Problem in Major upgrade

[Chad Petersen]

A person does need to use OnlyDetect="no" to have a product removed. With it 
set to yes it will only detect that it is there, but not remove it.

It's at least one thing to try.

-Original Message-
From: Chaitanya [mailto:chaita...@pointcross.com] 
Sent: Wednesday, November 07, 2012 1:43 AM
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] Problem in Major upgrade

Hi,

Iam trying to do major upgrade.

Its doing action but in my control panel it is showing two entries don't want 
two entries.

Here is my upgrade code.



  

  







  newProductFound

  



Iam changing the product code and maintaining upgrade code same. Through 
command line "msiexec /I {.msi} ALLUSERS=1

Please help  me where im doing wrong.

Thanks,

Chaitanya.

--
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center 
Diagnose problems and improve visibility into emerging IT issues Automate, 
monitor and manage. Do more in less time with Central 
http://p.sf.net/sfu/logmein12331_d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Getting values from listbox

[Chad Petersen]

Is your property all uppercase letters? Making it all uppercase makes it 
public, otherwise it is private. Also if the property is being set in the UI 
sequence and then being called in the Execute sequence you probably need to add 
it to SecureCustomProperties.

http://msdn.microsoft.com/en-us/library/windows/desktop/aa371571(v=vs.85).aspx

Just some thoughts.

Chad

-Original Message-
From: Natalie Carr [mailto:natalie.c...@measuresoft.com] 
Sent: Thursday, October 04, 2012 7:08 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Getting values from listbox

Hi I got my custom action to populate my Listbox table in Wix which is linked 
to a property. I am now trying to call that property from another custom action 
but I do not seem to be able to do that. I'm using MsiGetProperty and tried 
WcaGetProperty but I am getting  and it is not picking up the value. 
Anyone came across this?

 

Kind Regards,

 

Natalie Carr

 

--
Don't let slow site performance ruin your business. Deploy New Relic APM Deploy 
New Relic app performance management and know exactly what is happening inside 
your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and 
get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] modify XML file using utils:XmlConfig...

[Chad Petersen]

Your ElementPath isn't pointing to anything beyond your root element of 
appplicationSettings, as far as I can tell. You need to use XPath to specify 
the inner text of that deeper element. Seems it is almost always some trial and 
error to nail these. I like to create a mini installer that does nothing but 
modify the XML so I can run it and uninstall it very quickly for some quick 
iterative tests until I get the syntax right for a given XPath. Then I merge 
that into my main project.


-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com] 
Sent: Wednesday, September 19, 2012 3:50 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] modify XML file using utils:XmlConfig...

Sigh...

I need to modify an xml file:


  
*false*
  
  
3
  


  
SQL Server Database Provider
  


  

I need to change the false to a true... here is my xmlconfig code:



What the heck am I doing wrong?

Frustrated,

Steve



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/modify-XML-file-using-utils-XmlConfig-tp7580678.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat 
landscape has changed and how IT managers can respond. Discussions will include 
endpoint security, mobile security and the latest in malware threats. 
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Bug? UpgradeVersion element causing LGHT0094 error

[Chad Petersen]

I was able to get past this error in your example by adding this inside the 
Fragment


  
 

-Original Message-
From: Don Walker [mailto:don.wal...@versaterm.com] 
Sent: Wednesday, July 11, 2012 8:49 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Bug? UpgradeVersion element causing LGHT0094 error

In WiX version 3.6.3109.0 I am getting the following build error:

Product.wxs(16,0): error LGHT0094: Unresolved reference to symbol 
'WixAction:InstallExecuteSequence/RemoveExistingProducts' in section 
'Product:*'.
The same error appears for line 18.

My test example follows:


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





  
  
  
  



  

  

  

  

  

  

  


  


let me know if this is a bug and I'll file an official bug report. If not, let 
me know what I did wrong.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat 
landscape has changed and how IT managers can respond. Discussions will include 
endpoint security, mobile security and the latest in malware threats. 
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Question on RemoveFolderEx

[Chad Petersen]

What version of WiX are you using? I don't believe that RemoveFolderEx
would be available until WiX 3.6. Something to consider, at least.

-Original Message-
From: Shyam Kannam [mailto:shyam.kan...@gmail.com] 
Sent: Wednesday, May 30, 2012 10:44 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Question on RemoveFolderEx

Hi,

I'm pretty newbie on using WiX.  I'm having trouble with using
RemoveFolderEx in our installer sources.  Hope someone could help me
with this.



Our software application creates temporary folders in our installation
directory.  On uninstall these folders as well the root folder is not
getting removed due to the new temp folders existing.  I searched the
wix forums and found out that RemoveFolderEx could help scrubbing the
folders on uninstall.



I'm hitting into compilation issues with using RemoveFolderEx.  Any help
on this is greatly appreciated.  Below is the code snippet and the
compilation error.



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

 xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";>



...





  







  





  







...





error CNDL0005: The Component element contains an unexpected child
element 'util:RemoveFolderEx'.



Thanks

Shyam

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat
landscape has changed and how IT managers can respond. Discussions will
include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Install Failed, Log Attached

[Chad Petersen]

Not sure it's what you want, but what I typically do in this case is run
REGASM /Regfile to generate a .REG file and then use Heat to convert
that .REG file into a .WXS fragment that I can then include in my
project.

-Original Message-
From: Sam Youtsey [mailto:sam.yout...@gmail.com] 
Sent: Thursday, April 26, 2012 3:21 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Failed, Log Attached

I've built the DLL with an interface for interacting with other COM
components, how does this differ from being a Win32 COM DLL? Thanks for
the assistance with this!

On Thu, Apr 26, 2012 at 3:16 PM, Wilson, Phil
wrote:

> You really have to say if it's a Win32 COM Dll or not. I can't see a 
> definitive statement one way or another. However if it is Win32 COM, 
> just use Heat.exe to generate the WiX source for the registration.
>
> Phil W
>
> -Original Message-
> From: Sam Youtsey [mailto:sam.yout...@gmail.com]
> Sent: Thursday, April 26, 2012 3:13 PM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Install Failed, Log Attached
>
> Once I've installed it into the CommonFiles directory how can I 
> register and access it through the system? This is typically done with

> RegAsm.exe on the dev machine but this isn't available on the client 
> machine. Eventually, I want to be able to see this DLL's classes
through Excel.
>
>
> > Well you can install assemblies (that supply COM interfaces) into 
> > the
> GAC.
> > But you are trying to install a Win32 COM DLL into the GAC? That 
> > won't work, and it's not a WiX issue - it doesn't matter what you 
> > use to build your MSI file because it's MSI that's doing the
install.
> > If it's Win32 COM, just install it in CommonFiles for your Company.
> > Phil W
> > -Original Message-
> > From: Sam Youtsey [mailto:sam.youtsey@...]
> > Sent: Thursday, April 26, 2012 1:41 PM
> > To: wix-users@...
> > Subject: Re: [WiX-users] Install Failed, Log Attached Ah, I wasn't 
> > aware COM DLLs couldn't be installed into the GAC. What's an 
> > appropriate course of action for using them on the client system if 
> > I still wanted to use WiX?
> > > And the TLB file is in the same component as the assembly or is 
> > > somehow being installed to the GAC? That could explain an error 
> > > FUSION_E_UNEXPECTED_MODULE_FOUND.
> > > Phil W
> > > -Original Message-
> > > From: John Cooper [mailto:JoCooper@...]
> > > Sent: Thursday, April 26, 2012 12:35 PM
> > > To: General discussion for Windows Installer XML toolset.
> > > Subject: Re: [WiX-users] Install Failed, Log Attached A TLB files 
> > > strongly suggests that this is a COM and/or native DLL. I don't 
> > > think that's a candidate for the GAC either way.
> > > --
> > > John Merryweather Cooper
> > > Build & Install Engineer - ESA
> > > Jack Henry & Associates, Inc.(r)
> > > Shawnee Mission, KS 66227
> > > Office: 913-341-3434 x791011
> > > JoCooper@...
> > > http://www.jackhenry.com
> > > -Original Message-
> > > From: Sam Youtsey [mailto:sam.youtsey@...]
> > > Sent: Thursday, April 26, 2012 2:28 PM
> > > To: wix-users@...
> > > Subject: Re: [WiX-users] Install Failed, Log Attached Yeah, it's a

> > > DLL. There don't seem to be any config files associated, just the 
> > > TLB file. Anything else to look for?
> > > That HRESULT is FUSION_E_UNEXPECTED_MODULE_FOUND.
> > > > http://blogs.msdn.com/b/astebner/archive/2004/11/10/255346.aspx
> > > > Is there a config file associated with the assembly (maybe 
> > > > because it's a policy assembly)?
> > > > Is it actually a Dll?
> > > > Phil W
> > > > -Original Message-
> > > > From: Sam Youtsey [mailto:sam.youtsey@...]
> > > > Sent: Thursday, April 26, 2012 10:35 AM
> > > > To: wix-users@...
> > > > Subject: [WiX-users] Install Failed, Log Attached Hi all, My 
> > > > installer doesn't seem to be installing anything properly. Any 
> > > > chance I could get some help with it?
> > > > Here's the .wxs file:
> > > >   > > > xmlns="http://schemas.microsoft.com/wix/2006/wi";>
> > > >  > > > Name="MyProg"
> > > > Language="1033"
> > > > Version="$(var.ProductVersion)"
> > > > Manufacturer="MyCompany"
> > > > UpgradeCode="MyGuid2">
> > > >  > > InstallScope="perMachine"
> > > > />
> > > >   > > > EmbedCab="yes"/>  > > > Level="1">  
> > > > > > > Name="SourceDir">
> >  > > > Name="Program Files">  > > > Name="MyCompany"> 

> > > >  
> > > >  > > > Directory="INSTALLFOLDER">
> > > >  
>  > > > Source="..\MyProg\bin\Debug\MyProg.dll" KeyPath="yes"
> > > > Assembly=".net">
> > > >  > > > Source="..\MyProg\bin\Debug\MyProg.tlb">
> > > >  > > > Source="..\$(var.JavascriptNET)\Noesis.Javascript.dll" />  > > > Id="MyProg_Demo" Source="..\MyProg_Demo.xlsm">
> > > > 
> > > > 
> > > > 
> > > > 
> > > > And here's around the error that I'm seeing in the log:
> > > > MSI (s) (CC:68) [10:04:32:829]: Executing op:
> > > > UpgradeCodePublish(UpgradeCode={MyGuid3})
> > > > MSI (s) (CC:68) [10:04:32:829]:

Re: [WiX-users] Setting MsiLogFileLocation property

[Chad Petersen]

I use a second custom action called WriteToMSILog that I call at specific times 
from my first custom action to log to the normal log file that everything else 
writes to. Keeps everything in one log file and is easy to call as needed.

The CDATA portion looks like this (Jscript example)




The call from my first custom action looks like this

Session.Property("WriteToMSILog") = "Process Name: " + pProps[proc];
Session.DoAction("WriteToMSILog");

-Original Message-
From: Alec Swan [mailto:alecs...@gmail.com] 
Sent: Thursday, March 15, 2012 3:20 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Setting MsiLogFileLocation property

Wow, this is a pretty active mailing list. I think we have the
definite answer now.

As you can already tell I am a newbie to WIX, so please take it easy
on me with my next question. What logging mechanism do you normally
use to log messages from your custom actions?

Thanks,

Alec

On Thu, Mar 15, 2012 at 12:58 PM, Castro, Edwin G. (Hillsboro)
 wrote:
> In addition, the Windows Installer engine starts producing log messages 
> before it loads the MSI package to determine what log file to use.
>
> In short, one can set a log file:
> * On the command line
> * As an argument to MsiProductInstall()
> * In the registry (global and applies to all MSI packages, cannot be changed 
> on a per package basis)
>
> The MsiLogFileLocation property is automatically set by the Windows Installer 
> engine to allow a MSI UI to display the log file location on a dialog. 
> Changing the value of MsiLogFileLocation within the MSI package itself does 
> not change where the Windows Installer engine is logging to (as evidenced by 
> the tests performed by various people).
>
> To automatically set a log file you'll need to use a bootstrapper as was 
> already suggested so that the bootstrapper can set it on the command line or 
> as an argument to MsiProductInstall().
>
> Your system administrator could use the registry approach to control whether 
> all MSI packages generate a log file to a specific folder location with a 
> random: MSI*.LOG name.
>
> This is documented in the MSDN documentation so if anybody wants to use this 
> approach I suggest they check MSDN at 
> http://msdn.microsoft.com/en-us/library/windows/desktop/aa372847.aspx
>
> Edwin G. Castro
> Software Developer - Staff
> Digital Channels
> Fiserv
> Office: 503-746-0643
> Fax: 503-617-0291
> www.fiserv.com
> Please consider the environment before printing this e-mail
>
>
>
>> -Original Message-
>> From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
>> Sent: Thursday, March 15, 2012 11:22 AM
>> To: General discussion for Windows Installer XML toolset.
>> Subject: Re: [WiX-users] Setting MsiLogFileLocation property
>>
>> A good test anyone can try. Run a command something like this.
>>
>> MSIEXEC.EXE /L*v C:\Foobar\test.log /I 
>>
>> For that log folder that you point to make sure the C:\Foobar directly DOES
>> NOT EXIST.
>>
>> Note how MSIEXEC.EXE will simply error out rather than creating the Foobar
>> folder in which to create the log file.
>>
>> I feel this shows an example of what Edwin and others are talking about. Log
>> file must be established before MSIEXEC calls into the MSI.
>>
>> -Original Message-
>> From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
>> Sent: Thursday, March 15, 2012 11:10 AM
>> To: General discussion for Windows Installer XML toolset.
>> Subject: Re: [WiX-users] Setting MsiLogFileLocation property
>>
>> WiX is not in control of the MsiLogFileLocation property. This is 
>> functionality
>> provided by Windows Installer.
>>
>> As mentioned earlier, the log file location must be set before the MSI
>> package is loaded by the Windows Installer engine. This is how Windows
>> Installer works and the WiX team has no control over it.
>>
>> Please refer to http://msdn.microsoft.com/en-
>> us/library/windows/desktop/aa372847.aspx for information on Windows
>> Installer Logging. In particular check the Normal Logging  section at
>> http://msdn.microsoft.com/en-us/library/windows/desktop/aa370536.aspx
>> for an explanation of your options.
>>
>> Edwin G. Castro
>> Software Developer - Staff
>> Digital Channels
>> Fiserv
>> Office: 503-746-0643
>> Fax: 503-617-0291
>> www.fiserv.com
>> P Please consider the environment before printing this e-mail
>>
>>
>>
>> > -Original Message-
>> > From: Alec Swan [mailto:alecs...@gmail.com]
>> > Sent: Thursday, March 15, 

Re: [WiX-users] Setting MsiLogFileLocation property

[Chad Petersen]

A good test anyone can try. Run a command something like this.

MSIEXEC.EXE /L*v C:\Foobar\test.log /I 

For that log folder that you point to make sure the C:\Foobar directly DOES NOT 
EXIST.

Note how MSIEXEC.EXE will simply error out rather than creating the Foobar 
folder in which to create the log file.

I feel this shows an example of what Edwin and others are talking about. Log 
file must be established before MSIEXEC calls into the MSI.

-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] 
Sent: Thursday, March 15, 2012 11:10 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Setting MsiLogFileLocation property

WiX is not in control of the MsiLogFileLocation property. This is functionality 
provided by Windows Installer.

As mentioned earlier, the log file location must be set before the MSI package 
is loaded by the Windows Installer engine. This is how Windows Installer works 
and the WiX team has no control over it.

Please refer to 
http://msdn.microsoft.com/en-us/library/windows/desktop/aa372847.aspx for 
information on Windows Installer Logging. In particular check the Normal 
Logging  section at 
http://msdn.microsoft.com/en-us/library/windows/desktop/aa370536.aspx for an 
explanation of your options.

Edwin G. Castro
Software Developer - Staff
Digital Channels
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment before printing this e-mail



> -Original Message-
> From: Alec Swan [mailto:alecs...@gmail.com]
> Sent: Thursday, March 15, 2012 10:44 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Setting MsiLogFileLocation property
> 
> Phil, thank you for sharing your experience.
> 
> I would like to keep this thread active until we get a definite answer from 
> the
> WIX team. Whether it is "You can't enable MSI logging in the current version
> of WIX but will be available in version x.x" or "This is how you do this ..." 
> - it
> will still be very helpful.
> 
> Thanks,
> 
> Alec
> 
> On Thu, Mar 15, 2012 at 11:32 AM, Wilson, Phil 
> wrote:
> > You can't set MsiLogFileLocation, as the MSDN docs pretty much say. You
> can try to set it but it's ineffective. If you set it in the property table 
> it just
> gets overwritten. If you set it with a type 51 it just gets ignored.
> >
> > Phil W
> >
> > -Original Message-
> > From: Alec Swan [mailto:alecs...@gmail.com]
> > Sent: Thursday, March 15, 2012 10:09 AM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] Setting MsiLogFileLocation property
> >
> > Adam,
> >
> > This post indicates that it is possible to set MSI property from WIX:
> > http://blogs.technet.com/b/alexshev/archive/2009/05/16/from-msi-to-
> wix
> > -part-23-dll-custom-actions-logging-and-setting-properties.aspx
> >
> > If this is true, shouldn't I be able to use this approach to set some
> > kind of MSI property to force logging and/or configure location of the
> > log file?
> >
> > Enabling logging seems to be a pretty common question on the WIX
> > forum, can we have WIX team to provide a recommendation on how to do
> > this?
> >
> > Thanks,
> >
> > Alec
> >
> > On Thu, Mar 15, 2012 at 10:54 AM, Adam Kadzban
> >  wrote:
> >> Alec,
> >>
> >> As far as I know, you can't set the log file location inside WIX
> >> because you need to tell msiexec where to write the log file to
> >> before actually starting the MSI.  You need some sort of bootstrapper
> >> that calls msiexec with the logging options. I've used IExpress in
> >> the past, but I think I'll be switching to dotNetInstaller soon.
> >>
> >> -Adam
> >>
> >> On Thu, Mar 15, 2012 at 11:43 AM, John Cooper
> wrote:
> >>
> >>> I've seen the same bugs CP has seen.  I've got it set in my
> >>> installers, but only because CD demands it.  Setting it causes a
> >>> fair number of install failures, particular in install/repair/uninstall 
> >>> cycles.
> >>>
> >>> --
> >>> John Merryweather Cooper
> >>> Build & Install Engineer - ESA
> >>> Jack Henry & Associates, Inc.®
> >>> Shawnee Mission, KS  66227
> >>> Office:  913-341-3434 x791011
> >>> jocoo...@jackhenry.com
> >>> www.jackhenry.com
> >>>
> >>>
> >>>
> >>>
> >>> -Original Message-
> >>> From: Alec Swan [mailto:alecs...@gmail.com]
> >>> Sent: Thursday, March 15, 2012 11:30 AM
> >>> To: General discussion for Windows Installer XML toolset.
> >>> Subject: Re: [WiX-users] Setting MsiLogFileLocation property
> >>>
> >>> The following thread implied that the file log location can be set
> >>> through MsiLogFileLocation property in WIX:
> >>>
> >>> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Msi-Lo
> >>> gging-td707004.html#a707011
> >>>
> >>> But it sounds like Rob is saying this is not possible.
> >>>
> >>> So, how can I reliably enable MSI logging programmatically in WIX
> >>> code and ideally set the location of the log file? We need to
> >>

Re: [WiX-users] Setting MsiLogFileLocation property

[Chad Petersen]

I was also going to point out that Rob already responded with the same info and 
you don't get much more "WiX Team" than that.

-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com] 
Sent: Thursday, March 15, 2012 11:07 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Setting MsiLogFileLocation property

Given that WiX generates MSI files and the MSI MSDN docs say you can't set it, 
and my testing also indicates that you can't set it, I don't see how you could 
expect a different answer from the WiX Team! It's nothing to do with WiX, or 
InstallShield or any other tool that generates MSI files. Setting log file 
location is something you do on the command line to the install or equivalent 
(MsiInstallProduct parameter). 

Phil W 

-Original Message-
From: Alec Swan [mailto:alecs...@gmail.com] 
Sent: Thursday, March 15, 2012 10:44 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Setting MsiLogFileLocation property

Phil, thank you for sharing your experience.

I would like to keep this thread active until we get a definite answer
from the WIX team. Whether it is "You can't enable MSI logging in the
current version of WIX but will be available in version x.x" or "This
is how you do this ..." - it will still be very helpful.

Thanks,

Alec

On Thu, Mar 15, 2012 at 11:32 AM, Wilson, Phil  wrote:
> You can't set MsiLogFileLocation, as the MSDN docs pretty much say. You can 
> try to set it but it's ineffective. If you set it in the property table it 
> just gets overwritten. If you set it with a type 51 it just gets ignored.
>
> Phil W
>
> -Original Message-
> From: Alec Swan [mailto:alecs...@gmail.com]
> Sent: Thursday, March 15, 2012 10:09 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Setting MsiLogFileLocation property
>
> Adam,
>
> This post indicates that it is possible to set MSI property from WIX:
> http://blogs.technet.com/b/alexshev/archive/2009/05/16/from-msi-to-wix-part-23-dll-custom-actions-logging-and-setting-properties.aspx
>
> If this is true, shouldn't I be able to use this approach to set some
> kind of MSI property to force logging and/or configure location of the
> log file?
>
> Enabling logging seems to be a pretty common question on the WIX
> forum, can we have WIX team to provide a recommendation on how to do
> this?
>
> Thanks,
>
> Alec
>
> On Thu, Mar 15, 2012 at 10:54 AM, Adam Kadzban
>  wrote:
>> Alec,
>>
>> As far as I know, you can't set the log file location inside WIX because
>> you need to tell msiexec where to write the log file to before actually
>> starting the MSI.  You need some sort of bootstrapper that calls msiexec
>> with the logging options. I've used IExpress in the past, but I think I'll
>> be switching to dotNetInstaller soon.
>>
>> -Adam
>>
>> On Thu, Mar 15, 2012 at 11:43 AM, John Cooper wrote:
>>
>>> I've seen the same bugs CP has seen.  I've got it set in my installers,
>>> but only because CD demands it.  Setting it causes a fair number of install
>>> failures, particular in install/repair/uninstall cycles.
>>>
>>> --
>>> John Merryweather Cooper
>>> Build & Install Engineer - ESA
>>> Jack Henry & Associates, Inc.®
>>> Shawnee Mission, KS  66227
>>> Office:  913-341-3434 x791011
>>> jocoo...@jackhenry.com
>>> www.jackhenry.com
>>>
>>>
>>>
>>>
>>> -Original Message-
>>> From: Alec Swan [mailto:alecs...@gmail.com]
>>> Sent: Thursday, March 15, 2012 11:30 AM
>>> To: General discussion for Windows Installer XML toolset.
>>> Subject: Re: [WiX-users] Setting MsiLogFileLocation property
>>>
>>> The following thread implied that the file log location can be set through
>>> MsiLogFileLocation property in WIX:
>>>
>>> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Msi-Logging-td707004.html#a707011
>>>
>>> But it sounds like Rob is saying this is not possible.
>>>
>>> So, how can I reliably enable MSI logging programmatically in WIX code and
>>> ideally set the location of the log file? We need to support Windows XP SP2
>>> and higher.
>>>
>>> Thanks,
>>>
>>> Alec
>>>
>>> On Thu, Mar 15, 2012 at 10:05 AM, Christopher Painter 
>>> wrote:
>>> > I don't know if this is common knowledge but I don't set the
>>> > MsiLogging property anymore.  There' s a known bug in Windows 7 where
>>> > Explorer / Shell can lose reference to the installer log file location
>>> > and it causes the installer to crash out.    It can manifest itself on
>>> > uninstall  which means you are stuck unless you run the uninstall from
>>> > the command line passing in an explicit path.
>>> >
>>> > 
>>> >
>>> > From: "Rob Mensching" 
>>> >
>>> > Sent: Thursday, March 15, 2012 11:02 AM
>>> >
>>> > To: "General discussion for Windows Installer XML toolset."
>>> > 
>>> >
>>> > Subject: Re: [WiX-users] Setting MsiLogFileLocation property
>>> >
>>> >
>>> > I don't think you can set the log fi

Re: [WiX-users] Mouseover

[Chad Petersen]

I'm not sure if the ToolTip attribute works on a Text Control. I'll let
you experiment.


-Original Message-
From: James DellaRosa [mailto:jdellar...@aspexcorp.com] 
Sent: Monday, March 05, 2012 1:10 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Mouseover

That works as far as a hover over event is concerned thanks! Now a more
difficult concept... is there a way to make it so that the ToolTip
attribute can reference another control, say a text control?

-Original Message-----
From: Chad Petersen [mailto:chad.peter...@harlandfs.com] 
Sent: Monday, March 05, 2012 3:59 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Mouseover

Check out the ToolTip attribute of the Control element. Should do
exactly what you are looking for. At least that is how I use it.



-Original Message-
From: James DellaRosa [mailto:jdellar...@aspexcorp.com]
Sent: Monday, March 05, 2012 12:35 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Mouseover

I was wondering if there was any way to have text show up when a user
hover's over a checkbox?  For example let's say that someone has a few
checkboxes that they can select from that would allow them to install
separate products (FeatureX, FeatureY, FeatureZ).  I want to be able to
have the use hover over the checkbox for FeatureX and have a more
in-depth description of what FeatureX does appear next to the checkbox.
If anyone has any insight on this subject could let please let me know,
thank you in advance for your time and help.

--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Mouseover

[Chad Petersen]

Check out the ToolTip attribute of the Control element. Should do
exactly what you are looking for. At least that is how I use it.



-Original Message-
From: James DellaRosa [mailto:jdellar...@aspexcorp.com] 
Sent: Monday, March 05, 2012 12:35 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Mouseover

I was wondering if there was any way to have text show up when a user
hover's over a checkbox?  For example let's say that someone has a few
checkboxes that they can select from that would allow them to install
separate products (FeatureX, FeatureY, FeatureZ).  I want to be able to
have the use hover over the checkbox for FeatureX and have a more
in-depth description of what FeatureX does appear next to the checkbox.
If anyone has any insight on this subject could let please let me know,
thank you in advance for your time and help.

--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to reference a wxs file from another

[Chad Petersen]

An option I use on the candle command line is just to pass an arg of
*.wxs rather than calling each. Likewise on the light command I pass in
*.wixobj.

I find it cuts down on the length of the command line.

-Original Message-
From: Ian Williams [mailto:iawil...@microsoft.com] 
Sent: Thursday, March 01, 2012 1:18 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to reference a wxs file from another

Yep, you need to reference something in a fragment (DirectoryRef,
ComponentRef, etc) to load the fragment (it will all be loaded, note).

Also remember to include allt he .wxs files in your call to candle and
light.

Ian

-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com] 
Sent: Thursday, March 01, 2012 1:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to reference a wxs file from another

You need a reference element to any one bit inside the fragment.  The
way Wix linking currently works, a linkage to one item in a fragment
brings in the whole fragment.

For example, if you have a Component element in a fragment, you would
link in the fragment using a ComponentRef with the appropriate Id
attribute.

--
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: Troy Teixeira [mailto:tteixe...@polariswireless.com]
Sent: Thursday, March 01, 2012 2:58 PM
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] How to reference a wxs file from another

I know that this is a very elementary question since I'm new to this,
but could someone tell what lines of code I would add to a WXS file to
reference it to one containing Fragments.

I have a Product.wxs file and another wxs file named Directory.wxs which
contains a bunch of Fragments. How can I tell the Product.wxs file to
use the Directory.wxs file? Below is the code from the Product.wxs file.

The situation is that when the automated build is happening the MSI file
is not including all of the necessary files for the program to work.


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

   
 
 

  

  
  
  

  

   


  

  



  



  


  
  
  

  





--
Virtualization & Cloud Management Using Capacity Planning Cloud
computing makes use of virtualization - but cloud computing also focuses
on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
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.



--
Virtualization & Cloud Management Using Capacity Planning Cloud
computing makes use of virtualization - but cloud computing also focuses
on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users







--
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Check running installer by Administrator or not

[Chad Petersen]

Is this happening across all supported operating systems or have you
been able to narrow it down to something like Windows 2008 Server and
Windows 7, for example? Sounds like UAC *might* be involved. When logged
in as the Domain User in Administrators group do a right click on your
MSI and choose "Run as Administrator" if you have that option and see if
it runs or not.

-Original Message-
From: shengyixing [mailto:shengyix...@hotmail.com] 
Sent: Wednesday, February 29, 2012 6:38 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Check running installer by Administrator or not

anyone knows this? Thanks.

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Check-runn
ing-installer-by-Administrator-or-not-tp7045540p7331421.html
Sent from the wix-users mailing list archive at Nabble.com.


--
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Several questions related to: Automatic version update, Prompt for installation path, Desktop Shortcut

[Chad Petersen]

I can probably answer one fairly easily. For the shortcut put it inside
of your file element


Shortcut Id="DesktopShortcut" Directory="DesktopFolder"
Advertise="yes" Name="Hello World" Icon="HelloWorld.exe">
  



-Original Message-
From: Troy Teixeira [mailto:tteixe...@polariswireless.com] 
Sent: Thursday, February 23, 2012 10:48 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Several questions related to: Automatic version
update,Prompt for installation path, Desktop Shortcut

Good morning all,
 
I have been tasked with gathering the information for setting up a
program. I'm new to this and really could use the help.
 
Questions:
1.   How do I set the correct path for the shortcut on the desktop
to point to the executable, currently it's not working?
2.   What code do I need to add so that when I run the MSI
installation it will prompt me to input an installation path instead of
using the default?
3.   What code do I need to add so that the version is automatically
updated/incremented with each new build?
 
The contents of the Product.wxs file is pasted below.
 



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

 


  

  



  

  

  
  

  


  



 

--
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Combining 32- and 64-bit installers

[Chad Petersen]

That's been my experience. If I set Platform="x64" to make a 64-bit installer 
then it won't run on 32-bit systems.

-Original Message-
From: Dieter Lunn [mailto:coder2...@gmail.com] 
Sent: Wednesday, January 25, 2012 12:49 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Combining 32- and 64-bit installers

No. MSI can only support one architecture per script as far as I know.
You still need a bootstrapper to launch the appropriate installer.

Dieter Lunn
http://ubiety.ca



On Wed, Jan 25, 2012 at 2:40 PM, Malcolm D. McCrimmon
 wrote:
> I'm working for a company that's currently overhauling its evaluation 
> process, and one of the things we're trying to do is combine our 32- and 
> 64-bit MSI installers into one package.  I saw that on stack overflow 
> (http://stackoverflow.com/questions/1922259/how-to-implement-single-installer-for-32-64-platforms),
>  this question had already been asked and the answer was "not possible"-that 
> I would have to use a bootstrapper to combine the two MSI's.  That question 
> was answered in 2009, though; has this changed since?
>
> Thanks,
> Malcolm
> --
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users

--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] MSI not creating Virtual Directory

[Chad Petersen]

Do you have a separate WebSite element in your code? I see the WebSite
attribute on the WebVirtualDir element, but I'm not seeing the WebSite
element. Maybe you didn't paste in into your e-mail.





-Original Message-
From: Bourne, Kevin [mailto:kevin.bou...@chasepaymentech.com] 
Sent: Wednesday, January 04, 2012 7:15 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] MSI not creating Virtual Directory

I have WIX creating a web site MSI. It puts everything in the correct
directory in wwwroot but does not create it as an application (virtual
directory) under the web site in IIS. The script is below.
Main.wxs



..


  



  Installed OR IISROOT


..


   
  ...

  




.

  



.





Web.wxs


  




  





  

Kevin Bourne | Software Developer | Chase Paymentech
..
JPMorgan Chase & Co.

--
Learn more about Chase Paymentech Solutions,LLC payment processing
services at www.chasepaymentech.com.

THIS MESSAGE IS CONFIDENTIAL.  This e-mail message and any attachments
are proprietary and confidential information intended only for the use
of the recipient(s) named above.  If you are not the intended recipient,
you may not print, distribute, or copy this message or any attachments.
If you have received this communication in error, please notify the
sender by return e-mail and delete this message and any attachments from
your computer.




--
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a
complex
infrastructure or vast IT resources to deliver seamless, secure access
to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI
infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Util:FileShare or FileSharePermissions isremoving additional users on minor/small updates.

[Chad Petersen]

If you open up your MSP in Orca does it have a FileShare and/or
FileSharePermissions tables? It sounds like it does based off of the
behavior you describe, but I'd hope it doesn't because I'd think
(ideally) your minor update should leave the shares and permissions
alone that were created by the major installer as well as added since
the install.

If those tables were there I think I'd try making a copy of the MSP,
then use Orca to drop those two tables and save and test it to see if
the same thing happened. Using the modified MSP, of course.


-Original Message-
From: McCain, Jon [mailto:jon.mcc...@inin.com] 
Sent: Monday, December 12, 2011 5:32 AM
To: General discussion for Windows Installer XML toolset.
Cc: McCain, Jon
Subject: Re: [WiX-users] Util:FileShare or FileSharePermissions
isremoving additional users on minor/small updates.

Anyone have any other thoughts on this?

Jon W. McCain | Software Engineer - Install
phone & fax +1.317.715.8462 | jon.mcc...@inin.com

Interactive Intelligence Inc.
Deliberately Innovative
www.inin.com



-Original Message-
From: McCain, Jon 
Sent: Friday, December 09, 2011 8:31 AM
To: General discussion for Windows Installer XML toolset.
Cc: McCain, Jon
Subject: RE: [WiX-users] Util:FileShare or FileSharePermissions is
removing additional users on minor/small updates.

I am referring to a minor upgrade not a major in this instance. The
product code remains the same and an MSP is used for the install.

Jon W. McCain | Software Engineer - Install phone & fax +1.317.715.8462
| jon.mcc...@inin.com

Interactive Intelligence Inc.
Deliberately Innovative
www.inin.com



-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Friday, December 09, 2011 4:47 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Util:FileShare or FileSharePermissions is
removing additional users on minor/small updates.

If by "the update" you're meaning a major update then you can avoid the
component being reinstalled by scheduling RemoveExistingProducts late -
one of the latter 2 options here:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa371197%28v=vs.
85%29
.aspx
Components that exist in both the old and new installers are not
reinstalled.

-Original Message-
From: McCain, Jon [mailto:jon.mcc...@inin.com]
Sent: 08 December 2011 18:18
To: wix-users@lists.sourceforge.net
Cc: McCain, Jon
Subject: [WiX-users] Util:FileShare or FileSharePermissions is removing
additional users on minor/small updates.

I am experiencing an issue where a network share created with
util:FileShare is overwriting post install added members to the Share
Permissions DACL. The components look like this for the GA install:

  

  


  
  

  

  

These do not change during minor updates but when the update is applied
any additional permissions that have been added are lost. I attempted to
add Conditions to the components but to only run when "Not Installed" is
true but that didn't resolve the issue. The only solution I can think of
is a custom action that creates a cache of the share information and
later restores it. I searched the bugs on sourceforge and do not see a
specific one for this issue.

Any and all help is appreciated.

Regards,
Jon W. McCain | Software Engineer - Install


-
-
Cloud Services Checklist: Pricing and Packaging Optimization This white
paper is intended to serve as a reference, checklist and point of
discussion for anyone considering optimizing the pricing and packaging
model of a cloud services business. Read Now!
http://www.accelacomm.com/jaw/sfnl/114/51491232/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and
requires that you delete it without acting upon or copying any of its
contents, and we further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.
Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire
SL6 7DY, UK.



--
Cloud Services Checklist: Pricing and Packaging Optimization This white
paper is intended to serve as a reference, checklist and point of
discussion for anyone considering optimizing the pricing and packaging
model of a cloud services business. Read Now!
http://www.accelacomm.com/jaw/sfnl/114/51491232/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
Learn Windows Azure Live!  Tuesday

Re: [WiX-users] Conditional Components based on OS ?

[Chad Petersen]

http://msdn.microsoft.com/en-us/library/windows/desktop/aa370556(v=vs.85
).aspx

Would probably look about like this. You don't have to use CDATA blocks,
but my example used the > symbol so I just went with it.



  



  



  



  



-Original Message-
From: Michael Tissington [mailto:michael_tissing...@ciqual.com] 
Sent: Thursday, December 08, 2011 7:04 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] Conditional Components based on OS ?

I have four components XP, XP64, Vista32+ and Vista64+

How can I create conditions for these components?



--
Cloud Services Checklist: Pricing and Packaging Optimization
This white paper is intended to serve as a reference, checklist and
point of 
discussion for anyone considering optimizing the pricing and packaging
model 
of a cloud services business. Read Now!
http://www.accelacomm.com/jaw/sfnl/114/51491232/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Cloud Services Checklist: Pricing and Packaging Optimization
This white paper is intended to serve as a reference, checklist and point of 
discussion for anyone considering optimizing the pricing and packaging model 
of a cloud services business. Read Now!
http://www.accelacomm.com/jaw/sfnl/114/51491232/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Wix Uninstall - MaintenanceTypeDlg, VerifyReadyDlg Dialog sequence is Shown Twice

[Chad Petersen]

The inner text in a Publish element is the Condition expression. An
inner text of 1 says to "always do it". I could be off here, but it
seems like you just need to set up a proper Condition for each inner
text to only show the given dialog under a given condition.

Mine look a bit like this






-Original Message-
From: Robert Hermann [mailto:rob.herm...@nicewareintl.com] 
Sent: Tuesday, December 06, 2011 12:43 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Wix Uninstall - MaintenanceTypeDlg, VerifyReadyDlg
Dialog sequence is Shown Twice

When I goto to remove my installed product by running the installer
twice and going into maintenance mode,   here is the sequence of dialogs
I get


1.   MaintenanceWelcomeDlg.  Click next

2.   MaintenanceTypeDlg  click remove

3.   VerifyReadyDlg click remove

4.   MaintenanceTypeDlg click remove

5.   VerifyReadyDlg click remove

6.   Product uninstalls 

Here is my snippet of code to

1

1
1
1

 NOT Installed
Installed

I've tried run this uninstall from the command line but when I run it
with msiexec /uninstall .. it uninstalls without the repeating dialog
sequence.

Rob


--
Cloud Services Checklist: Pricing and Packaging Optimization
This white paper is intended to serve as a reference, checklist and
point of 
discussion for anyone considering optimizing the pricing and packaging
model 
of a cloud services business. Read Now!
http://www.accelacomm.com/jaw/sfnl/114/51491232/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Cloud Services Checklist: Pricing and Packaging Optimization
This white paper is intended to serve as a reference, checklist and point of 
discussion for anyone considering optimizing the pricing and packaging model 
of a cloud services business. Read Now!
http://www.accelacomm.com/jaw/sfnl/114/51491232/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Is major update supposed to duplicate the add/removeprograms entry?

[Chad Petersen]

Sounds to me like you only need to schedule RemoveExistingProducts in your 
InstallExecuteSequnce.
 

 




From: Robert Lee [mailto:genrobert...@gmail.com]
Sent: Wed 11/30/2011 3:12 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Is major update supposed to duplicate the 
add/removeprograms entry?



I would like to develop an installer so that it would NOT force the user to
uninstall the application manually prior to installing new version. Just
running the new msi should update everything automatically.
As far as I understood the wix book, in order to achieve that, I should set
product ID in the markup to "*", keep the upgrade code, and increase
version number. But when I run the new msi, a new entry is added to
add/remove programs. How to prevent that?
--
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] removing broken installations from Windows XP

[Chad Petersen]

Microsoft used to provide the Windows Clean-up Utility (MSIZAP.EXE was
one common name) but I believe they must have removed it from their web
site. 

This might be a viable copy of that same program. They seem to indicate
the author is Microsoft Corp.

http://www.majorgeeks.com/Windows_Installer_CleanUp_Utility_d4459.html


-Original Message-
From: Remi [mailto:therealr...@gmail.com] 
Sent: Tuesday, November 29, 2011 7:26 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] removing broken installations from Windows XP

OK, I know now I need some virtual pc software for testing
installations.
But I still have to clean what I messed up already.

Basically I ended up installing some components to some random,
inexistent,
incorrect path (set in a custom action...). I didn't get any error
dialog
while installing, but I did during uninstall - it complained something
about the bogus path being inaccessible. In my ignorance I run the
installer few more times with the same error in my custom action. So I
have
a few unremovable entries in Add/Remove Programs. How to clean this up?

--
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Use files in temp dir during installation

[Chad Petersen]

That does seem overly complex right out of the gate. Have you taken a good look 
at the Binary element? This is how I make my files available to my custom 
actions without having to copy anything to the local computer. Might not be 
what you are after, but it's worth mentioning.

-Original Message-
From: Lluís Batlle i Rossell [mailto:llbat...@aqsense.com] 
Sent: Tuesday, November 29, 2011 6:21 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Use files in temp dir during installation

Hello,

we need some files (distributed with the MSI) to be in some path only 
for the execution of some custom actions. Then, after the installer 
finished, the files should be removed.

We've tried simply putting them as  in a component inside a 
TempFolder , but at the time of the customAction the files 
are not there.

So, we have little idea on how to do that. Any suggestion on how to 
achieve that?

Thank you,
Lluís.
-- 
Lluís Batlle i Rossell
Software and Electronics Engineer
AQSENSE S.L.
C/ Pic de Peguera, 15
17003 Girona
Catalunya
Spain
Phone: +34 972 183 215
Fax: +34 972 487 487
http://www.aqsense.com/


--
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] install file from subfolder

[Chad Petersen]

Absolutely possible. Wouldn't be much fun if all files on installation
media had to be in the same folder. Wouldn't even work for files with
the same names that should go into different subfolders like you are
asking about.

On your hard drive just set up the folders the way you ultimately want
them and then run Heat.exe against this folder and it will create a WiX
output sample that you could then merge into your project.

But, yes, totally possible. I'd call it the "norm".

-Original Message-
From: Tomasz Grobelny [mailto:tom...@grobelny.oswiecenia.net] 
Sent: Monday, November 14, 2011 12:44 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] install file from subfolder

On Monday 14 November 2011 20:14:00 Tomasz Grobelny wrote:
> Is it possible to install file that is located in subfolder of folder
in
> which msi file is located? The installation media would look like
this:
> rootfolder\
>   test.msi
>   subfolder1\
> test.dll
>   subfolder2\
> test.dll
>   subfolder3\
> test.dll
> 
> Can this be done without manually specifying Media element for each
> subfolder?
> 
After a bit of testing: is it possible to achieve such an effect in MSI
at 
all? And if so, how?
-- 
Regards,
Tomasz Grobelny


--
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Validating Web site in IIS7 - WiX 3.5

[Chad Petersen]

That looks like some promising VB. Thanks Greg and John for the quick
replies!

-Original Message-
From: Gregory Swanson [mailto:gswan...@athoc.com] 
Sent: Friday, October 21, 2011 1:05 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Validating Web site in IIS7 - WiX 3.5

Using the IIS 7 API you would do something like this
(http://www.iis.net/ConfigReference/system.applicationHost/sites):

Function CheckWebSiteExists(name)
Set adminManager =
CreateObject("Microsoft.ApplicationHost.WritableAdminManager")
adminManager.CommitPath = "MACHINE/WEBROOT/APPHOST"

Set sitesSection =
adminManager.GetAdminSection("system.applicationHost/sites",
"MACHINE/WEBROOT/APPHOST")
Set sitesCollection = sitesSection.Collection
siteElementPos = FindElement(sitesCollection, "site",
Array("name", name))

If (siteElementPos = -1) Then
bSiteFound = False
Else
bSiteFound = True
End If
...
End Function

Function FindElement(collection, elementTagName, valuesToMatch)
Dim i, iVal
Dim elem, prop
Dim matches, value

on error resume next

for i = 0 to cint(collection.Count)
Set elem = collection.Item(i)

if err.number <> 0 then
err.clear
FindElement = -1
Exit Function
end if

if (elem.Name = elementTagName) then 
matches = true

for iVal = 0 to ubound(valuesToMatch) step 2

set prop = elem.GetPropertyByName(valuesToMatch(iVal))
value = prop.Value
if (Not IsNull(value)) then
value = cstr(value)
end if
if (value <> valuesToMatch(iVal + 1)) then
matches = false
exit for
end if
next
if (matches) then
FindElement = i
Exit Function
end if
end if
next
FindElement = -1
End Function

Thanks,
Greg

-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com] 
Sent: Friday, October 21, 2011 12:53 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Validating Web site in IIS7 - WiX 3.5

My CA also works fine if I install the IIS6 Compatibility Layer on
Win2008 R2 Server as the old GetObject method uses the Metabase. Was
just hoping to avoid having to install that extra layer. Since we still
have to support 2003 Server right now I need this older method still for
that OS, but had planned on running that only on Win2003 and using some
newer method with Win2008 that didn't require that Compat layer.
Thoughts?

-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Friday, October 21, 2011 12:22 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Validating Web site in IIS7 - WiX 3.5

I query the IIS6 Metabase Compatibility layer (the custom action hasn't
been migrated to a pure IIS7 form using ServerManager ) to populate a
ComboBox (which gets queried for the "Default Web Site" if the UI is
suppressed).  In UI mode, A dialog box with the contents of the ComboBox
is displayed.  The site selected by the user is then used to initialize
a set of website properties (port, certificate, name, description, ip,
header).  An additional dialog is then displayed to allow the user to
override the default ports.  If the default ports are overridden,
additional custom actions run to update the ports (particularly
net.tcp).  In the non UI case, a custom action runs to harvest the UPN
username and password off selected AppPools on the "Default Web Site".
Both this CA and the binding (port) CA's use the IIS7 ServerManager
class.

--
John Merryweather Cooper
Jack Henry & Associates, Inc. (Premier Tech, Inc.) Build & Install
Engineer - jXchange
Office:  913-341-3434 x791011
jocoo...@jackhenry.com




-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Friday, October 21, 2011 1:48 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Validating Web site in IIS7 - WiX 3.5

Trying to figure out the right approach to validate that a Web site
already exists during my install. In IIS6 I used
GetObject("IIS://localhost/w3svc") and queried that for the info the
user typed in. Any of you that target IIS7+ how are you dealing with
this? I am using a Web site locator for an existing Web site rather than
creating my own Web site. I'd probably want to do this as a DoAction
during my InstallUISequence.

Suggestions or code snippets would be great!

Thanks
Chad


---

Re: [WiX-users] Validating Web site in IIS7 - WiX 3.5

[Chad Petersen]

My CA also works fine if I install the IIS6 Compatibility Layer on
Win2008 R2 Server as the old GetObject method uses the Metabase. Was
just hoping to avoid having to install that extra layer. Since we still
have to support 2003 Server right now I need this older method still for
that OS, but had planned on running that only on Win2003 and using some
newer method with Win2008 that didn't require that Compat layer.
Thoughts?

-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com] 
Sent: Friday, October 21, 2011 12:22 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Validating Web site in IIS7 - WiX 3.5

I query the IIS6 Metabase Compatibility layer (the custom action hasn't
been migrated to a pure IIS7 form using ServerManager ) to populate a
ComboBox (which gets queried for the "Default Web Site" if the UI is
suppressed).  In UI mode, A dialog box with the contents of the ComboBox
is displayed.  The site selected by the user is then used to initialize
a set of website properties (port, certificate, name, description, ip,
header).  An additional dialog is then displayed to allow the user to
override the default ports.  If the default ports are overridden,
additional custom actions run to update the ports (particularly
net.tcp).  In the non UI case, a custom action runs to harvest the UPN
username and password off selected AppPools on the "Default Web Site".
Both this CA and the binding (port) CA's use the IIS7 ServerManager
class.

--
John Merryweather Cooper
Jack Henry & Associates, Inc. (Premier Tech, Inc.)
Build & Install Engineer - jXchange
Office:  913-341-3434 x791011
jocoo...@jackhenry.com




-----Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com] 
Sent: Friday, October 21, 2011 1:48 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Validating Web site in IIS7 - WiX 3.5

Trying to figure out the right approach to validate that a Web site
already exists during my install. In IIS6 I used
GetObject("IIS://localhost/w3svc") and queried that for the info the
user typed in. Any of you that target IIS7+ how are you dealing with
this? I am using a Web site locator for an existing Web site rather than
creating my own Web site. I'd probably want to do this as a DoAction
during my InstallUISequence.

Suggestions or code snippets would be great!

Thanks
Chad



--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn about
Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
___
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.



--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Validating Web site in IIS7 - WiX 3.5

[Chad Petersen]

Trying to figure out the right approach to validate that a Web site
already exists during my install. In IIS6 I used
GetObject("IIS://localhost/w3svc") and queried that for the info the
user typed in. Any of you that target IIS7+ how are you dealing with
this? I am using a Web site locator for an existing Web site rather than
creating my own Web site. I'd probably want to do this as a DoAction
during my InstallUISequence.

Suggestions or code snippets would be great!

Thanks
Chad


--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Replacing .Net v.3 Assemblieswith.Net v.4Assembliesduring Major Upgrade

[Chad Petersen]

It might not be an issue, but just reading your code I'd tend to avoid
the SharedDllRefCount. But, reading that also makes me wonder if there
was a particular reason for using that? Do other packages you know of
also deliver the same DLL?

I'm not sure how to generate an uninstall log when the Major Upgrade is
the one doing the uninstall of the prior package. Maybe the registry
keys for voicewarmup?

Start Registry Editor (Regedt32.exe), and then create the following path
and keys in the registry: 
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer

Reg_SZ: Logging
Value: voicewarmup

The verbose log file will probably be the only way to see what is going
on behind the scenes.

You are sure that the Major Upgrade is removing the other package?
Control Panel only shows the newest one when you are done installing it?




-Original Message-
From: Gregory Swanson [mailto:gswan...@athoc.com] 
Sent: Tuesday, October 18, 2011 11:28 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Replacing .Net v.3 Assemblieswith.Net
v.4Assembliesduring Major Upgrade

They're installed using the Wix File element for .Net Assemblies, like
this:




-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com] 
Sent: Tuesday, October 18, 2011 11:16 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Replacing .Net v.3 Assemblies with.Net
v.4Assembliesduring Major Upgrade

How are the files being GAC'ed in the old installer?  Custom action or
using the File element attributes?

--
John Merryweather Cooper
Jack Henry & Associates, Inc. (Premier Tech, Inc.) Build & Install
Engineer - jXchange
Office:  913-341-3434 x791011
jocoo...@jackhenry.com




-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Tuesday, October 18, 2011 12:54 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Replacing .Net v.3 Assemblies with .Net
v.4Assembliesduring Major Upgrade

That's very odd. The old MSI that installed those v.3 assemblies is the
one that should be removing them, not the newer MSI. If you don't
consider the upgrade, but just uninstall that older MSI through Control
Panel does it not remove the GAC'ed files? The Major Upgrade simply
uninstalls that previous package so no real extra mechanism is usually
required. Sounds like an issue of some sort with that older MSI. You've
probably done the best given the situation, but the real question is
what caused the situation in the first place? We use lots of GAC'ed
files and have not run into a given installer not uninstalling the
GAC'ed files it is responsible for.



-Original Message-
From: Gregory Swanson [mailto:gswan...@athoc.com]
Sent: Tuesday, October 18, 2011 10:44 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Replacing .Net v.3 Assemblies with .Net
v.4Assembliesduring Major Upgrade

Follow up - I implemented a custom action that uses gacUtil.exe to
uninstall the old assemblies and scheduled it just after CostFinalize in
the InstallExecuteSequence.

-Original Message-
From: Gregory Swanson [mailto:gswan...@athoc.com]
Sent: Thursday, October 13, 2011 3:50 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Replacing .Net v.3 Assemblies with .Net v.4
Assembliesduring Major Upgrade

Hello:

 

I have an MSI developed with WIX, which packages (among other things) a
few .Net DLLs.  Recently, these .Net v.3 DLLs have been updated to .Net
v.4.

 

I noticed that after running an upgrade, the .Net v.3 Assemblies remain
in the .Net 2 GAC (I noticed this after upgrades on Windows Server 2003
R2 and Windows Server 2008 R2).  What I don't understand is: since I am
installing .Net v.4 Assemblies, should the .Net 3 Assemblies be removed
by the MSI or not?  The .Net v.4 Assemblies are installed in the .Net 4
GAC and the application seems to work fine, but I would like to remove
the old v.3 Assemblies during upgrade.

While investigating how to do this, I found a reference to Bob Arnson's
blog ( http://www.joyofsetup.com/2008/12/30/paying-for-upgrades/ ) and
followed his advice by setting RemoveExistingProducts to execute Before
InstallInitialize.  It was set to After InstallFinalize previously.
Checking the verbose log, I do see that RemoveExistingProducts now
executes just before InstallInitialize, but the v.3 Assemblies were not
removed.  The DLLs are authored one per component.

 

So I thought that maybe the scheduling of RemoveExistingProducts is not
the reason, maybe something else like file versioning (we have a build
engineer who manages that, and since the builds are automated I don't
usually notice a problem right away).  I checked the file versions, and
one .Net v.3 DLL has a File Version of 2.3.0.0, while the .Net v.4 copy
has a File Version of 2.10.0.0.  The Assembly v

Re: [WiX-users] Replacing .Net v.3 Assemblies with .Net v.4Assembliesduring Major Upgrade

[Chad Petersen]

That's very odd. The old MSI that installed those v.3 assemblies is the
one that should be removing them, not the newer MSI. If you don't
consider the upgrade, but just uninstall that older MSI through Control
Panel does it not remove the GAC'ed files? The Major Upgrade simply
uninstalls that previous package so no real extra mechanism is usually
required. Sounds like an issue of some sort with that older MSI. You've
probably done the best given the situation, but the real question is
what caused the situation in the first place? We use lots of GAC'ed
files and have not run into a given installer not uninstalling the
GAC'ed files it is responsible for.



-Original Message-
From: Gregory Swanson [mailto:gswan...@athoc.com] 
Sent: Tuesday, October 18, 2011 10:44 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Replacing .Net v.3 Assemblies with .Net
v.4Assembliesduring Major Upgrade

Follow up - I implemented a custom action that uses gacUtil.exe to
uninstall the old assemblies and scheduled it just after CostFinalize in
the InstallExecuteSequence.

-Original Message-
From: Gregory Swanson [mailto:gswan...@athoc.com] 
Sent: Thursday, October 13, 2011 3:50 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Replacing .Net v.3 Assemblies with .Net v.4
Assembliesduring Major Upgrade

Hello:

 

I have an MSI developed with WIX, which packages (among other things) a
few .Net DLLs.  Recently, these .Net v.3 DLLs have been updated to .Net
v.4.

 

I noticed that after running an upgrade, the .Net v.3 Assemblies remain
in the .Net 2 GAC (I noticed this after upgrades on Windows Server 2003
R2 and Windows Server 2008 R2).  What I don't understand is: since I am
installing .Net v.4 Assemblies, should the .Net 3 Assemblies be removed
by the MSI or not?  The .Net v.4 Assemblies are installed in the .Net 4
GAC and the application seems to work fine, but I would like to remove
the old v.3 Assemblies during upgrade.

While investigating how to do this, I found a reference to Bob Arnson's
blog ( http://www.joyofsetup.com/2008/12/30/paying-for-upgrades/ ) and
followed his advice by setting RemoveExistingProducts to execute Before
InstallInitialize.  It was set to After InstallFinalize previously.
Checking the verbose log, I do see that RemoveExistingProducts now
executes just before InstallInitialize, but the v.3 Assemblies were not
removed.  The DLLs are authored one per component.

 

So I thought that maybe the scheduling of RemoveExistingProducts is not
the reason, maybe something else like file versioning (we have a build
engineer who manages that, and since the builds are automated I don't
usually notice a problem right away).  I checked the file versions, and
one .Net v.3 DLL has a File Version of 2.3.0.0, while the .Net v.4 copy
has a File Version of 2.10.0.0.  The Assembly version is the same for
both DLLs.  I think this is the correct versioning to prevent a
side-by-side deployment when the DLLs are created with the same, or even
with different versions of .Net.

 

I'm pretty sure I could remove the .Net v.3 Assemblies with a simple
Custom Action, but I don't want to do that if there is a better
approach.

 

Thanks in advance for any help.

Greg


--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Using wix how to always overwrite a file?

[Chad Petersen]

Another option is to use the  element tied to the same
Component as your  element. This will always clear out the
existing file prior to the current install writing the new one. Works
for rollback and uninstall.


 
 


The RemoveFiles action is always scheduled before the InstallFiles
action by default, so as long as you don't change that sequence in
InstallExecuteSequence then it should work fine. I consider this the
functional equivalent of the InstallShield "Always Overwrite" setting.




-Original Message-
From: McCain, Jon [mailto:jon.mcc...@inin.com] 
Sent: Tuesday, October 18, 2011 5:33 AM
To: General discussion for Windows Installer XML toolset.
Cc: McCain, Jon
Subject: Re: [WiX-users] Using wix how to always overwrite a file?

You could write a CA to put the file in a temp location each time, check
the creation date on both (or some other unique variable), and then move
it into the proper directory. You would have to write additional code to
handle backup of the pre-existing file in the instance of an update
removal or an total uninstall.

Jon W. McCain | Software Engineer - Install
phone & fax +1.317.715.8462 | jon.mcc...@inin.com

Interactive Intelligence Inc.
Deliberately Innovative
www.inin.com



-Original Message-
From: Pandurangan, Vasanthakumar
[mailto:vasanthakumar.panduran...@hp.com] 
Sent: Tuesday, October 18, 2011 6:50 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Using wix how to always overwrite a file?

Hi,

There are 2 msi installer files, both of them write the same file in the
same location. Objective is to overwrite the file by the latest
installer.
As of now, the file is not versioned. So Installer re-writes the file
only when the modified date is older than created date of the existing
file.

How to change it so that this file is always over written by the latest
installer? What should be the value of "DefaultVersion" attribute in
File tag?
I'm unable to find any example of Wix code which uses "DefaultVersion"
attribute in File element.

Thanks in Advance,
Vasanth


--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] New file not installed

[Chad Petersen]

I had a recent situation where a window with no title had the file "in
use" that I was trying to replace. And the developers on that project
hadn't changed the version so it went like this.

1. MSI detects file in use so schedules a reboot for that to be deleted.
2. MSI does a version check of the file and sees it's the same so
decides it doesn't need to replace anything
3. MSI reboots system and deletes file from step #1 - resulting in no
file

The OnlyDetect="yes" says to keep the product it is looking for.
OnlyDetect="no" says to not only detect but also remove the prior
version(s).

Are these GAC'ed or WinSxS'ed files? Have their versions all changed? If
not this article might explain it.

http://blogs.msdn.com/b/astebner/archive/2007/02/08/assemblies-may-be-mi
ssing-from-the-gac-or-winsxs-cache-after-an-msi-major-upgrade.aspx


-Original Message-
From: Kurt Jensen [mailto:kurt.jen...@us.ophiropt.com] 
Sent: Wednesday, August 17, 2011 1:20 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] New file not installed

> OnlyDetect="yes"
???

> You might also check a clean install to see if all four files get
installed.
yes, a clean install works.

> Do these files contain Version information
yes, all files have strong names

> Is each file in its own Component?
yes

Kurt

-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Wednesday, August 17, 2011 1:51 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] New file not installed

I'm used to Major upgrades removing the previous release(s) so only the
newest major version shows in Add/Remove Programs. But, that probably
won't work if you have OnlyDetect="yes". And maybe that's not what you
want to do.

You might also check a clean install to see if all four files get
installed. If it doesn't work on a clean install then that's probably
the first place to take a look. I'd suppose that is working, just an
idea.

Do these files contain Version information or are they version-less type
of files? Is each file in its own Component?

Just some thinking points.

-Original Message-
From: Kurt Jensen [mailto:kurt.jen...@us.ophiropt.com]
Sent: Wednesday, August 17, 2011 12:25 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] New file not installed

>somehow difficult to describe with few background information.
what information do you need?

>Maybe take the Tramontana tutorial as starting point:
yes, I am following the tutorial

>Are you handling the whole installer as major upgrade ?
yes

>Did any of the assembly versions decrease ?
this is a file that did not exist in the previous installation.
there is no previous version.

Kurt


--
Get a FREE DOWNLOAD! and learn more about uberSVN rich system,
user administration capabilities and model configuration. Take
the hassle out of deploying and managing Subversion and the
tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--

Get a FREE DOWNLOAD! and learn more about uberSVN rich system,
user administration capabilities and model configuration. Take
the hassle out of deploying and managing Subversion and the
tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Get a FREE DOWNLOAD! and learn more about uberSVN rich system, 
user administration capabilities and model configuration. Take 
the hassle out of deploying and managing Subversion and the 
tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Get a FREE DOWNLOAD! and learn more about uberSVN rich system, 
user administration capabilities and model configuration. Take 
the hassle out of deploying and managing Subversion and the 
tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] New file not installed

[Chad Petersen]

I'm used to Major upgrades removing the previous release(s) so only the
newest major version shows in Add/Remove Programs. But, that probably
won't work if you have OnlyDetect="yes". And maybe that's not what you
want to do.

You might also check a clean install to see if all four files get
installed. If it doesn't work on a clean install then that's probably
the first place to take a look. I'd suppose that is working, just an
idea.

Do these files contain Version information or are they version-less type
of files? Is each file in its own Component?

Just some thinking points.

-Original Message-
From: Kurt Jensen [mailto:kurt.jen...@us.ophiropt.com] 
Sent: Wednesday, August 17, 2011 12:25 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] New file not installed

>somehow difficult to describe with few background information.
what information do you need?

>Maybe take the Tramontana tutorial as starting point:
yes, I am following the tutorial

>Are you handling the whole installer as major upgrade ?
yes

>Did any of the assembly versions decrease ?
this is a file that did not exist in the previous installation.
there is no previous version.

Kurt


--
Get a FREE DOWNLOAD! and learn more about uberSVN rich system, 
user administration capabilities and model configuration. Take 
the hassle out of deploying and managing Subversion and the 
tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Get a FREE DOWNLOAD! and learn more about uberSVN rich system, 
user administration capabilities and model configuration. Take 
the hassle out of deploying and managing Subversion and the 
tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How do you share dll's between executabled files

[Chad Petersen]

Oh, and there is a known property called CommonFilesFolder as documented
here.

http://msdn.microsoft.com/en-us/library/aa367994%28VS.85%29.aspx

So, makes it real easy to use.

-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com] 
Sent: Tuesday, June 28, 2011 1:46 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How do you share dll's between executabled
files

We place some of our shared files in C:\Program Files\Common Files\

-Original Message-
From: Robert Hermann [mailto:rob.herm...@nicewareintl.com] 
Sent: Tuesday, June 28, 2011 1:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] How do you share dll's between executabled files

I've got a wix installer that installs a backend service and a  front
end to control the backend service.

The Admin front end is being placed in one directory and the service is
being placed in another directory.  They have a few dlls that I would
like to share between them.

My plan is to install the dlls to one directory and  then have those dll
be seen by the service and frontend.

How would you do this ?

Thanks !

Rob



**
The information in this e-mail and any attachments is confidential and
may be subject to legal professional privilege. It is intended solely
for the attention and use of the named addressee(s). If you are not the
intended recipient or person responsible for delivering this information
to the intended recipient, please notify the sender immediately. Unless
you are the intended recipient or his/her representative you are not
authorized to, and must not, read, copy, distribute, use or retain this
message or any part of it


--
All of the data generated in your IT infrastructure is seriously
valuable.
Why? It contains a definitive record of application performance,
security 
threats, fraudulent activity, and more. Splunk takes this data and makes

sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
All of the data generated in your IT infrastructure is seriously
valuable.
Why? It contains a definitive record of application performance,
security 
threats, fraudulent activity, and more. Splunk takes this data and makes

sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How do you share dll's between executabled files

[Chad Petersen]

We place some of our shared files in C:\Program Files\Common Files\

-Original Message-
From: Robert Hermann [mailto:rob.herm...@nicewareintl.com] 
Sent: Tuesday, June 28, 2011 1:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] How do you share dll's between executabled files

I've got a wix installer that installs a backend service and a  front
end to control the backend service.

The Admin front end is being placed in one directory and the service is
being placed in another directory.  They have a few dlls that I would
like to share between them.

My plan is to install the dlls to one directory and  then have those dll
be seen by the service and frontend.

How would you do this ?

Thanks !

Rob



**
The information in this e-mail and any attachments is confidential and
may be subject to legal professional privilege. It is intended solely
for the attention and use of the named addressee(s). If you are not the
intended recipient or person responsible for delivering this information
to the intended recipient, please notify the sender immediately. Unless
you are the intended recipient or his/her representative you are not
authorized to, and must not, read, copy, distribute, use or retain this
message or any part of it


--
All of the data generated in your IT infrastructure is seriously
valuable.
Why? It contains a definitive record of application performance,
security 
threats, fraudulent activity, and more. Splunk takes this data and makes

sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Show Installer Log file

[Chad Petersen]

I'd suggest taking one step back. You mention a log file created in the temp 
folder. Have you tried running your installer when the temp folder doesn't 
exist or the TEMP variable isn't defined? If you are calling MSIEXEC /L*v and 
wanting it to log to a TEMP folder I recommend you try it in these error 
conditions. MSIEXEC.EXE won't create the folder you want to log to if it 
doesn't exist. So, don't assume you will always be able to create a log file in 
the TEMP folder. Your MSI will simply fail if it can't create the log file.

It will simply say

"Error opening installation log file.  Verify that the specified log file 
location exists and is writable."

You can't really assume that any folder exists. If you want to log reliably you 
must ensure that the folder you want to use exists before running the 
MSIEXEC.EXE command.

Just a word of caution. If I were to test what you are proposing on the surface 
I could break it in an instant.




-Original Message-
From: lokanath devineni [mailto:ldevin...@yahoo.com] 
Sent: Tuesday, June 21, 2011 8:14 AM
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] Show Installer Log file

Hello All,
 
I want to show installer log file created in temp folder on error/cancel  and  
final screen. what are the best ways to do this?
 
Thanks in advance,
 
Loknath 
--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Control keyboard chortcut

[Chad Petersen]

Your isn't working like that already? Well, it's a simple fix, but may
be needed in quite a few places. In the following example the & in
front of the character you want to use as the hotkey should do the
trick.




  [ButtonFont]&Next >
  


-Original Message-
From: Wang, Miaohsi [mailto:miaohsi.w...@invensys.com] 
Sent: Friday, June 03, 2011 11:41 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Control keyboard chortcut

Dear All,

Is there a way to enable the keyboard shortcut on a control on an
install dialog? For example, instead of clicking on the Next button, the
user can simply press the n key while holding down the Alt key to
proceed to the next dialog. Your help will be greatly appreciated.

Thanks,
Miaohsi



*** Confidentiality Notice: This e-mail, including any associated or
attached files, is intended solely for the individual or entity to which
it is addressed. This e-mail is confidential and may well also be
legally privileged. If you have received it in error, you are on notice
of its status. Please notify the sender immediately by reply e-mail and
then delete this message from your system. Please do not copy it or use
it for any purposes, or disclose its contents to any other person. This
email comes from a division of the Invensys Group, owned by Invensys
plc, which is a company registered in England and Wales with its
registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW
(Registered number 166023). For a list of European legal entities within
the Invensys Group, please go to
http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_i
d=77.

You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail
recept...@invensys.com. This e-mail and any attachments thereto may be
subject to the terms of any agreements between Invensys (and/or its
subsidiaries and affiliates) and the recipient (and/or its subsidiaries
and affiliates).


--
Simplify data backup and recovery for your virtual environment with
vRanger.
Installation's a snap, and flexible recovery options mean your data is
safe,
secure and there when you need it. Discover what all the cheering's
about.
Get your free trial download today. 
http://p.sf.net/sfu/quest-dev2dev2 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Discover what all the cheering's about.
Get your free trial download today. 
http://p.sf.net/sfu/quest-dev2dev2 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Application Shortcut Not Placed

[Chad Petersen]

What I find immediately odd is that your sample shows single quotes
around double quotes on the  attribute. I'm thinking it should
be one or the other, but not both. Maybe it's correct, but it is
different than the manual shows, too.

-Original Message-
From: Jonah Dahlquist [mailto:jonahbro...@gmail.com] 
Sent: Thursday, June 02, 2011 2:33 PM
To: wix-users
Subject: [WiX-users] Application Shortcut Not Placed

Hello, world!

I have an application installer created for my app.  Everything works
except the shortcut.  When I install, it does not place the shortcut
in the start menu.  Here's the code:


   
   
   
   
   
   
   


And it's properly referenced in the  item.



The code seems to be to the documentation
(http://wix.sourceforge.net/manual-wix3/create_start_menu_shortcut.htm).
 What might be the problem?

Thanks!

--
Simplify data backup and recovery for your virtual environment with
vRanger.
Installation's a snap, and flexible recovery options mean your data is
safe,
secure and there when you need it. Discover what all the cheering's
about.
Get your free trial download today. 
http://p.sf.net/sfu/quest-dev2dev2 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Discover what all the cheering's about.
Get your free trial download today. 
http://p.sf.net/sfu/quest-dev2dev2 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] need pointers to docs on file-versioning

[Chad Petersen]

Versioning is built into certain files like DLLs and EXEs and not into
other files like XML and text files. That much has nothing to do with
WiX or MSI. Files are either versioned or they aren't. MSI simply
reflects those versions, by default.

-Original Message-
From: Dave Combs [mailto:dave.co...@kaazing.com] 
Sent: Thursday, June 02, 2011 11:56 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] need pointers to docs on file-versioning

Hi,

I just had a couple simple questions, and looking through both the WiX
book
and various Google searches hasn't helped.

* In WiX, how does one indicate that a given file is to be unversioned?
* In WiX, how does one indicate that a given file is versioned?  I see
the
'DefaultVersion' property, but am not sure to what that applies (what's
'default' about this value?)
* Do all the files in an installation have to be at the same version?
If
not, how does one distinguish?  Conversely, if not, do I have to then
specify the version for every file, or is this inherited somehow from
the
ProductVersion setting?

Any quick pointers to docs or discussions or anything else that actually
describes how to specify versioned vs unversioned files would be
helpful.
Everything I've found so far describes how versioned vs unversioned are
updated during upgrades/patches, but not how to specify
versioned/unversioned in the first place.

Thanks!
Dave

--
Simplify data backup and recovery for your virtual environment with
vRanger.
Installation's a snap, and flexible recovery options mean your data is
safe,
secure and there when you need it. Discover what all the cheering's
about.
Get your free trial download today. 
http://p.sf.net/sfu/quest-dev2dev2 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Discover what all the cheering's about.
Get your free trial download today. 
http://p.sf.net/sfu/quest-dev2dev2 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Excluding file types

[Chad Petersen]

Heat /? shows usage. Looks like -ke is keep empty directories. I don't
see a way to exclude files, but maybe somewhere in the mix.


-Original Message-
From: CoolBreeze [mailto:coolbreeze...@googlemail.com] 
Sent: Friday, May 13, 2011 11:20 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Excluding file types

I have a couple of questions, I want to find out from the list.

1. Is it possible to exclude certain file types when harvesting files
with
heat? I'm using Wix 3.5 and I have files that I need to harvest from a
Surround repository folder. Surround like Subversion creates .
files.
I'd like to exclude these files if possible when I harvest the files.

2. During the harvesting of files is it possible to create an empty
directory that gets included in the resulting .wxs file? I need to
include
in my .wxs components file a folder and set permissions on it. I
currently
take the file after it has been created by heat and manually add the
 entry.

Thanks.

--
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] missing assemblies referenced by Custom Action

[Chad Petersen]

http://msdn.microsoft.com/en-us/library/0c6xyb66.aspx



-Original Message-
From: Kurt Jensen [mailto:kurt.jen...@us.ophiropt.com] 
Sent: Wednesday, May 11, 2011 7:44 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] missing assemblies referenced by Custom Action

Yes, the assemblies are referenced by project in the CA project

> set the "build action" to "Content"?
do not know what this means...

-Original Message-
From: Dick Van den Brink [mailto:d_vandenbr...@live.com]
Sent: Wednesday, May 11, 2011 8:35 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] missing assemblies referenced by Custom Action


Did you add the dll to the CA project and set the "build action" to
"Content"?

> From: kurt.jen...@us.ophiropt.com
> Date: Wed, 11 May 2011 08:27:10 -0600
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] missing assemblies referenced by Custom Action
>
> now (all of a sudden...) something quit working
>
> we have a C# custom action that requires a couple of assemblies.  in
> wix3.0 these assemblies were copied into the
> CustomAction.Install.WiX.CA.dll-# directory where the custom action
was
> invoked.  but now using winx3.5 it is failing because it cannot find
these
> dependent assemblies.
>
> originally we were referencing the assemblies by Browse... but this
did
> not work.  changed to referencing the assembly projects.  yesterday
this
> worked.  today it does not.  what did I change?  yes.  actually I
checked
> out some code that worked yesterday but today it does not.
>
> how do I reference assemblies needed by a C# custom action so that
they
> are copied into the temporary directory when the custom action is
invoked?
>
>

--

> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users


--

Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Publishing to GAC

[Chad Petersen]

I might have missed but does this happen during a clean install, upgrade
or both?

-Original Message-
From: Kurt Jensen [mailto:kurt.jen...@us.ophiropt.com] 
Sent: Tuesday, May 10, 2011 1:05 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Publishing to GAC

I remember reading about that.  double checked, the entry in
MsiAssemblyName has a version

we are at a loss as to how to track down the problem.
there are no errors.
any ideas?


-Original Message-
From: Jacques Eloff [mailto:repst...@gmail.com]
Sent: Tuesday, May 10, 2011 12:33 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Publishing to GAC

Ahh, I found that when moving from WiX 2.0 to 3.0/3.5, the assembly file
version wasn't written to the MsiAssemblyName table and it caused
problems
for us during upgrades. The solution in that case was just to add the
-fv
switch to Light, but that only solves upgrade issues.

On Tue, May 10, 2011 at 8:41 AM, Kurt Jensen
wrote:

> yes, we set the Assembly=".net" otherwise we would not get the log
entry
> listing our assembly.  the assembly is properly listed in the
MsiAssembly
> table with attribute=0
>
> we are converting a vs2008/wix3.0 project to vs2010/wix3.5.  in the
wix3.0
> project we only install it to the GAC.  in the new wix3.5 we install
it
> both local and GAC.  the source code for installing to the GAC is
> identical in both projects.
>
>
> 
>  
> Assembly=".net" KeyPath="yes" />
>  
> 
>
> note that CONSOLESERVICEDIRECTORY is never actually created
>
>
> > Make sure that the assembly is signed.
> we are using strong naming but not code signing.  same as in the
wix3.0
> project.
>
>
> surely we would see an entry in the log if there was a problem?
>
>
> -Original Message-
> From: Jacques Eloff [mailto:repst...@gmail.com]
> Sent: Tuesday, May 10, 2011 9:01 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Publishing to GAC
>
> Did you set the Assembly attribute in the File element to ".net"?
>
>  Name="MyAssembly.dll"
> ProcessorArchitecture="msil"/>
>
> Also, as I recall, you need to create a separate directory for the
GAC'd
> assembly. So you would have two  elements for the assembly with
> different parent directories. One to actually install it to disk, the
> other
> one to install it into the GAC.
>
> Make sure that the assembly is signed. You can't install unsigned
> assemblies
> into the GAC.
>
> Take a look at Aaron's blog as well:
> http://blogs.msdn.com/b/astebner/archive/2007/06/21/3450539.aspx
>
> Jacques
> On Tue, May 10, 2011 at 7:46 AM, Kurt Jensen
> wrote:
>
> > we publish one assembly to the GAC.  we find the
MsiPublishAssemblies
> > action
> > in the log file.  there is no error.
> >
> > but the assembly does not appear in the GAC.
> >
> >
> >
> >
> >
> > Action 7:17:10: MsiPublishAssemblies. Publishing assembly
information
> >
> > MSI (s) (F8:2C) [07:17:10:015]: Executing op:
> >
> >
>
AssemblyPublish(Feature=ProductFeature,Component={F23AAD89-8D5F-46C1-879
2-
>
C7988BEF6212}[~]2,AssemblyType=1,,AssemblyName=Spiricon.Interfaces.Conso
le
>
Service,version="1.0.0.0",culture="neutral",publicKeyToken="18293B57E84A
EC
> 4B",processorArchitecture="MSIL",)
> >
> > MsiPublishAssemblies: Application Context:Global, Assembly
> >
> >
>
Name:Spiricon.Interfaces.ConsoleService,version="1.0.0.0",culture="neutr
al
> ",publicKeyToken="18293B57E84AEC4B",processorArchitecture="MSIL"
> >
> > MSI (s) (F8:2C) [07:17:10:030]: Executing op:
> > ActionStart(Name=PublishFeatures,Description=Publishing Product
> > Features,Template=Feature: [1])
> >
> >
> >
> >
> >
> > any ideas how to find out what is wrong?
> >
> >
> >
> >
> >
> > Kurt Jensen
> >
> > Senior Software Engineer
> >
> > Ophir-Spiricon LLC
> >
> >
> >
> > www.ophiropt.com/photonics

> >
> >
> >
> >
> >
> > The True Measure of Laser PerformanceT
> >
> >
>

--
> 
> > Achieve unprecedented app performance and reliability
> > What every C/C++ and Fortran developer should know.
> > Learn how Intel has extended the reach of its next-generation tools
> > to help boost performance applications - inlcuding clusters.
> > http://p.sf.net/sfu/intel-dev2devmay
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
>

--
>  
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> ___
> WiX-users mailing list
> WiX-users@lists.sourcefo

Re: [WiX-users] WiX force copy file.

[Chad Petersen]

My syntax is a bit different than yours, but you might try removing the
[WPFINSTALLDIR] property from your  element. But, I always
nest my Components under a  element, so our approach is
somewhat different.

-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com] 
Sent: Wednesday, April 13, 2011 12:54 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] WiX force copy file.

I cannot seem to get RemoveFile to work. Here is my latest attempt:

  


.








.
  

I still get the error message in the log below. The error message
indicates that the file is unversioned but modified. Hopefullly applying
 correctly will let me essentially overwrite the file.

Thank you.

-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, April 13, 2011 12:21 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX force copy file.

The log file looks like:

MSI (s) (6C:EC) [13:54:36:297]: Executing op:
FileCopy(SourceName=dfl-c3lj.con|app.Config,SourceCabKey=FILE_ServiceApp
Config,DestName=app.Config,Attributes=512,FileSize=32206,PerTick=32768,,
VerifyMedia=1,CheckCRC=0,,,InstallMode=58982400,HashOptions=0,HashPa
rt1=-680126199,HashPart2=1248668224,HashPart3=-1650872411,HashPart4=1522
490087,,)
MSI (s) (6C:EC) [13:54:36:297]: File: D:\Program Files
(x86)\BsiServices\ServiceHost\app.Config;   Won't Overwrite;
Won't patch;Existing file is unversioned but modified

I will look at RemoveFile. It seems kind of counter intuitive that on
installation I want to remove a file. Would I put the 
element in the same component as the component that is installing the
file?



--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and
improve 
application availability and disaster protection. Learn more about
boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] WiX force copy file.

[Chad Petersen]

I only ever specify On="install".

I think of it as asking the install to remove the existing file, no
matter what, prior to copying in the new file. I equate this to the
InstallShield "Always Overwrite" setting.

-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com] 
Sent: Wednesday, April 13, 2011 12:37 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX force copy file.

I add  but on uninstall. This gave me the same "error" do
you usually specify "both" for this kind of situation?

Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com 

-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com] 
Sent: Wednesday, April 13, 2011 2:25 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX force copy file.

Yes. I run into this with text files (xml mostly) a lot. RemoveFile can
go under the same Component as the File element. That's the way I always
use it.

-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, April 13, 2011 12:21 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX force copy file.

The log file looks like:

MSI (s) (6C:EC) [13:54:36:297]: Executing op:
FileCopy(SourceName=dfl-c3lj.con|app.Config,SourceCabKey=FILE_ServiceApp
Config,DestName=app.Config,Attributes=512,FileSize=32206,PerTick=32768,,
VerifyMedia=1,CheckCRC=0,,,InstallMode=58982400,HashOptions=0,HashPa
rt1=-680126199,HashPart2=1248668224,HashPart3=-1650872411,HashPart4=1522
490087,,)
MSI (s) (6C:EC) [13:54:36:297]: File: D:\Program Files
(x86)\BsiServices\ServiceHost\app.Config;   Won't Overwrite;
Won't patch;Existing file is unversioned but modified

I will look at RemoveFile. It seems kind of counter intuitive that on
installation I want to remove a file. Would I put the 
element in the same component as the component that is installing the
file?

-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Wednesday, April 13, 2011 2:05 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX force copy file.

Check a verbose log file and it should say why it is not replacing that
file. Typically because it is newer than the file you hope to replace it
with.

The RemoveFile element can be handy for some of these types of issues.
Not positive it's what you'll want, but maybe.



-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, April 13, 2011 11:37 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] WiX force copy file.

Here is the situation. I have a configuration file that on installation
in release mode I use the XmlFile task to remove a section of the file.
In debug I also use XmlFile to modify one of the elements in the file.
Is what I am finding is that if I do a release installation followed by
a debug installation the element that I am looking for is not found and
the installation fails. If I look at the configuration file the section
is missing. I was expecting the whole file to be copied to the
installation folder (overwriting the release edited file) before I try
the debug editing but apparently that is not happening. Is there some
rule within WiX that it will not overwrite a file if it exists? If so
can I override this behavior?

The applicable WiX code looks like:

  

. . . . .










Thank you.

Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com<mailto:kev...@buyseasons.com>


--
Forrester Wave Report - Recovery time is now measured in hours and
minutes not days. Key insights are discussed in the 2010 Forrester Wave
Report as part of an in-depth evaluation of disaster recovery service
providers.
Forrester found the best-in-class provider in terms of services and
vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
Forrester Wave Report - Recovery time is now measured in hours and
minutes not days. Key insights are discussed in the 2010 Forrester Wave
Report as part of an in-depth evaluation of disaster recovery service
providers.
Forrester found the best-in-class provider in terms of services and
vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
___
WiX-users mailing list
WiX-users@lists

Re: [WiX-users] WiX force copy file.

[Chad Petersen]

Yes. I run into this with text files (xml mostly) a lot. RemoveFile can
go under the same Component as the File element. That's the way I always
use it.

-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com] 
Sent: Wednesday, April 13, 2011 12:21 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX force copy file.

The log file looks like:

MSI (s) (6C:EC) [13:54:36:297]: Executing op:
FileCopy(SourceName=dfl-c3lj.con|app.Config,SourceCabKey=FILE_ServiceApp
Config,DestName=app.Config,Attributes=512,FileSize=32206,PerTick=32768,,
VerifyMedia=1,CheckCRC=0,,,InstallMode=58982400,HashOptions=0,HashPa
rt1=-680126199,HashPart2=1248668224,HashPart3=-1650872411,HashPart4=1522
490087,,)
MSI (s) (6C:EC) [13:54:36:297]: File: D:\Program Files
(x86)\BsiServices\ServiceHost\app.Config;   Won't Overwrite;
Won't patch;Existing file is unversioned but modified

I will look at RemoveFile. It seems kind of counter intuitive that on
installation I want to remove a file. Would I put the 
element in the same component as the component that is installing the
file?

-Original Message-----
From: Chad Petersen [mailto:chad.peter...@harlandfs.com] 
Sent: Wednesday, April 13, 2011 2:05 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX force copy file.

Check a verbose log file and it should say why it is not replacing that
file. Typically because it is newer than the file you hope to replace it
with.

The RemoveFile element can be handy for some of these types of issues.
Not positive it's what you'll want, but maybe.



-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, April 13, 2011 11:37 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] WiX force copy file.

Here is the situation. I have a configuration file that on installation
in release mode I use the XmlFile task to remove a section of the file.
In debug I also use XmlFile to modify one of the elements in the file.
Is what I am finding is that if I do a release installation followed by
a debug installation the element that I am looking for is not found and
the installation fails. If I look at the configuration file the section
is missing. I was expecting the whole file to be copied to the
installation folder (overwriting the release edited file) before I try
the debug editing but apparently that is not happening. Is there some
rule within WiX that it will not overwrite a file if it exists? If so
can I override this behavior?

The applicable WiX code looks like:

  

. . . . .










Thank you.

Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com<mailto:kev...@buyseasons.com>


--
Forrester Wave Report - Recovery time is now measured in hours and
minutes not days. Key insights are discussed in the 2010 Forrester Wave
Report as part of an in-depth evaluation of disaster recovery service
providers.
Forrester found the best-in-class provider in terms of services and
vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
Forrester Wave Report - Recovery time is now measured in hours and
minutes not days. Key insights are discussed in the 2010 Forrester Wave
Report as part of an in-depth evaluation of disaster recovery service
providers.
Forrester found the best-in-class provider in terms of services and
vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Forrester Wave Report - Recovery time is now measured in hours and
minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report
as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and
vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the bes

Re: [WiX-users] WiX force copy file.

[Chad Petersen]

Check a verbose log file and it should say why it is not replacing that
file. Typically because it is newer than the file you hope to replace it
with.

The RemoveFile element can be handy for some of these types of issues.
Not positive it's what you'll want, but maybe.



-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com] 
Sent: Wednesday, April 13, 2011 11:37 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] WiX force copy file.

Here is the situation. I have a configuration file that on installation
in release mode I use the XmlFile task to remove a section of the file.
In debug I also use XmlFile to modify one of the elements in the file.
Is what I am finding is that if I do a release installation followed by
a debug installation the element that I am looking for is not found and
the installation fails. If I look at the configuration file the section
is missing. I was expecting the whole file to be copied to the
installation folder (overwriting the release edited file) before I try
the debug editing but apparently that is not happening. Is there some
rule within WiX that it will not overwrite a file if it exists? If so
can I override this behavior?

The applicable WiX code looks like:

  

. . . . .










Thank you.

Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com


--
Forrester Wave Report - Recovery time is now measured in hours and
minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report
as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and
vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!  http://p.sf.net/sfu/ibm-webcastpromo
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Problem searching GAC for installed assembly

[Chad Petersen]

I thought you might say that. It's one of those "leap of faith" things.
Go to Start | Run and type in C:\Windows\Installer and hit Enter. It
should open the folder.

-Original Message-
From: CoolBreeze [mailto:coolbreeze...@googlemail.com] 
Sent: Thursday, March 31, 2011 2:08 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Problem searching GAC for installed assembly

Thanks for the suggestion. I'm on XP, so I don't know if that matters or
not, but I don't have an Installer folder anywhere under my C:\Windows
folder.

On Thu, Mar 31, 2011 at 4:59 PM, Chad Petersen
wrote:

> Oh, and an easy way to see what each MSI was used for is to open the
> C:\Windows\Installer folder in Explorer and add the Subject column to
> the details. I can immediately see what each MSI belongs to. Quite
> informative.
>
> -Original Message-
> From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
> Sent: Thursday, March 31, 2011 1:43 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Problem searching GAC for installed assembly
>
> If it was pre-installed perhaps the MSI is cached and you could
inspect
> it using Orca or similar tool. Normally in C:\Windows\Installer. Just
a
> thought. A combination of the date/time stamp of when it was installed
> and/or the Properties of the MSI in that folder and looking at the
> Summary tab will help identify which one is correct since the MSI name
> is some number in this folder. It took just a couple of minutes to
find
> my MSI amongst the 143 MSIs on my system.
>
> -Original Message-
> From: CoolBreeze [mailto:coolbreeze...@googlemail.com]
> Sent: Thursday, March 31, 2011 1:21 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Problem searching GAC for installed assembly
>
> I don't have one because it is not a part of my installer. It was
> pre-installed and I don't have the .msi for that specific version of
> csla.
>
>
> On Thu, Mar 31, 2011 at 10:14 AM, Rob Mensching
> wrote:
>
> > ComponentSearches are a little weird because you need to make sure
the
> > search Type matches the Component's KeyPath. What's the KeyPath in
the
> > target MSI?
> >
> > On Tue, Mar 29, 2011 at 1:08 PM, CoolBreeze
>  > >wrote:
> >
> > > Thanks for everyone's help. I still haven't resolved why this is
not
> > > working
> > > for me after trying numerous suggestions, but the more I work with
> Wix
> > the
> > > more I learn.
> > >
> > > Thanks again everyone.
> > >
> > > On Tue, Mar 29, 2011 at 9:28 AM, CoolBreeze <
> > coolbreeze...@googlemail.com
> > > >wrote:
> > >
> > > > Thanks for the suggestion Rob. The only problem is that this is
a
> older
> > > > version of CSLA we use 3.6.2 and on Rockford's website he no
> longer
> > > provides
> > > > an installer. This should not be  much of a road block, because
> you can
> > > get
> > > > the source and within the Setup Project find the GUID. I've done
> this
> > and
> > > > for some reason it still will not work. Below is that I have.
> > > >
> > > > 
> > > >  > > > Guid="B71EFC75-5891-437F-96F9-E2347C9F4FB4" />
> > > >
> > > >   
> > > >   Installed OR CSLA
> > > >
> > > > Am I doing this check incorrectly?
> > > >
> > > >
> > > >
> > > > On Tue, Mar 29, 2011 at 8:13 AM, Rob Mensching
>  > > >wrote:
> > > >
> > > >> How about a ComponentSearch instead of a FileSearch?
> > > >>
> > > >> On Mon, Mar 28, 2011 at 2:11 PM, CoolBreeze <
> > > coolbreeze...@googlemail.com
> > > >> >wrote:
> > > >>
> > > >> > Thanks for the reply Chad. I've tried increasing the Depth to
> say 4
> > as
> > > >> well
> > > >> > as providing and absolute path to the assembly and when I
> compile, I
> > > get
> > > >> > the
> > > >> > following error:
> > > >> >
> > > >> > Error1When the parent DirectorySearch/@Depth
attribute
> is
> > > >> greater
> > > >> > than 1 for the DirectorySearch 'GACPath', the FileSearch/@Id
> > attribute
> > > >> must
> > > >> > be absent for FileSearch 'CslaFileSearch' unless the 

Re: [WiX-users] Problem searching GAC for installed assembly

[Chad Petersen]

Oh, and an easy way to see what each MSI was used for is to open the
C:\Windows\Installer folder in Explorer and add the Subject column to
the details. I can immediately see what each MSI belongs to. Quite
informative.

-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com] 
Sent: Thursday, March 31, 2011 1:43 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Problem searching GAC for installed assembly

If it was pre-installed perhaps the MSI is cached and you could inspect
it using Orca or similar tool. Normally in C:\Windows\Installer. Just a
thought. A combination of the date/time stamp of when it was installed
and/or the Properties of the MSI in that folder and looking at the
Summary tab will help identify which one is correct since the MSI name
is some number in this folder. It took just a couple of minutes to find
my MSI amongst the 143 MSIs on my system. 

-Original Message-
From: CoolBreeze [mailto:coolbreeze...@googlemail.com] 
Sent: Thursday, March 31, 2011 1:21 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Problem searching GAC for installed assembly

I don't have one because it is not a part of my installer. It was
pre-installed and I don't have the .msi for that specific version of
csla.


On Thu, Mar 31, 2011 at 10:14 AM, Rob Mensching
wrote:

> ComponentSearches are a little weird because you need to make sure the
> search Type matches the Component's KeyPath. What's the KeyPath in the
> target MSI?
>
> On Tue, Mar 29, 2011 at 1:08 PM, CoolBreeze
 >wrote:
>
> > Thanks for everyone's help. I still haven't resolved why this is not
> > working
> > for me after trying numerous suggestions, but the more I work with
Wix
> the
> > more I learn.
> >
> > Thanks again everyone.
> >
> > On Tue, Mar 29, 2011 at 9:28 AM, CoolBreeze <
> coolbreeze...@googlemail.com
> > >wrote:
> >
> > > Thanks for the suggestion Rob. The only problem is that this is a
older
> > > version of CSLA we use 3.6.2 and on Rockford's website he no
longer
> > provides
> > > an installer. This should not be  much of a road block, because
you can
> > get
> > > the source and within the Setup Project find the GUID. I've done
this
> and
> > > for some reason it still will not work. Below is that I have.
> > >
> > > 
> > >  > > Guid="B71EFC75-5891-437F-96F9-E2347C9F4FB4" />
> > >
> > >   
> > >   Installed OR CSLA
> > >
> > > Am I doing this check incorrectly?
> > >
> > >
> > >
> > > On Tue, Mar 29, 2011 at 8:13 AM, Rob Mensching
 > >wrote:
> > >
> > >> How about a ComponentSearch instead of a FileSearch?
> > >>
> > >> On Mon, Mar 28, 2011 at 2:11 PM, CoolBreeze <
> > coolbreeze...@googlemail.com
> > >> >wrote:
> > >>
> > >> > Thanks for the reply Chad. I've tried increasing the Depth to
say 4
> as
> > >> well
> > >> > as providing and absolute path to the assembly and when I
compile, I
> > get
> > >> > the
> > >> > following error:
> > >> >
> > >> > Error1When the parent DirectorySearch/@Depth attribute
is
> > >> greater
> > >> > than 1 for the DirectorySearch 'GACPath', the FileSearch/@Id
> attribute
> > >> must
> > >> > be absent for FileSearch 'CslaFileSearch' unless the parent
> > >> > DirectorySearch/@AssignToProperty attribute value is 'yes'.
Remove
> the
> > >> > FileSearch/@Id attribute for 'CslaFileSearch' to resolve this
issue.
> > >> >
> > >> >
> > >>
> >
>
C:\Source\MS-Intelliscript\ProjectDeployments\ProjectDeployments\eCoPayW
ebSite.Setup\ConditionChecks.wxi
> > >> > 181eCoPayWebSite.Setup
> > >> >
> > >> > Now I've also tried removing the ID for my FileSearch as the
error
> > >> > suggests,
> > >> > but each time I run the installer it stops with my Condition
message
> > not
> > >> > matter what I try.
> > >> >
> > >> > I'm trying to essentially provide a base path of
> > %systemroot%\assembly\
> > >> and
> > >> > have the installer do a recursive search for the assembly I
specify
> > >> within
> > >> > my FileSearch as the assembly could reside in a number of
> sub-folders
> > >> like

Re: [WiX-users] Problem searching GAC for installed assembly

[Chad Petersen]

If it was pre-installed perhaps the MSI is cached and you could inspect
it using Orca or similar tool. Normally in C:\Windows\Installer. Just a
thought. A combination of the date/time stamp of when it was installed
and/or the Properties of the MSI in that folder and looking at the
Summary tab will help identify which one is correct since the MSI name
is some number in this folder. It took just a couple of minutes to find
my MSI amongst the 143 MSIs on my system. 

-Original Message-
From: CoolBreeze [mailto:coolbreeze...@googlemail.com] 
Sent: Thursday, March 31, 2011 1:21 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Problem searching GAC for installed assembly

I don't have one because it is not a part of my installer. It was
pre-installed and I don't have the .msi for that specific version of
csla.


On Thu, Mar 31, 2011 at 10:14 AM, Rob Mensching
wrote:

> ComponentSearches are a little weird because you need to make sure the
> search Type matches the Component's KeyPath. What's the KeyPath in the
> target MSI?
>
> On Tue, Mar 29, 2011 at 1:08 PM, CoolBreeze
 >wrote:
>
> > Thanks for everyone's help. I still haven't resolved why this is not
> > working
> > for me after trying numerous suggestions, but the more I work with
Wix
> the
> > more I learn.
> >
> > Thanks again everyone.
> >
> > On Tue, Mar 29, 2011 at 9:28 AM, CoolBreeze <
> coolbreeze...@googlemail.com
> > >wrote:
> >
> > > Thanks for the suggestion Rob. The only problem is that this is a
older
> > > version of CSLA we use 3.6.2 and on Rockford's website he no
longer
> > provides
> > > an installer. This should not be  much of a road block, because
you can
> > get
> > > the source and within the Setup Project find the GUID. I've done
this
> and
> > > for some reason it still will not work. Below is that I have.
> > >
> > > 
> > >  > > Guid="B71EFC75-5891-437F-96F9-E2347C9F4FB4" />
> > >
> > >   
> > >   Installed OR CSLA
> > >
> > > Am I doing this check incorrectly?
> > >
> > >
> > >
> > > On Tue, Mar 29, 2011 at 8:13 AM, Rob Mensching
 > >wrote:
> > >
> > >> How about a ComponentSearch instead of a FileSearch?
> > >>
> > >> On Mon, Mar 28, 2011 at 2:11 PM, CoolBreeze <
> > coolbreeze...@googlemail.com
> > >> >wrote:
> > >>
> > >> > Thanks for the reply Chad. I've tried increasing the Depth to
say 4
> as
> > >> well
> > >> > as providing and absolute path to the assembly and when I
compile, I
> > get
> > >> > the
> > >> > following error:
> > >> >
> > >> > Error1When the parent DirectorySearch/@Depth attribute
is
> > >> greater
> > >> > than 1 for the DirectorySearch 'GACPath', the FileSearch/@Id
> attribute
> > >> must
> > >> > be absent for FileSearch 'CslaFileSearch' unless the parent
> > >> > DirectorySearch/@AssignToProperty attribute value is 'yes'.
Remove
> the
> > >> > FileSearch/@Id attribute for 'CslaFileSearch' to resolve this
issue.
> > >> >
> > >> >
> > >>
> >
>
C:\Source\MS-Intelliscript\ProjectDeployments\ProjectDeployments\eCoPayW
ebSite.Setup\ConditionChecks.wxi
> > >> > 181eCoPayWebSite.Setup
> > >> >
> > >> > Now I've also tried removing the ID for my FileSearch as the
error
> > >> > suggests,
> > >> > but each time I run the installer it stops with my Condition
message
> > not
> > >> > matter what I try.
> > >> >
> > >> > I'm trying to essentially provide a base path of
> > %systemroot%\assembly\
> > >> and
> > >> > have the installer do a recursive search for the assembly I
specify
> > >> within
> > >> > my FileSearch as the assembly could reside in a number of
> sub-folders
> > >> like
> > >> > you specified. I must be missing something simple, because it
> doesn't
> > >> seem
> > >> > that it should be so difficult to get this to work.
> > >> >
> > >> > On Mon, Mar 28, 2011 at 4:38 PM, Chad Petersen
> > >> > wrote:
> > >> >
> > >> > > If you run a CMD prompt and change to c:\windows\assembly
folder
> and
> > >>

Re: [WiX-users] Registry check for Acrobat reader

[Chad Petersen]

You might check with Adobe and see what their recommended method is for
detecting their application. I've had good luck doing that with third
party apps I've needed to detect. Never actually needed to check for
Acrobat myself.

-Original Message-
From: kim [mailto:contactme...@gmail.com] 
Sent: Wednesday, March 30, 2011 12:34 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Registry check for Acrobat reader

Thanks for the suggestion Chad.

One more thing...this registry key (HKLM\SOFTWARE\Adobe\Acrobat
Reader\9.0\Installer) will work on Windows XP. But not for Windows 7 or
Server 2008 as I cant find relavent key here. Any sugguestions what can
be
done for these OS.

Regards

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Registry-c
heck-for-Acrobat-reader-tp6223495p6224663.html
Sent from the wix-users mailing list archive at Nabble.com.


--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Registry check for Acrobat reader

[Chad Petersen]

I think this is happening because your Silverlight check has a version
number in the registry Data and the URLProtocol has no value in the
registry Data for that string. I think you might need to check a setting
that would actually have a value. As soon as I put a value of "Test" in
the URLProtocol then the check started working fine.

I also had luck with this code, but you'd probably need a separate
RegistrySearch for each version using this approach.




ACROBATREADER



-Original Message-
From: kim [mailto:contactme...@gmail.com] 
Sent: Wednesday, March 30, 2011 7:51 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Registry check for Acrobat reader

I need to check if any version of acrobat reader is installed on target
machine. IF not installed display error message and stop installation.

Wix code:




ACROBATREADER = "notfound"

My problem is,above message always gets displayed whether or not acrobat
reader is installed or not. It does not check the condition
ACROBATREADER =
"notfound".

I also tried folloiwng way but still the same result




 ACROBATREADER 

Any suggestions please? Thanks

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Registry-c
heck-for-Acrobat-reader-tp6223495p6223495.html
Sent from the wix-users mailing list archive at Nabble.com.


--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Problem searching GAC for installed assembly

[Chad Petersen]

If you run a CMD prompt and change to c:\windows\assembly folder and
then do a DIR you will likely see GAC, GAC_32 and GAC_MSIL as
subfolders. Yours is apparently in GAC_MSIL. From there it has folders
following a name similar to your DLL name. Then a  specific
folder in which your DLL will likely reside. You might try including the
additional folders in your search or possibly increasing the Depth= to
something more like 3.

Path="%systemroot%\assembly\GAC_MSIL\Csla\"

-Original Message-
From: CoolBreeze [mailto:coolbreeze...@googlemail.com] 
Sent: Monday, March 28, 2011 1:15 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Problem searching GAC for installed assembly

I'm having some problems with getting a condition I've defined to work
properly. I have the following condition defined and I'm trying to have
the
installer search the GAC for the existence of the assembly. If the
assembly
isn't present I don't want to proceed with the installation, because
it's a
pre-requisite that it must already exist.



  


Installed OR CSLA

Can anyone see what the problem might be? Each time I start the
installer,
it comes up saying that CSLA must be installed, even on a machine that
does
have it installed under C:\Windows\assembly\GAC_MSIL\Csla\...

--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and publish 
your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and publish 
your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Get computer name??

[Chad Petersen]

Or you could publish the property just before entering your custom
dialog, like in the preceding dialog.

1

-Original Message-
From: Skildum, Mathew [mailto:mathew.skil...@aspect.com] 
Sent: Thursday, March 24, 2011 12:59 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Get computer name??

You have to use a custom action to do what you are trying to do.

For example:


Mat Skildum


-Original Message-
From: kim [mailto:contactme...@gmail.com] 
Sent: Thursday, March 24, 2011 2:49 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Get computer name??

Following is code from my .wxs file:



Code from my custom UI dialog



When i execute msi, editMachineName control displays [ComputerName]
instead of my machine name.

Please let me know what am I doing wrong here. Thanks

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Get-comput
er-name-tp6205253p6205447.html
Sent from the wix-users mailing list archive at Nabble.com.


--
Enable your software for Intel(R) Active Management Technology to meet
the growing manageability and security demands of your customers.
Businesses are taking advantage of Intel(R) vPro (TM) technology - will
your software be a part of the solution? Download the Intel(R)
Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Enable your software for Intel(R) Active Management Technology to meet
the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your
software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Get computer name??

[Chad Petersen]

X2

Even installs where I never use [ComputerName] the verbose log file
still lists the entry

Property(C): ComputerName = 

Showing that this is always available for use in any install.

-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com] 
Sent: Thursday, March 24, 2011 12:30 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Get computer name??

You might be inventing properties - I've no idea what LocalMachine might
be, but it's not a standard Windows Installer property. 

The answer IS [ComputerName] as has been mentioned: 

http://msdn.microsoft.com/en-us/library/aa368009(v=VS.85).aspx 

so stick with that. Look, this thing is used in thousands of setups, it
does really work, so please provide some context instead of giving up
and trying something else. 


Phil Wilson 

-Original Message-
From: kim [mailto:contactme...@gmail.com] 
Sent: Thursday, March 24, 2011 12:14 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Get computer name??

[LocalMachine] is also not working for me

  



Please advice

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Get-comput
er-name-tp6205253p6205348.html
Sent from the wix-users mailing list archive at Nabble.com.


--
Enable your software for Intel(R) Active Management Technology to meet
the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your
software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


*** Confidentiality Notice: This e-mail, including any associated or
attached files, is intended solely for the individual or entity to which
it is addressed. This e-mail is confidential and may well also be
legally privileged. If you have received it in error, you are on notice
of its status. Please notify the sender immediately by reply e-mail and
then delete this message from your system. Please do not copy it or use
it for any purposes, or disclose its contents to any other person. This
email comes from a division of the Invensys Group, owned by Invensys
plc, which is a company registered in England and Wales with its
registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW
(Registered number 166023). For a list of European legal entities within
the Invensys Group, please go to
http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_i
d=77.

You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail
recept...@invensys.com. This e-mail and any attachments thereto may be
subject to the terms of any agreements between Invensys (and/or its
subsidiaries and affiliates) and the recipient (and/or its subsidiaries
and affiliates).




--
Enable your software for Intel(R) Active Management Technology to meet
the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your
software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Get computer name??

[Chad Petersen]

Actually, I've been using [ComputerName] since MSI 2.0. If you read
those requirements a bit closer it goes on to say...

Windows Installer on Windows Server 2003, Windows XP, and Windows 2000.

Which implies just about any version.

The 4.0, 4,5 and 5.0 are required if you are on the newer OSes from the
sound of it.

Minor point, but I thought it worth a mention.



-Original Message-
From: David Watson [mailto:dwat...@sdl.com] 
Sent: Thursday, March 24, 2011 11:45 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Get computer name??

ComputerName should work on msi verions 4 and up.
http://msdn.microsoft.com/en-us/library/aa368009(VS.85).aspx



I use [LocalMachine] when creating local accounts...

-Original Message-
From: kim [mailto:contactme...@gmail.com] 
Sent: 24 March 2011 18:34
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Get computer name??

How can i populate a control with the name of the computer on which msi
is
executed.

I used [ComputerName] and [COMPUTERNAME] property but its not working.

Please advice.

thanks

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Get-comput
er-na
me-tp6205253p6205253.html
Sent from the wix-users mailing list archive at Nabble.com.


-
-
Enable your software for Intel(R) Active Management Technology to meet
the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your
software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and
requires that you delete it without acting upon or copying any of its
contents, and we further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.
Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire
SL6 7DY, UK.



--
Enable your software for Intel(R) Active Management Technology to meet
the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your
software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Error 1923 upgrading a service

[Chad Petersen]

Is this a major upgrade or a minor upgrade? Sounds like the uninstall of
the older version might not be removing the service. Verbose log file
might be helpful. You can also hit Cancel during an install to
effectively pause it (then hit Resume to continue) to look at the state
of the machine at certain discreet points along the way, like if the old
product gets removed but new files aren't being copied yet, this can be
a good point to pause the install and look in Services.msc to see the
current situation.

-Original Message-
From: Matthew Dodkins [mailto:matthew.dodk...@gmail.com] 
Sent: Thursday, March 24, 2011 9:39 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Error 1923 upgrading a service

Yes, it looks like this :-



Thanks


On Thu, Mar 24, 2011 at 3:54 PM, David Watson  wrote:

> Do you have a ServiceControl element that stops the service on
install?
>
> 
>
>
>
> -Original Message-
> From: Matthew Dodkins [mailto:matthew.dodk...@gmail.com]
> Sent: 24 March 2011 10:33
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Error 1923 upgrading a service
>
> Hi there
>
> I'm having problems upgrading an existing service using my wix
installer.
> i'm getting the 1923 error ("Verify that you have sufficient
privileges to
> install system services.").
>
> This doesn't happen the *first* time I install the service, but when I
try
> to upgrade it.
>
> I've searched around and tried a few different things, but nothing has
> solved it so far.
>
> My ServiceInstall looks like this :-
>
>  Name="My
> Service Name" DisplayName="My Display Name" Description="My
description"
> Start="auto" Account="LocalSystem" ErrorControl="ignore"
Interactive="no">
>
> I'm logged in as a local administrator. I've tried logging in direct
on the
> machine, not just from remote desktop. I've tried making sure the Name
> attribute in the ServiceInstall tag matches the service name in the
service
> code.
>
> If I uninstall the service and run my MSI, it works fine.
>
> Any help would be greatly appreciated.
>
> Thanks!
>
>

-
> -
> Enable your software for Intel(R) Active Management Technology to meet
the
> growing manageability and security demands of your customers.
Businesses
> are taking advantage of Intel(R) vPro (TM) technology - will your
software
> be a part of the solution? Download the Intel(R) Manageability Checker
> today! http://p.sf.net/sfu/intel-dev2devmar
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> SDL PLC confidential, all rights reserved.
> If you are not the intended recipient of this mail SDL requests and
> requires that you delete it without acting upon or copying any of its
> contents, and we further request that you advise us.
> SDL PLC is a public limited company registered in England and Wales.
>  Registered number: 02675207.
> Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire
SL6
> 7DY, UK.
>
>
>
>

--
> Enable your software for Intel(R) Active Management Technology to meet
the
> growing manageability and security demands of your customers.
Businesses
> are taking advantage of Intel(R) vPro (TM) technology - will your
software
> be a part of the solution? Download the Intel(R) Manageability Checker
> today! http://p.sf.net/sfu/intel-dev2devmar
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>

--
Enable your software for Intel(R) Active Management Technology to meet
the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your
software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] One install for multiple OS

[Chad Petersen]

I found OR Priviledged to work better than OR AdminUser. It actually
triggered a Windows message rather than the message in the condition.









-Original Message-
From: Robert Hermann [mailto:rob.herm...@nicewareintl.com] 
Sent: Wednesday, March 16, 2011 6:50 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] One install for multiple OS

The problem is getting the installer to consider AdminUser only when the
OS is Windows 2008 R2 
And not to consider it on any other OS.


If a user runs this install on Windows 2008 R2 and they are not "running
as Administrator", then I want an error to come up and say
You need to be an administrator.Ideally they would run this install
from inside a command prompt window that is running as administrator.

If a user runs this install on any other OS .. just proceed with the
install,  don't bother with the "running as Administrator" check.


-Original Message-
From: Jeremy Farrell [mailto:jfarr...@pillardata.com] 
Sent: Tuesday, March 15, 2011 5:12 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] One install for multiple OS

And the problem is? 

> From: Robert Hermann [mailto:rob.herm...@nicewareintl.com] 
> 
> I've got an install for a backend service that needs to 
> consider a couple of OS and then scenarios within that os.
> 
> For the time being I need  my project to first detect the os 
> and if its not at least Windows 2003, to throw an error.
> 
> If its Windows 2008 R2, then the install needs to detect if 
> its being run from a Administrator command prompt or not.  If 
> its not, say something.
> 
> I can the logic to work if its either or but not together ...
> 
> Right now I've got
> 
> 
> 
> 
> 
> 
> 
> Rob

--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] One install for multiple OS

[Chad Petersen]

I think it is because your Conditions are not mutually exclusive. 

-Original Message-
From: Robert Hermann [mailto:rob.herm...@nicewareintl.com] 
Sent: Tuesday, March 15, 2011 2:25 PM
To: 'wix-users@lists.sourceforge.net'
Subject: [WiX-users] One install for multiple OS

I've got an install for a backend service that needs to consider a
couple of OS and then scenarios within that os.

For the time being I need  my project to first detect the os and if its
not at least Windows 2003, to throw an error.

If its Windows 2008 R2, then the install needs to detect if its being
run from a Administrator command prompt or not.  If its not, say
something.

I can the logic to work if its either or but not together ...

Right now I've got







Rob



--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Error 1723

[Chad Petersen]

Of course, there's more than one way to skin a cat. Check out Phil's suggestion 
here

http://social.msdn.microsoft.com/forums/en-us/winformssetup/thread/9E48A3D0-ADF2-4CF3-B9BA-D5E9DE584C8F



-Original Message-
From: Colin LeMahieu [mailto:clemah...@gmail.com] 
Sent: Tuesday, March 01, 2011 8:27 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Error 1723

Yea, and the million dollar question is, which dll is missing?

The exact error message I get is:

MSI (c) (C0:1C) [10:18:19:335]: Note: 1: 1723 2:
caStripCharsFromNetworkPort 3: StripExtraCharsFromRegSearchValue 4:
C:\DOCUME~1\ADMINI~1.LAB\LOCALS~1\Temp\MSI151.tmp
Error 1723. There is a problem with this Windows Installer package. A
DLL required for this install to complete could not be run. Contact
your support personnel or package vendor. Action
caStripCharsFromNetworkPort, entry: StripExtraCharsFromRegSearchValue,
library: C:\DOCUME~1\ADMINI~1.LAB\LOCALS~1\Temp\MSI151.tmp
MSI (c) (C0:1C) [10:18:20:664]: Product: Email Management Services --
Error 1723. There is a problem with this Windows Installer package. A
DLL required for this install to complete could not be run. Contact
your support personnel or package vendor. Action
caStripCharsFromNetworkPort, entry: StripExtraCharsFromRegSearchValue,
library: C:\DOCUME~1\ADMINI~1.LAB\LOCALS~1\Temp\MSI151.tmp

This custom action is a managed assembly.  I unpacked the MSI and CAB
and pointed .NET reflector at the assembly and all its references were
found.  I set the fusion log to log while running the MSI and it
doesn't report any errors.  I ran msiexec within a WinDBG session and
didn't get any module load failures.

Does anyone have tips on how do debug this type or issue?  Or
basically any debugging related to WiX/MSI?  How can the wixpdb files
be used?

Thanks for the reply, I know you didn't write WiX though I've had an
easier time debugging hex machine code than the WiX/MSI process.

> Message: 6
> Date: Thu, 24 Feb 2011 11:05:01 +0200
> From: "Dan Vasilov" 
> Subject: Re: [WiX-users] Error 1723
> To: "'General discussion for Windows Installer XML toolset.'"
>        
> Message-ID: <02fc01cbd401$eb598740$c20c95c0$@ro>
> Content-Type: text/plain;       charset="us-ascii"
>
>        It is very likely the .dll is not included in the MSI package at
> build.
> Another possibility is the .dll is missing some dependent .dll files.
>
> -Original Message-
> From: Colin LeMahieu [mailto:clemah...@gmail.com]
> Sent: Wednesday, February 23, 2011 7:26 PM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Error 1723
>
> I'm getting this error on startup for an MSI that previously worked.
> Are there any tips for debugging this error?  Is it unreasonable to
> expect the name of the offending DLL or some way to attach a debugger
> to an MSI while installing?
>
> 
> --

--
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Error 1723

[Chad Petersen]

I believe I might know what you are running into. You can't access things 
destined for the GAC *during* the install. You probably will need to expose a 
regular COM interface to your assembly and put it someplace accessible other 
(also) than the GAC. We've had to do this with some of our .NET assemblies that 
we needed to also call during the install.

Well, it's a thought, anyway...

-Original Message-
From: Colin LeMahieu [mailto:clemah...@gmail.com] 
Sent: Tuesday, March 01, 2011 8:27 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Error 1723

Yea, and the million dollar question is, which dll is missing?

The exact error message I get is:

MSI (c) (C0:1C) [10:18:19:335]: Note: 1: 1723 2:
caStripCharsFromNetworkPort 3: StripExtraCharsFromRegSearchValue 4:
C:\DOCUME~1\ADMINI~1.LAB\LOCALS~1\Temp\MSI151.tmp
Error 1723. There is a problem with this Windows Installer package. A
DLL required for this install to complete could not be run. Contact
your support personnel or package vendor. Action
caStripCharsFromNetworkPort, entry: StripExtraCharsFromRegSearchValue,
library: C:\DOCUME~1\ADMINI~1.LAB\LOCALS~1\Temp\MSI151.tmp
MSI (c) (C0:1C) [10:18:20:664]: Product: Email Management Services --
Error 1723. There is a problem with this Windows Installer package. A
DLL required for this install to complete could not be run. Contact
your support personnel or package vendor. Action
caStripCharsFromNetworkPort, entry: StripExtraCharsFromRegSearchValue,
library: C:\DOCUME~1\ADMINI~1.LAB\LOCALS~1\Temp\MSI151.tmp

This custom action is a managed assembly.  I unpacked the MSI and CAB
and pointed .NET reflector at the assembly and all its references were
found.  I set the fusion log to log while running the MSI and it
doesn't report any errors.  I ran msiexec within a WinDBG session and
didn't get any module load failures.

Does anyone have tips on how do debug this type or issue?  Or
basically any debugging related to WiX/MSI?  How can the wixpdb files
be used?

Thanks for the reply, I know you didn't write WiX though I've had an
easier time debugging hex machine code than the WiX/MSI process.

> Message: 6
> Date: Thu, 24 Feb 2011 11:05:01 +0200
> From: "Dan Vasilov" 
> Subject: Re: [WiX-users] Error 1723
> To: "'General discussion for Windows Installer XML toolset.'"
>        
> Message-ID: <02fc01cbd401$eb598740$c20c95c0$@ro>
> Content-Type: text/plain;       charset="us-ascii"
>
>        It is very likely the .dll is not included in the MSI package at
> build.
> Another possibility is the .dll is missing some dependent .dll files.
>
> -Original Message-
> From: Colin LeMahieu [mailto:clemah...@gmail.com]
> Sent: Wednesday, February 23, 2011 7:26 PM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Error 1723
>
> I'm getting this error on startup for an MSI that previously worked.
> Are there any tips for debugging this error?  Is it unreasonable to
> expect the name of the offending DLL or some way to attach a debugger
> to an MSI while installing?
>
> 
> --

--
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Command line installation?

[Chad Petersen]

In another area of your code look for the  element and make
sure you change the Id="" guid there as one necessary step. But, leave
the UpgradeCode unchanged in that same element. Also make sure you
increment your version number to something higher than that one you have
already installed.

Then in your UpgradeVersion element that you show below don't forget to
add

OnlyDetect="no"

This is what causes it to not just check for your other version, but
also remove it.

Hope that helps
Chad


-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com] 
Sent: Thursday, February 24, 2011 3:21 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Command line installation?

I have WiX code like:



  
   
. . . . .

  


I am trying to automatically uninstall any previous versions of the
package before this installation proceeds. But even with this code when
I run the .msi I get a prompt indicating that I must go to the Control
Panel and uninstall a previous version. What am I doing wrong?

Kevin


--
Free Software Download: Index, Search & Analyze Logs and other IT data
in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT
data 
generated by your applications, servers and devices whether physical,
virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Command line installation?

[Chad Petersen]

Sure. In the previous dialog you can usually put Conditions on the Next
pushbutton to display any other dialog based upon the Condition set by
the Property 





Something like that is one approach, at least.

-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com] 
Sent: Wednesday, February 23, 2011 11:02 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Command line installation?

Since I have set default properties I just need to test BEFORE I set the
default to make sure some key "required" properties are set and if any
of these are set then I could safely avoid the dialog UI and take the
defaults for the rest. How do I test for the existence of a property and
disable the dialog if true?

Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com


-Original Message-----
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Wednesday, February 23, 2011 11:01 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Command line installation?

I can offer some help. For the command line you append your PROPERTYNAME
followed by an equal sign and then the value you want to assign to that
property. Like this.

msiexec /L*v c:\log.txt /i my.msi PROPERTYNAME1=value1
PROPERTYNAME2=value2

In my experience it seemed like if you gave it all "required" properties
that correspond to your UI then it breezes through without a hitch. But,
if you forget a property it either starts popping up dialog boxes for
you to fill in or some other behavior, I can't remember which. I'm not
sure if you only give it one or two properties that it's going to know
what to do for the remainder.

A command line that works for my installer is 623 characters long, but
it can install in a test environment where all properties are known
quantities without any dialogs showing. Really helps with automation.

-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com]
Sent: Wednesday, February 23, 2011 7:08 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Command line installation?

I would like to know what strategies are best to use if I optionally
don't want a UI. Right now I have a custom dialog that appears and it
sets a number of properties. If any of these properties are set on the
command line I would like to skip the dialog. That is one question. The
second question is how do I set the properties on the command line?

If it helps the dialog is defined as


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


  devbrain03
  user
  testing
  computer
  computer
  computer
  computer
  computer
  site
  mail.company.com
  server
  user
  testing
  https://myco.ic3.com/

  






























  


  

  
  
  

  


Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Wednesday, February 16, 2011 9:40 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Conditionally invoking ServiceInstall Element

I don't think more disk space should be consumed if things are cabbed
and the service executable is identical in the two Components (one
Conditioned, the other not) because only one will ever get installed on
the machine (due to mutually exclusive Conditions) and smart-cabbing
should make sure only one file is in the cabinet.

(wow, that's one sentence ).
On Mon, Feb 14, 2011 at 8:50 AM, Christopher Painter <
chr...@deploymentengineering.com> wrote:

> Technically it's a violation of the component rules.   However, if you
can
> make
> sure that the two components ( whether they be in two merge modules or

> no merge modules ) have mutually exclusive component conditions so
> that only one will
> ever be installed you can pretty much get away with it.   You will
still
> get
> validation errors as part of the build though I believe.  I've done
> this in the past  and my main complaint about it is it doesn't scale
> well.
>
>
> If dev doesn't want to redo the app,  what would be the effect of
> taking consoleappservice.exe and copying / renaming it to have two
files:
>
> consoleapp.exe
> service.exe
>
> It's a confusing hack and you'll eat up more disk space then if you
> factored it
> out into the shared.dll   but you should be able to still do
everything I
>

Re: [WiX-users] Command line installation?

[Chad Petersen]

I can offer some help. For the command line you append your PROPERTYNAME
followed by an equal sign and then the value you want to assign to that
property. Like this.

msiexec /L*v c:\log.txt /i my.msi PROPERTYNAME1=value1
PROPERTYNAME2=value2

In my experience it seemed like if you gave it all "required" properties
that correspond to your UI then it breezes through without a hitch. But,
if you forget a property it either starts popping up dialog boxes for
you to fill in or some other behavior, I can't remember which. I'm not
sure if you only give it one or two properties that it's going to know
what to do for the remainder.

A command line that works for my installer is 623 characters long, but
it can install in a test environment where all properties are known
quantities without any dialogs showing. Really helps with automation.

-Original Message-
From: Kevin Burton [mailto:kev...@buyseasons.com] 
Sent: Wednesday, February 23, 2011 7:08 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Command line installation?

I would like to know what strategies are best to use if I optionally
don't want a UI. Right now I have a custom dialog that appears and it
sets a number of properties. If any of these properties are set on the
command line I would like to skip the dialog. That is one question. The
second question is how do I set the properties on the command line?

If it helps the dialog is defined as


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


  devbrain03
  user
  testing
  computer
  computer
  computer
  computer
  computer
  site
  mail.company.com
  server
  user
  testing
  https://myco.ic3.com/

  






























  


  

  
  
  

  


Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com 

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: Wednesday, February 16, 2011 9:40 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Conditionally invoking ServiceInstall Element

I don't think more disk space should be consumed if things are cabbed
and the service executable is identical in the two Components (one
Conditioned, the other not) because only one will ever get installed on
the machine (due to mutually exclusive Conditions) and smart-cabbing
should make sure only one file is in the cabinet.

(wow, that's one sentence ).
On Mon, Feb 14, 2011 at 8:50 AM, Christopher Painter <
chr...@deploymentengineering.com> wrote:

> Technically it's a violation of the component rules.   However, if you
can
> make
> sure that the two components ( whether they be in two merge modules or

> no merge modules ) have mutually exclusive component conditions so 
> that only one will
> ever be installed you can pretty much get away with it.   You will
still
> get
> validation errors as part of the build though I believe.  I've done 
> this in the past  and my main complaint about it is it doesn't scale 
> well.
>
>
> If dev doesn't want to redo the app,  what would be the effect of 
> taking consoleappservice.exe and copying / renaming it to have two
files:
>
> consoleapp.exe
> service.exe
>
> It's a confusing hack and you'll eat up more disk space then if you 
> factored it
> out into the shared.dll   but you should be able to still do
everything I
> mentioned previously.   If this is .NET code it might not be happy but
you
> could
> give it a try.
>
> Personally if it is a .NET service, I can't imagine it taking more 
> then a few hours to factor out, build and test.
>
> ---
> Christopher Painter, Author of Deployment Engineering Blog Have a hot 
> tip, know a secret or read a really good thread that deserves 
> attention? E-Mail Me
>
>
>
> - Original Message 
> From: Gregg Swanson 
> To: General discussion for Windows Installer XML toolset.
> 
> Sent: Mon, February 14, 2011 10:38:26 AM
> Subject: Re: [WiX-users] Conditionally invoking ServiceInstall Element
>
> Thanks for the help...
>
> I am a WIX rooky.
>
> Is this is a valid option -
>
> Package the consleappservice.exe in two separate merge modules, the 
> first doesn't invoke ServiceInstall the second does invoke
ServiceInstall?
>
> The application that I am helping will have to refactor code and they 
> may be reluctant to do so at this point in time.
>
> Thanks,
> Gregg
>
>
> -Original Message-
> From: Christopher Painter [mailto:chr...@deploymentengineering.com]
> Sent: Monday, February 14, 2011 10:14 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Conditionally invokin

Re: [WiX-users] WixCreateInternetShortcuts: Error 0x8000ffff:failed toset shortcut

[Chad Petersen]

3171783

-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com] 
Sent: Tuesday, February 01, 2011 5:59 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] WixCreateInternetShortcuts: Error
0x8000:failed toset shortcut

On 31-Jan-11 14:23, Chad Petersen wrote:
> Thanks for your help. Turns out the customer did not have IE or any
> other browser installed on this particular computer. Hadn't run into
> that before.

Heh, funny. Can you enter a feature request to add a ContinueOnError 
attribute, like exists for some other custom elements?

-- 
sig://boB
http://joyofsetup.com/



--
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better
price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] WixCreateInternetShortcuts: Error 0x8000ffff:failed toset shortcut

[Chad Petersen]

Thanks for your help. Turns out the customer did not have IE or any
other browser installed on this particular computer. Hadn't run into
that before.

-Original Message-
From: Thom Leigh [mailto:t...@mondago.com] 
Sent: Monday, January 31, 2011 10:17 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WixCreateInternetShortcuts: Error
0x8000:failed toset shortcut

The MSDN page for IUniformResourceLocator::SetURL details these return
values...

S_OK: The object's URL was set successfully.
E_OUTOFMEMORY: There is not enough memory to complete the operation.
IS_E_EXEC_FAILED: The URL's protocol handler failed to run.
URL_E_INVALID_SYNTAX: The URL's syntax is invalid.
URL_E_UNREGISTERED_PROTOCOL: The URL's protocol does not have a
registered protocol handler.

So I would start with:
Does the customer have a handler for http (for the user that the
installer is running as)?
Does it work? (does Start>Run>http://e3server start a browser?)
Do they have enough memory/disk space to create the shortcut?


-----Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com] 
Sent: 31 January 2011 17:36
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] WixCreateInternetShortcuts: Error 0x8000:
failed toset shortcut

WiX version 3.0.5419.0

OK, my installer is working in a huge number of cases without hitting
this error. We released back in November. Today I get a log file from a
customer that doesn't get any on-screen error. The installer just
suddenly rolls back on its own. The verbose log file shows these
entries.

WixCreateInternetShortcuts:  Creating IUniformResourceLocatorW shortcut
'C:\Documents and Settings\All Users\Desktop\Interlinq E3.url' target
'http://E3SERVER:80/E3Container'
WixCreateInternetShortcuts:  Error 0x8000: failed to set shortcut
'C:\Documents and Settings\All Users\Desktop\Interlinq E3.url' target
'http://E3SERVER:80/E3Container'
WixCreateInternetShortcuts:  Error 0x8000: failed to create Internet
shortcut

My code looks like this






The support team made sure they could create shortcuts in C:\Documents
and Settings\All Users\Desktop. I'm not sure how to troubleshoot this
one. Thanks for any ideas?

Chad




--
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better
price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires February
28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better
price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] WixCreateInternetShortcuts: Error 0x8000ffff: failed to set shortcut

[Chad Petersen]

WiX version 3.0.5419.0

OK, my installer is working in a huge number of cases without hitting
this error. We released back in November. Today I get a log file from a
customer that doesn't get any on-screen error. The installer just
suddenly rolls back on its own. The verbose log file shows these
entries.

WixCreateInternetShortcuts:  Creating IUniformResourceLocatorW shortcut
'C:\Documents and Settings\All Users\Desktop\Interlinq E3.url' target
'http://E3SERVER:80/E3Container'
WixCreateInternetShortcuts:  Error 0x8000: failed to set shortcut
'C:\Documents and Settings\All Users\Desktop\Interlinq E3.url' target
'http://E3SERVER:80/E3Container'
WixCreateInternetShortcuts:  Error 0x8000: failed to create Internet
shortcut

My code looks like this






The support team made sure they could create shortcuts in C:\Documents
and Settings\All Users\Desktop. I'm not sure how to troubleshoot this
one. Thanks for any ideas?

Chad



--
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How do you fix this error? (id is too long, 72 characters max)

[Chad Petersen]

Did you know that your original post on December 6th didn't make it to
the mailing list? It's only in the reply to your own e-mail on the 9th
that made it so others could see your initial inquiry from the 6th. Just
thought you might find that interesting because you'd mentioned silence
on the issue initially, but there were no prior posts from you on the
6th that appeared here.


In the initial email from the 6th, which shows in your reply to that,
you say at the very end.

"It appears that this is the location of the error, it is in a generated
file.








"

What generates the file that contains this code? That's not compiler or
linker code. That's just straight up WiX code as "normally" written by a
human. It would seem so straight forward to fix as to be trivial, but
apparently not.


-Original Message-
From: John Bergman [mailto:john.berg...@xpedienttechnologies.com] 
Sent: Friday, December 10, 2010 8:49 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How do you fix this error? (id is too long, 72
characters max)

To me, it looks like it is because the filename is long.

 
$(var.Core.Data.DataManagement.Plugins.Client.TargetDir)XPT.Core.Data.Da
taManagement.Plugins.Client.pdb

The physical directory is this:
C:\XPertSeries\Source\XPJ-R7S3\bin\debug\plugins\platformclient

Core.Data.DataManagement.Plugins.Client is the project name (and the
assembly name + XPT).

So you see my dilemma, short of renaming everything I am left with the
warnings.  To me, since the ID is generated, it seems like a bug...

-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com] 
Sent: Friday, December 10, 2010 10:11 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How do you fix this error? (id is too long, 72
characters max)

I think you'd mentioned before that it was during the compile, as
opposed to the link, which I suspect, too. You can certainly break those
down into two discreet steps to figure out which one it is. Assuming it
is the compile then it would be in one of the .wixobj files, since that
is what the compiler creates. You could do just the compile and then use
a utility like FINDSTR to search through those .wixobj files and figure
out which one it is. Then correlate that back to which source file it
is. I suspect one of your $(var.aaa.bbb.ccc.ddd.eee) entries is being
expanded out during the compile time to be the entry that is too long.
If that were to hold true then it would be necessary for you to examine
those var entries to see which one it is and how to shorten it to
eliminate the error.




-Original Message-
From: John Bergman [mailto:john.berg...@xpedienttechnologies.com]
Sent: Friday, December 10, 2010 7:38 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How do you fix this error? (id is too long, 72
characters max)

The file must be generated by WiX during build time.

-Original Message-
From: Jeremy Farrell [mailto:jfarr...@pillardata.com]
Sent: Thursday, December 09, 2010 7:42 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How do you fix this error? (id is too long, 72
characters max)

Maybe it's just my lack of understanding, but you don't seem to be
giving us many clues here. You say the problem Id is in "a generated
file" - what file, generated by what? 

> -Original Message-
> From: John Bergman [mailto:john.berg...@xpedienttechnologies.com]
> Sent: Thursday, December 09, 2010 10:58 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] How do you fix this error? (id is too long,
> 72 characters max)
> 
> This is the full contents of the WiX file, I don't see how I can 
> shorten it based on what you replied.
> 
>   xmlns="http://schemas.microsoft.com/wix/2006/wi";
>   xmlns:iis="http://schemas.microsoft.com/wix/IIsExtension";
>   xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";>
> 
>   
>   
>Version="$(var.MajorVersion).$(var.MinorVersion).$(var.BuildNumber)">
> Manufacturer="XPT" />
> 
>   
>   
> 
> 
>Name='$(var.Core.Data.DataManagement.Plugins.Client.TargetFile
> Name)' 
> Source='$(var.Core.Data.DataManagement.Plugins.Client.TargetPath)' />
>Name='XPedient.Core.Data.DataManagement.Plugins.Client.pdb' 
> Source='$(var.Core.Data.DataManagement.Plugins.Client.TargetDi
> r)XPedient.Core.Data.DataManagement.Plugins.Client.pdb' />
> 
> 
> 
&g

Re: [WiX-users] How do you fix this error? (id is too long, 72 characters max)

[Chad Petersen]

I think you'd mentioned before that it was during the compile, as
opposed to the link, which I suspect, too. You can certainly break those
down into two discreet steps to figure out which one it is. Assuming it
is the compile then it would be in one of the .wixobj files, since that
is what the compiler creates. You could do just the compile and then use
a utility like FINDSTR to search through those .wixobj files and figure
out which one it is. Then correlate that back to which source file it
is. I suspect one of your $(var.aaa.bbb.ccc.ddd.eee) entries is being
expanded out during the compile time to be the entry that is too long.
If that were to hold true then it would be necessary for you to examine
those var entries to see which one it is and how to shorten it to
eliminate the error.




-Original Message-
From: John Bergman [mailto:john.berg...@xpedienttechnologies.com] 
Sent: Friday, December 10, 2010 7:38 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How do you fix this error? (id is too long, 72
characters max)

The file must be generated by WiX during build time.

-Original Message-
From: Jeremy Farrell [mailto:jfarr...@pillardata.com] 
Sent: Thursday, December 09, 2010 7:42 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How do you fix this error? (id is too long, 72
characters max)

Maybe it's just my lack of understanding, but you don't seem to be
giving us many clues here. You say the problem Id is in "a generated
file" - what file, generated by what? 

> -Original Message-
> From: John Bergman [mailto:john.berg...@xpedienttechnologies.com]
> Sent: Thursday, December 09, 2010 10:58 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] How do you fix this error? (id is too long, 
> 72 characters max)
> 
> This is the full contents of the WiX file, I don't see how I can 
> shorten it based on what you replied.
> 
>   xmlns="http://schemas.microsoft.com/wix/2006/wi";
>   xmlns:iis="http://schemas.microsoft.com/wix/IIsExtension";
>   xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";>
> 
>   
>   
>Version="$(var.MajorVersion).$(var.MinorVersion).$(var.BuildNumber)">
> Manufacturer="XPT" />
> 
>   
>   
> 
> 
>Name='$(var.Core.Data.DataManagement.Plugins.Client.TargetFile
> Name)' 
> Source='$(var.Core.Data.DataManagement.Plugins.Client.TargetPath)' />
>Name='XPedient.Core.Data.DataManagement.Plugins.Client.pdb' 
> Source='$(var.Core.Data.DataManagement.Plugins.Client.TargetDi
> r)XPedient.Core.Data.DataManagement.Plugins.Client.pdb' />
> 
> 
> 
>Name='$(var.Core.MetaData.Plugins.Model.Client.TargetFileName)
> ' Source='$(var.Core.MetaData.Plugins.Model.Client.TargetPath)' />
>Name='XPedient.Core.MetaData.Plugins.Model.Client.pdb' 
> Source='$(var.Core.MetaData.Plugins.Model.Client.TargetDir)XPe
dient.Core.MetaData.Plugins.Model.Client.pdb' />
> 
> 
> 
>Name='$(var.Core.Repository.Plugins.Client.TargetFileName)' 
> Source='$(var.Core.Repository.Plugins.Client.TargetPath)' />
>Name='XPedient.Core.Repository.Plugins.Client.pdb' 
> Source='$(var.Core.Repository.Plugins.Client.TargetDir)XPedien
t.Core.Repository.Plugins.Client.pdb' />
> 
> 
> 
>Name='$(var.Core.System.Plugins.Client.TargetFileName)' 
> Source='$(var.Core.System.Plugins.Client.TargetPath)' />
>Name='XPedient.Core.System.Plugins.Client.pdb' 
> Source='$(var.Core.System.Plugins.Client.TargetDir)XPedient.Co
> re.System.Plugins.Client.pdb' />
> 
> 
> 
>Name='$(var.Core.System.Plugins.Presenter.TargetFileName)' 
> Source='$(var.Core.System.Plugins.Presenter.TargetPath)' />
>Name='XPedient.Core.System.Plugins.Presenter.pdb' 
> Source='$(var.Core.System.Plugins.Presenter.TargetDir)XPedient
.Core.System.Plugins.Presenter.pdb' />
> 
> 
>   
>   
>   
> 
> 
> 
> -Original Message-
> From: Paden, Patrick [mailto:patrick.pa...@wolterskluwer.com]
> Sent: Thursday, December 09, 2010 9:57 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] How do you fix this error? (id is too long, 
> 72 characters max)
> 
> -=-=-=-
> 
> error:
> 
> The DirectoryRef/@Id of attributes value, 
> 'Application.managementserver.plugins.authentication.native.cl
> ient.symbo
> ls' is too long for an identifier, standard identifiers are
> 72 characters or less.
> 
>  Id="Application.ManagementServer.Plugins.Authentication.Native
> .Client.Sy
> mbols">
> 
> -=-=-=-
> The  in the above text-cut is 73 characters long, this 
> is what needs to be changed down to 72 characters or less.
> Your  elsewhere in the code most likely needs to be changed

> too.
> 
> Hope this helps,
> Patrick Paden
> 

Re: [WiX-users] Run DB Scripts

[Chad Petersen]

Use the  element is the WiX way to do it. Working very well for 
me.

-Original Message-
From: Anu Dev [mailto:queryl...@yahoo.com] 
Sent: Wednesday, December 08, 2010 9:01 AM
To: WIX
Subject: [WiX-users] Run DB Scripts

Hi

How can I run DBScripts during the installation process. I have seen an article 
which looks for SQLCMD.exe and calls the respective .SQL files . Is this the 
right way? Can anyone please point me to some pointers on the best practice to 
run DB Scripts.

Regards
Anweshi


  
--
This SF Dev2Dev email is sponsored by:

WikiLeaks The End of the Free Internet
http://p.sf.net/sfu/therealnews-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
This SF Dev2Dev email is sponsored by:

WikiLeaks The End of the Free Internet
http://p.sf.net/sfu/therealnews-com
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Shortcut Icons showing as generic

[Chad Petersen]

I tried setting Advertise="no" and I get these two ICE errors, which is
probably what prompted the change during the conversion.

error LGHT0204 : ICE43: Component Autotaskconfigexe has non-advertised
shortcuts. It should use a registry key under HKCU as its KeyPath, not a
file.
error LGHT0204 : ICE57: Component 'Autotaskconfigexe' has both per-user
and per-machine data with a per-machine KeyPath.


If I leave it as Advertise="yes" then no ICE errors, but the original
problem occurs where the icon shows generic until someone clicks it.

-----Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com] 
Sent: Monday, October 25, 2010 12:29 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Shortcut Icons showing as generic

When installing my package the icon for normal file shortcuts are
initially showing up as generic icons. Once a person double-clicks on a
particular one then the icon changes to the correct one. We did not have
this issue when compiling using WiX 2.0. In that version the Shortcut
table in Orca showed the Target column as [#fileid]. Now, when compiled
using WiX 3.0 the Target column shows the Feature under which the icon
is created. 

The conversion itself added Advertise="yes" to each of my Shortcut
elements. Is this correct? Or it is likely what is causing the new
behavior?

Thanks
Chad



--
Nokia and AT&T present the 2010 Calling All Innovators-North America
contest
Create new apps & games for the Nokia N8 for consumers in  U.S. and
Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in
marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store

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



--
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store 
http://p.sf.net/sfu/nokia-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Shortcut Icons showing as generic

[Chad Petersen]

When installing my package the icon for normal file shortcuts are
initially showing up as generic icons. Once a person double-clicks on a
particular one then the icon changes to the correct one. We did not have
this issue when compiling using WiX 2.0. In that version the Shortcut
table in Orca showed the Target column as [#fileid]. Now, when compiled
using WiX 3.0 the Target column shows the Feature under which the icon
is created. 

The conversion itself added Advertise="yes" to each of my Shortcut
elements. Is this correct? Or it is likely what is causing the new
behavior?

Thanks
Chad


--
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store 
http://p.sf.net/sfu/nokia-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] File share missing after major upgrade

[Chad Petersen]

By name:

MSI (s) (F4:30) [13:43:39:156]: Component: ConnectSharedFilesShare;
Installed: Absent;   Request: Local;   Action: Local

MSI (s) (F4:DC) [13:44:05:328]: Component: ConnectSharedFilesShare;
Installed: Local;   Request: Absent;   Action: Absent

By Guid:

MSI (s) (F4:DC) [13:44:14:703]: Executing op:
ComponentUnregister(ComponentId={1E1F2637-AEDB-4727-9297-893F3CBE2A0A},,
BinaryType=0,)
1: {AA31BF3A-DFDE-4086-A1CE-33A63C2FF229} 2:
{1E1F2637-AEDB-4727-9297-893F3CBE2A0A}

MSI (s) (F4:30) [13:44:46:140]: Executing op:
ComponentRegister(ComponentId={1E1F2637-AEDB-4727-9297-893F3CBE2A0A},Key
Path=C:\Program Files\Harland Financial
Solutions\Connect\ConnectSharedFiles\,State=3,,Disk=1,SharedDllRefCount=
0,BinaryType=0)
1: {EBB0EFC7-146D-491D-9AE3-B41BF82F42C6} 2:
{1E1F2637-AEDB-4727-9297-893F3CBE2A0A} 3: C:\Program Files\Harland
Financial Solutions\Connect\ConnectSharedFiles\



And that is it. I've found if I change RemoveExistingProducts to
After="InstallFinalize" then my file shares are there at the end of the
install.

Thanks
Chad

-Original Message-
From: Blair [mailto:os...@live.com] 
Sent: Wednesday, October 13, 2010 9:24 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] File share missing after major upgrade

Search the log(s) for both the name and the guid of the component. I'm
primarily interested in seeing the state and action values for that
component and for all features that component is found in, as well as
the
sequence involved.

-----Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com] 
Sent: Wednesday, October 13, 2010 7:59 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] File share missing after major upgrade

No, the previous major release one back, which is the only version we
allow upgrading over, has the exact same guid. We keep them mostly
static once we get the initial authoring done. We've had several major
releases of this product and hadn't run into this before. It reproduces
on several different machines. We primarily would be doing upgrades on
Windows Server 2003. I've saved verbose log files of a clean install and
an upgrade. Is there anything to hone in on the logs? They are a bit
tricky to beyond compare well as the upgrade logs all the
RemoveExistingProducts stuff.


-Original Message-
From: Blair [mailto:os...@live.com] 
Sent: Tuesday, October 12, 2010 3:38 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] File share missing after major upgrade

Did the guid of the ConnectSharedFilesShare component change between the
two
versions?

-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com] 
Sent: Tuesday, October 12, 2010 3:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] File share missing after major upgrade

If I do a clean install of our product I see the two file shares showing
at the end of the install. However, when I do the major upgrade the file
shares are there before I start the major upgrade and are missing by the
time it is done. I've taken verbose log files of each and tried to
compare them, but don't see the problem yet. I've been looking in the
area of CreateSmb and it is similar in both cases. 

This is still a WiX 2.0 project needing an update to WiX 3.0 but
probably not going to happen before we have to ship.


  

  


Any ideas why a share would not be recreated on a major upgrade?

Thanks
Chad




--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users





--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
exper

Re: [WiX-users] File share missing after major upgrade

[Chad Petersen]

No, the previous major release one back, which is the only version we
allow upgrading over, has the exact same guid. We keep them mostly
static once we get the initial authoring done. We've had several major
releases of this product and hadn't run into this before. It reproduces
on several different machines. We primarily would be doing upgrades on
Windows Server 2003. I've saved verbose log files of a clean install and
an upgrade. Is there anything to hone in on the logs? They are a bit
tricky to beyond compare well as the upgrade logs all the
RemoveExistingProducts stuff.


-Original Message-
From: Blair [mailto:os...@live.com] 
Sent: Tuesday, October 12, 2010 3:38 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] File share missing after major upgrade

Did the guid of the ConnectSharedFilesShare component change between the
two
versions?

-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com] 
Sent: Tuesday, October 12, 2010 3:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] File share missing after major upgrade

If I do a clean install of our product I see the two file shares showing
at the end of the install. However, when I do the major upgrade the file
shares are there before I start the major upgrade and are missing by the
time it is done. I've taken verbose log files of each and tried to
compare them, but don't see the problem yet. I've been looking in the
area of CreateSmb and it is similar in both cases. 

This is still a WiX 2.0 project needing an update to WiX 3.0 but
probably not going to happen before we have to ship.


  

  


Any ideas why a share would not be recreated on a major upgrade?

Thanks
Chad




--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] File share missing after major upgrade

[Chad Petersen]

If I do a clean install of our product I see the two file shares showing
at the end of the install. However, when I do the major upgrade the file
shares are there before I start the major upgrade and are missing by the
time it is done. I've taken verbose log files of each and tried to
compare them, but don't see the problem yet. I've been looking in the
area of CreateSmb and it is similar in both cases. 

This is still a WiX 2.0 project needing an update to WiX 3.0 but
probably not going to happen before we have to ship.


  

  


Any ideas why a share would not be recreated on a major upgrade?

Thanks
Chad


--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Issues when evaluating a condition

[Chad Petersen]

MSIEXEC /L*v [logfilename] /i [msifilename]

Replace the square bracket variables with your log file name of choice
and your MSI filename.

-Original Message-
From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] 
Sent: Monday, October 04, 2010 1:52 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Issues when evaluating a condition

Ok, how do I gereragte a verose log?
Cheers
Seanm.

-Original Message-
From: Blair [mailto:os...@live.com] 
Sent: 04 October 2010 21:15
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Issues when evaluating a condition

You change both because the actions will run run in the execute sequence
only if the UI sequence didn't run.

Generate a verbose log and see what is going on.

-Original Message-
From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk]
Sent: Monday, October 04, 2010 12:58 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Issues when evaluating a condition

Hi: 
Even after changing the order, the conditions are still not working as
expected.
Anyone got any idea?
All I need to do is see a particularly registry key exists.
Cheers
Sean.

-Original Message-
From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk]
Sent: 04 October 2010 19:09
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Issues when evaluating a condition

Hi: 
Thanks, just what I need, incidentally, what is the need to modify both
the ui and execute sequences?
Cheers
Sean.

-Original Message-
From: Blair [mailto:os...@live.com]
Sent: 04 October 2010 18:53
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Issues when evaluating a condition

http://wix.mindcapers.com/wiki/Launch_Conditions

-Original Message-
From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk]
Sent: Monday, October 04, 2010 10:28 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Issues when evaluating a condition

Hi: 
Ok, given the launch conditions are checked before app search, how do I
reverse this in wix?
Cheers
Sean.

-Original Message-
From: Blair [mailto:os...@live.com]
Sent: 04 October 2010 16:30
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Issues when evaluating a condition

Both will do it, but if Orca is already installed it is usually faster.
Dark will usually only show the derivation from the "standard" sequence,
which happens to check launch conditions before running AppSearch (just
the opposite of what you want).

-Original Message-
From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk]
Sent: Monday, October 04, 2010 4:51 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Issues when evaluating a condition

Will decompiling the msi with dark give me the sequence tables, or is
orca the only way?
Cheers
Sean.

-Original Message-
From: Blair [mailto:os...@live.com]
Sent: 04 October 2010 12:38
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Issues when evaluating a condition

Verify the order between the AppSearch and the LaunchConditions actions
in the sequence table. You may have to explicitly set one before or
after the other.

-Original Message-
From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk]
Sent: Sunday, October 03, 2010 10:10 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Issues when evaluating a condition

Hi:
I'm trying to write a launch condition for my installer.
I have the following fragment:

  

  

  
When the registry search takes place, it should set the value of the
property to ""
I hthen have the following condition:

  

The condition is still evaluated to true, even after the registry search
has happened, I know the product is installed, having checked using
regedit.
Anyone got any ideas?
Cheers
Sean.


--
Start uncovering the many advantages of virtual appliances and start
using them to simplify application deployment and accelerate your shift
to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
Virtualization is moving to the mainstream and overtaking
non-virtualized environment for deploying applications. Does it make
network security easier or more difficult to achieve? Read this
whitepaper to separate the two and get a better understanding.
http://p.sf.net/sfu/hp-phase2-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

---

Re: [WiX-users] Issues when evaluating a condition

[Chad Petersen]

I was having the same issue after converting from Wix2 to Wix3. Once I
added



To both InstallUISequence and InstallExecuteSequence then it started
working right for me. Sounds like what you already tried. If so, use
Orca to inspect both sequence tables and see if it shows up there in the
proper order.

It seems to me that was all I did at the time, but it's been a few
months since I converted. It took a few tries to see it correct in Orca.
Not sure if my OBJ files were not getting updated and hence no change to
the MSI at first.

At least I can confirm that it worked for one person.

-Original Message-
From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] 
Sent: Monday, October 04, 2010 12:58 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Issues when evaluating a condition

Hi: 
Even after changing the order, the conditions are still not working as
expected.
Anyone got any idea?
All I need to do is see a particularly registry key exists.
Cheers
Sean.

-Original Message-
From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] 
Sent: 04 October 2010 19:09
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Issues when evaluating a condition

Hi: 
Thanks, just what I need, incidentally, what is the need to modify both
the ui and execute sequences?
Cheers
Sean.

-Original Message-
From: Blair [mailto:os...@live.com] 
Sent: 04 October 2010 18:53
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Issues when evaluating a condition

http://wix.mindcapers.com/wiki/Launch_Conditions

-Original Message-
From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] 
Sent: Monday, October 04, 2010 10:28 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Issues when evaluating a condition

Hi: 
Ok, given the launch conditions are checked before app search, how do I
reverse this in wix?
Cheers
Sean.

-Original Message-
From: Blair [mailto:os...@live.com] 
Sent: 04 October 2010 16:30
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Issues when evaluating a condition

Both will do it, but if Orca is already installed it is usually faster.
Dark
will usually only show the derivation from the "standard" sequence,
which
happens to check launch conditions before running AppSearch (just the
opposite of what you want).

-Original Message-
From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] 
Sent: Monday, October 04, 2010 4:51 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Issues when evaluating a condition

Will decompiling the msi with dark give me the sequence tables, or is
orca
the only way?
Cheers
Sean.

-Original Message-
From: Blair [mailto:os...@live.com] 
Sent: 04 October 2010 12:38
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Issues when evaluating a condition

Verify the order between the AppSearch and the LaunchConditions actions
in
the sequence table. You may have to explicitly set one before or after
the
other.

-Original Message-
From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] 
Sent: Sunday, October 03, 2010 10:10 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Issues when evaluating a condition

Hi:
I'm trying to write a launch condition for my installer.
I have the following fragment:

  

  

  
When the registry search takes place, it should set the value of the
property to ""
I hthen have the following condition:

  

The condition is still evaluated to true, even after the registry search
has
happened, I know the product is installed, having checked using regedit.
Anyone got any ideas?
Cheers
Sean.


--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
Virtualization is moving to the mainstream and overtaking
non-virtualized
environment for deploying applications. Does it make network security 
easier or more difficult to achieve? Read this whitepaper to separate
the 
two and get a better understanding.
http://p.sf.net/sfu/hp-phase2-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Virtualization is moving to the mainstream and overtaking
non-virtualized
environment for deploying applications. Does it make net

Re: [WiX-users] set a property based on different OS

[Chad Petersen]

Use a separate Component for each necessary shortcut and then apply a
child Condition on each component based off of the VersionNT= property.
Here's a good reference for VersionNT.

http://msdn.microsoft.com/en-us/library/aa370556(v=VS.85).aspx

-Original Message-
From: Wu, Emma (GE Intelligent Platforms) [mailto:emma...@ge.com] 
Sent: Monday, October 04, 2010 8:34 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] set a property based on different OS

Hi,

 

I have a wix project creating my msi package for install. I have a
shortcut to be created in the program menu.

However, the target of this shortcut would be different based on
different operating system. How can I do that?

Thanks.

 

Emma


--
Virtualization is moving to the mainstream and overtaking
non-virtualized
environment for deploying applications. Does it make network security 
easier or more difficult to achieve? Read this whitepaper to separate
the 
two and get a better understanding.
http://p.sf.net/sfu/hp-phase2-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Virtualization is moving to the mainstream and overtaking non-virtualized
environment for deploying applications. Does it make network security 
easier or more difficult to achieve? Read this whitepaper to separate the 
two and get a better understanding.
http://p.sf.net/sfu/hp-phase2-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Uninstall question

[Chad Petersen]

Our product requires another product to be pre-installed. We then
overwrite some of the other products files during our install as the
"integration points" between our two products.

 

If they are in Folder A and my product goes into Folder B, then it would
be true that when we detect them we are supposed to overwrite some files
in Folder A. This is fine during the install of our product, but if the
other product gets uninstalled first and then I try to uninstall ours it
gives an error 1316. Before doing our uninstall if I replace the handful
of files we overwrite in Folder B that were removed by the other
products uninstall, then all is fine with my uninstall.

 

I've tried setting the Component of each to "Permanent="yes" and also
tried compressing those same files in hopes they would exist in the
cahed MSI, but it is stripped clean of files.

 

What's the proper approach here? Do I need to discover the GUIDs used by
their Components and replicate them in our product, hoping there can be
a one-to-one relationship?

 

Once they uncompress part way into my TEMP folder I can only see a
SETUP.EXE and other files like ISSetup.dll, but no MSI. It's
InstallShield, but I can't use Orca on it to crack their GUIDs.

 

Any advice would be great.

 

Thanks

 

--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Command Line ParameterstoDeferred CustomAction on Vista

[Chad Petersen]

CustomActionData is that magical packet of information passed from the 
installer to your deferred CustomAction using the Value= attribute.

Then, your .exe (or VBScript or Javascript) has to set a variable to the value 
of Session.Property("CustomActionData"); so it gets a copy of this information 
to use.

This info might help a little

http://msdn.microsoft.com/en-us/library/2w2fhwzz(VS.71).aspx



-Original Message-
From: Matt Walker [mailto:matt.wal...@synergis.com] 
Sent: Wednesday, September 22, 2010 10:07 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Command Line ParameterstoDeferred CustomAction on Vista

I guess I'm still a little foggy on it so I'll keep digging.  If
CustomActionData is needed to get values to Deferred Custom Actions, how
then is my property value, populated in the Property Table, getting to
my deferred action?  In addition to having the property pre-populated in
the table, I also added it to SecureCustomProperties.  However I'm not
using the Set Directory CA mechanism to get the value to
CustomActionData.

I don't know if I mentioned this before, but my Deferred Custom Action
fires an .exe stored in the Binary Table with the following command line
parameters being passed [ProductCode] [OURVERSION], the later being the
pre-populated property.

I don't know why, but I can't seem to get a handle on this!  :(


Matt Walker
Installation Development
200 Kelly Road | Quakertown, PA 18951
Phone: +1 215.529.9900, x192 | 800.836.5440 
Fax: +1 215.536.9249
http://www.synergissoftware.com/
Adept Engineering Document Management & Workflow
This message (and any associated files) is intended only for the use of the 
individual or entity to which it is addressed and may contain information that 
is confidential, subject to copyright or constitutes a trade secret. If you are 
not the intended recipient you are hereby notified that any dissemination, 
copying or distribution of this message, or files associated with this message, 
is strictly prohibited. If you have received this message in error, please 
notify us immediately by replying to the message and deleting it from your 
computer. Messages sent to and from us may be monitored.
Internet communications cannot be guaranteed to be secure or error-free as 
information could be intercepted, corrupted, lost, destroyed, arrive late or 
incomplete, or contain viruses. Therefore, we do not accept responsibility for 
any errors or omissions that are present in this message, or any attachment, 
that have arisen as a result of e-mail transmission. If verification is 
required, please request a hard-copy version. Any views or opinions presented 
are solely those of the author and do not necessarily represent those of the 
company.
-Original Message-

From: Wilson, Phil [mailto:phil.wil...@invensys.com] 
Sent: Wednesday, September 22, 2010 12:52 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Command Line Parameters toDeferred CustomAction
on Vista

They are still two separate items. SecureCustomProperties is need if you
want to pass properties from the UI to the execute sequence, whether
they get passed to custom actions or not. If you pass them to a
immediate custom actions there's no need to use CustomActionData. So if
you wanted to collect a property value in the UI sequence AND pass it to
a deferred custom action then you'd need to use SCP to get it into the
execute sequence AND use CustomActionData to pass it to a deferred
custom action. 

You might be thinking that CustomActionData is a single property, but
it's not. Every deferred custom action can have its own CustomActionData
associated with it. Yes, it's used to pass property values into deferred
custom actions. You simply cannot directly get property values in
deferred custom actions, that's what CustomActionData is for. 

There'a a paragraph or two at the end here
http://msdn.microsoft.com/en-us/library/aa370543(VS.85).aspx 

Phil Wilson 


-Original Message-
From: Matt Walker [mailto:matt.wal...@synergis.com] 
Sent: Tuesday, September 21, 2010 6:45 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Command Line Parameters to Deferred
CustomAction on Vista

Since both worked in my scenario, I still, really don't know the
difference.

When you say SCPs is used to pass property values to the execute
sequence, does that include access during or for deferred custom
actions?  Or, is CAD used to pass information to the deferred actions?

Would there be a good example to illustrate the need for the use of
CustomActionData where simply adding a property to
SecureCustomProperties would not provide access during the deferred
sequence?

Any further help greatly appreciated.

-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com] 
Sent: Tuesday, September 21, 2010 5:17 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re:

Re: [WiX-users] Here is my product.wxs; How to install to two different directories: C:\Program Files\MyApp and C:\Windows\System32 directory

[Chad Petersen]

The folder is referred to as "SystemFolder"

I'm fairly sure you can get away with only a DirectoryRef to it since it
is a built-in property.


-Original Message-
From: Beekeeper [mailto:bria...@yahoo.com] 
Sent: Tuesday, September 14, 2010 1:07 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Here is my product.wxs; How to install to two
different directories: C:\Program Files\MyApp and C:\Windows\System32
directory


Here is my product.wxs, how to install to two different directories.



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






  

  




  

  
  

  



  

  



  

  
  

  
  

  
  

  





  
  



  
  
  
  


  


-- 
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Here-is-my
-product-wxs-How-to-install-to-two-different-directories-C-Program-Files
-MyApp-and-C-Windoy-tp5531850p5531850.html
Sent from the wix-users mailing list archive at Nabble.com.


--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Default Install Drive to be Largest Free Space Drive of Physical Disk

[Chad Petersen]

That is handled by the ROOTDRIVE property. Not sure you can avoid USB
drives, though.

http://msdn.microsoft.com/en-us/library/aa371372(VS.85).aspx



-Original Message-
From: Prabhat_IE [mailto:prabhat.n...@gmail.com] 
Sent: Tuesday, August 31, 2010 2:00 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Default Install Drive to be Largest Free Space
Drive of Physical Disk


Hello,

By defaul in wix (I am using 3.5) the drive letter is selected to the
largest available in PC (may be a USB). 
How can I make sure my installer will do the same (defaul to largest
free
space drive) but on my physica disk.

Please advise.

Thanks,
Prabhat
-- 
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Default-In
stall-Drive-to-be-Largest-Free-Space-Drive-of-Physical-Disk-tp5484492p54
84492.html
Sent from the wix-users mailing list archive at Nabble.com.


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

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



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

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to change an entry using XmlConfig

[Chad Petersen]

Sorry, I missed that David had already replied.

-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com] 
Sent: Tuesday, August 31, 2010 10:43 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to change an entry using XmlConfig

In your Value= line you will need to escape the square brackets.
XMLConfig mentions this in the Value Attribute Description column.

Opening bracket - [\[]
Closing bracket - [\]]

-Original Message-
From: Alexander op de Weegh [mailto:alexan...@ipa-tp.nl] 
Sent: Tuesday, August 31, 2010 3:50 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to change an entry using XmlConfig

Hi all,

I am not an expert on Xml, let alone XPath, so I am running into this
problem. With my application the following NHibernate.config file is
used:



  
NHibernate.Connection.DriverConnectionProvide
r
NHibernate.ByteCode.LinFu.ProxyFactory
Factory, NHibernate.ByteCode.LinFu
NHibernate.Driver.MySqlDataDriver
Database=schemaname;Data
Source=localhost;User Id=username;Password=password
NHibernate.Dialect.MySQLDialect 
  


The configuration file is set up to be used from the Visual Studio
environment. In my Wix file, I have the following entry:


With this XmlConfig entry, I try to modify the value of the connection
string in the NHibernate.config file according to the settings specified
by the user during the installation. The MYSQLxxx parameters are
collected in one of the custom dialogs.

During the run of the Xml linker, the following error occurs:
LGHT0204 : ICE03: Invalid format string; Table: XmlConfig, Column:
ElementPath, Key(s): MySqlConnectionProperty

Can anyone help me out here? Thanks in advance,

Met vriendelijke groeten / With kind regards,
Alexander op de Weegh

Office:  +31(0)226-335023
Mobile: +31(0)6-20138301

IPA Total Productivity
Kosterij 4
1721 PN Broek op Langedijk
The Netherlands

www.ipa-tp.nl
of kijkt u eens op www.blean.nl van onze partner B-Lean voor het trainen
en implementeren
van productiemethodieken en het verbeteren van uw productiviteit.



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

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




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

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



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

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] How to change an entry using XmlConfig

[Chad Petersen]

In your Value= line you will need to escape the square brackets.
XMLConfig mentions this in the Value Attribute Description column.

Opening bracket - [\[]
Closing bracket - [\]]

-Original Message-
From: Alexander op de Weegh [mailto:alexan...@ipa-tp.nl] 
Sent: Tuesday, August 31, 2010 3:50 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to change an entry using XmlConfig

Hi all,

I am not an expert on Xml, let alone XPath, so I am running into this
problem. With my application the following NHibernate.config file is
used:



  
NHibernate.Connection.DriverConnectionProvide
r
NHibernate.ByteCode.LinFu.ProxyFactory
Factory, NHibernate.ByteCode.LinFu
NHibernate.Driver.MySqlDataDriver
Database=schemaname;Data
Source=localhost;User Id=username;Password=password
NHibernate.Dialect.MySQLDialect 
  


The configuration file is set up to be used from the Visual Studio
environment. In my Wix file, I have the following entry:


With this XmlConfig entry, I try to modify the value of the connection
string in the NHibernate.config file according to the settings specified
by the user during the installation. The MYSQLxxx parameters are
collected in one of the custom dialogs.

During the run of the Xml linker, the following error occurs:
LGHT0204 : ICE03: Invalid format string; Table: XmlConfig, Column:
ElementPath, Key(s): MySqlConnectionProperty

Can anyone help me out here? Thanks in advance,

Met vriendelijke groeten / With kind regards,
Alexander op de Weegh

Office:  +31(0)226-335023
Mobile: +31(0)6-20138301

IPA Total Productivity
Kosterij 4
1721 PN Broek op Langedijk
The Netherlands

www.ipa-tp.nl
of kijkt u eens op www.blean.nl van onze partner B-Lean voor het trainen
en implementeren
van productiemethodieken en het verbeteren van uw productiviteit.



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

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



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

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] XMLConfig question

[Chad Petersen]

Dave, thank you so much. Other than the compiler didn't like a blank
Name= and just wanted it removed completely, this did the trick. Thanks
for the nudge over the edge. You made my Friday...

Chad

-Original Message-
From: David Watson [mailto:dwat...@sdl.com] 
Sent: Friday, August 27, 2010 3:28 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] XMLConfig question

Hi,
I've not tried this but, it looks like your ElementPath is referring to
the context-param element you will probably need to add Param-value to
the end to select that node and leave the Name="" as then it will add to
the elements text.



Dave

-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com] 
Sent: 26 August 2010 22:27
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] XMLConfig question

I've made some headway, but not quite there yet. The closest I've gotten
so far is this code



Which results in this value being written to the second line below
rather than it modifying the fourth line. 



DEFAULT_LOCALE
en_US


DEFAULT_TIMEZONE
Pacific



-----Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com] 
Sent: Thursday, August 26, 2010 11:26 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] XMLConfig question

I have an XML file that looks like this. The goal is to alter the en_US
to some other value.



DEFAULT_LOCALE
en_US


DEFAULT_TIMEZONE
Pacific



I've written a very small installer with this entry



The verbose log says "Installation failed" near the end, but it doesn't
display an error, it simply rolls back. I'm not sure if my xPath syntax
is wrong or exactly what it doesn't like. Any ideas?

WiX 3.0.5419.0

Thanks



--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users

worldwide. Take advantage of special opportunities to increase revenue
and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users

worldwide. Take advantage of special opportunities to increase revenue
and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


http://www.sdl.com";>http://www.sdl.com/images/email
logo_150dpi-01.png" alt="www.sdl.com" border="0"/>

http://www.sdl.com";
style="color:005740; font-weight: bold">www.sdl.com



SDL PLC confidential, all rights reserved.
If you are not the intended recipient of this mail SDL requests and
requires that you delete it without acting upon or copying any of its
contents, and we further request that you advise us.
SDL PLC is a public limited company registered in England and Wales.
Registered number: 02675207.
Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire
SL6 7DY, UK.





--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users

worldwide. Take advantage of special opportunities to increase revenue
and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] XMLConfig question

[Chad Petersen]

I've made some headway, but not quite there yet. The closest I've gotten
so far is this code



Which results in this value being written to the second line below
rather than it modifying the fourth line. 



DEFAULT_LOCALE
en_US


DEFAULT_TIMEZONE
Pacific



-Original Message-----
From: Chad Petersen [mailto:chad.peter...@harlandfs.com] 
Sent: Thursday, August 26, 2010 11:26 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] XMLConfig question

I have an XML file that looks like this. The goal is to alter the en_US
to some other value.



DEFAULT_LOCALE
en_US


DEFAULT_TIMEZONE
Pacific



I've written a very small installer with this entry



The verbose log says "Installation failed" near the end, but it doesn't
display an error, it simply rolls back. I'm not sure if my xPath syntax
is wrong or exactly what it doesn't like. Any ideas?

WiX 3.0.5419.0

Thanks



--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users

worldwide. Take advantage of special opportunities to increase revenue
and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Question about using XmlFile (WixUtilExtension.dll in general, actually)

[Chad Petersen]

Try adding the xmlns:util="http://schemas.microsoft.com/wix/UtilExtension"; 
schema to the top of the file that has the XmlFile element in it.

Mine looks like this

http://www.w3.org/2001/XMLSchema-instance"; 
xmlns="http://schemas.microsoft.com/wix/2006/wi"; 
xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";>

-Original Message-
From: Dave DaveLists [mailto:dbfli...@gmail.com] 
Sent: Wednesday, August 25, 2010 8:50 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Question about using XmlFile (WixUtilExtension.dll in 
general, actually)

Ah, yes, sorry. It is a wix compiler error:

The Component element contains an unhandled extension element
'util:XmlFile'.  Please ensure that the extension for elements in the
'http:⁄⁄schemas.microsoft.com⁄wix⁄UtilExtension' namespace has been
provided.

I googled this line and found a few references to it but the
suggestion was always to add a reference to WixUtilExtension.dll,
which we already have. We tried deleting it and putting it back in
manually but this did not help (and I verified that the DLL is in the
directory where candle and light are, just to be sure).

Thanks,

-Dave

On Tue, Aug 24, 2010 at 6:16 PM, Bob Arnson  wrote:
>  On 24-Aug-10 21:00, Dave DaveLists wrote:
>> we expected to be able to reference XmlFile using util:XmlFile but
>> this is failing at compile time.
>
> It might help if you described how it was failing...
>
> --
> sig://boB
> http://joyofsetup.com/
>
>
> --
> Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
> Be part of this innovative community and reach millions of netbook users
> worldwide. Take advantage of special opportunities to increase revenue and
> speed time-to-market. Join now, and jumpstart your future.
> http://p.sf.net/sfu/intel-atom-d2d
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>

--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] XMLConfig question

[Chad Petersen]

I have an XML file that looks like this. The goal is to alter the en_US
to some other value.



DEFAULT_LOCALE
en_US


DEFAULT_TIMEZONE
Pacific



I've written a very small installer with this entry



The verbose log says "Installation failed" near the end, but it doesn't
display an error, it simply rolls back. I'm not sure if my xPath syntax
is wrong or exactly what it doesn't like. Any ideas?

WiX 3.0.5419.0

Thanks


--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users