date:20130313

No no, you got me all wrong.
I don't want cumulative patches! The opposite, I want the last patch that I 
install to supersede all others, overwriting the files.

I have the MSP file and in z7 I can see that it has all the right files, that 
is the new files. But if I install it after I installed an earlier patch... 
those files don't get to the installation folder...?! I'm using: 
msiexec.exe /L*v c:\temp\log.txt /p c:\temp\patch2\patch.msp REINSTALL=ALL 
REINSTALLMODE=aumsv ADDLOCAL=ALL REBOOT=ReallySuppress
the log of the second patch installation:
Note: 1: 2228 2:  3: MsiAssembly 4:  SELECT `MsiAssembly`.`Attributes`, 
`MsiAssembly`.`File_Application`, `MsiAssembly`.`File_Manifest`,  
`Component`.`KeyPath` FROM `MsiAssembly`, `Component` WHERE  
`MsiAssembly`.`Component_` = `Component`.`Component` AND 
`MsiAssembly`.`Component_` = ? 
MSI (s) (48:C4) [15:13:42:791]: Patch Modified Files List:
//it gives only a partial list of the files that are in the MSP file... 
allthose files are !NOT! .NET dlls, the .NET dlls are the files that don't get 
overwritten for some reason...

Please help! Thanks.

Tomer Cohen
InSight Team Leader, RD
QualiSystems
Mobile: +972-52-3362846
Email: tome...@qualisystems.com
Web: www.qualisystems.com

-Original Message-
From: Brian_Covington [mailto:briancoving...@yahoo.com] 
Sent: יום ד 13 מרץ 2013 06:02
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede 
first Patch

Sorry, no.  We are weeks away from having to release and the plan for now is to 
not use cumulative patches.

 


 From: Tomer Cohen [via Windows Installer XML (WiX) toolset] 
ml-node+s687559n758426...@n2.nabble.com
To: Brian_Covington briancoving...@yahoo.com 
Sent: Tuesday, March 12, 2013 10:11 AM
Subject: Re: Managed Bootstrapper - Second Patch does not supersede first Patch
  

Got anywhere with this? I have the same problem 
I don't mind having both patches appear in the add remove - updates side by 
side, but the second patch doesn't replace the files at all... 
If I install it without the first patch already installed then that patch works 
great. 

Tomer. 
Thanks. 

-Original Message- 
From: Brian_Covington [mailto:[hidden email]] 
Sent: יום ה 15 נובמבר 2012 00:41 
To: [hidden email] 
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede 
first Patch 

Same results with versions 10.00.35.0004, 10.00.36.0004 (HF1), and 
10.00.37.0004 (HF2). 

I am changing the bundle version as well as the version of the msi, but still 
the second patch for the bundle appears alongside the first one, not replacing 
it as I would expect. 

Do I need to do something to hide the first patch when the second one is 
applied?  And if so, how would I undo this when uninstalling the second patch? 

As these are cumulative, removable patches, only one entry must exist in the 
Installed Updates of ARP. 

I do see where it realized the first patch bundle was installed, but did 
nothing with it. 

Plan 3 packages, action: Install 
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on package 
with no dependency providers: Netfx4Full 
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on package 
with no dependency providers: S3DInstallPatch 
[0F98:0E38][2012-11-14T16:19:55]: Setting string variable 
'WixBundleLog_S3DInstallPatch' to value 
'C:\Users\sp3dtest\AppData\Local\Temp\PRODUCT_S3D_HotFix_2_20121114161952_{C193CA79-FACC-4874-AF85-6CCC6B10851C}_0_S3DInstallPatch.log'
 
[0F98:0E38][2012-11-14T16:19:55]: Setting string variable 
'WixBundleRollbackLog_S3DInstallPatch' to value 
'C:\Users\sp3dtest\AppData\Local\Temp\PRODUCT_S3D_HotFix_2_20121114161952_{C193CA79-FACC-4874-AF85-6CCC6B10851C}_0_S3DInstallPatch_rollback.log'
 
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on package 
with no dependency providers: RADInstallPatch 
[0F98:0E38][2012-11-14T16:19:55]: Planned package: Netfx4Full, state: 
Present, default requested: Present, ba requested: Present, execute: None, 
rollback: None, cache: No, uncache: No, dependency: None 
[0F98:0E38][2012-11-14T16:19:55]: Planned package: S3DInstallPatch, state: 
Absent, default requested: Present, ba requested: Present, execute: Install, 
rollback: Uninstall, cache: Yes, uncache: No, dependency: None 
[0F98:0E38][2012-11-14T16:19:55]: Planned package: RADInstallPatch, state: 
Present, default requested: Present, ba requested: Present, execute: None, 
rollback: None, cache: No, uncache: No, dependency: None 
*[0F98:0E38][2012-11-14T16:19:55]: Planned related bundle: 
{1ca42db4-c103-4fa2-ba05-d3c20f8f5d70}, type: Dependent, default requested: 
None, ba requested: None, execute: None, rollback: None, dependency: None* 

Then in the msi install log, I see 

Final Patch Application Order: 
MSI (s) (44:2C) [16:20:06:348]: {379A67FF-1175-42B8-B7B7-8F8ED98CA7EB} - 
C:\ProgramData\Package

Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch

2013-03-13 Thread David Watson

Did you increase the assemblyfileversion of those dlls?

-Original Message-
From: Tomer Cohen [mailto:tome...@qualisystems.com] 
Sent: 13 March 2013 13:28
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not
supersede first Patch

No no, you got me all wrong.
I don't want cumulative patches! The opposite, I want the last patch that I
install to supersede all others, overwriting the files.

I have the MSP file and in z7 I can see that it has all the right files,
that is the new files. But if I install it after I installed an earlier
patch... those files don't get to the installation folder...?! I'm using: 
msiexec.exe /L*v c:\temp\log.txt /p c:\temp\patch2\patch.msp REINSTALL=ALL
REINSTALLMODE=aumsv ADDLOCAL=ALL REBOOT=ReallySuppress the log of the second
patch installation:
Note: 1: 2228 2:  3: MsiAssembly 4:  SELECT `MsiAssembly`.`Attributes`,
`MsiAssembly`.`File_Application`, `MsiAssembly`.`File_Manifest`,
`Component`.`KeyPath` FROM `MsiAssembly`, `Component` WHERE
`MsiAssembly`.`Component_` = `Component`.`Component` AND
`MsiAssembly`.`Component_` = ? 
MSI (s) (48:C4) [15:13:42:791]: Patch Modified Files List:
//it gives only a partial list of the files that are in the MSP file...
allthose files are !NOT! .NET dlls, the .NET dlls are the files that don't
get overwritten for some reason...

Please help! Thanks.

Tomer Cohen
InSight Team Leader, RD
QualiSystems
Mobile: +972-52-3362846
Email: tome...@qualisystems.com
Web: www.qualisystems.com

-Original Message-
From: Brian_Covington [mailto:briancoving...@yahoo.com]
Sent: יום ד 13 מרץ 2013 06:02
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not
supersede first Patch

Sorry, no.  We are weeks away from having to release and the plan for now is
to not use cumulative patches.

 From: Tomer Cohen [via Windows Installer XML (WiX) toolset]
ml-node+s687559n758426...@n2.nabble.com
To: Brian_Covington briancoving...@yahoo.com
Sent: Tuesday, March 12, 2013 10:11 AM
Subject: Re: Managed Bootstrapper - Second Patch does not supersede first
Patch

Got anywhere with this? I have the same problem 
I don't mind having both patches appear in the add remove - updates side by
side, but the second patch doesn't replace the files at all... 
If I install it without the first patch already installed then that patch
works great. 

Tomer. 
Thanks. 

-Original Message- 
From: Brian_Covington [mailto:[hidden email]] 
Sent: יום ה 15 נובמבר 2012 00:41 
To: [hidden email] 
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not
supersede first Patch 

Same results with versions 10.00.35.0004, 10.00.36.0004 (HF1), and 
10.00.37.0004 (HF2). 

I am changing the bundle version as well as the version of the msi, but still
the second patch for the bundle appears alongside the first one, not
replacing it as I would expect. 

Do I need to do something to hide the first patch when the second one is
applied?  And if so, how would I undo this when uninstalling the second
patch? 

As these are cumulative, removable patches, only one entry must exist in the
Installed Updates of ARP. 

I do see where it realized the first patch bundle was installed, but did
nothing with it. 

Plan 3 packages, action: Install 
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on package
with no dependency providers: Netfx4Full 
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on package
with no dependency providers: S3DInstallPatch 
[0F98:0E38][2012-11-14T16:19:55]: Setting string variable
'WixBundleLog_S3DInstallPatch' to value
'C:\Users\sp3dtest\AppData\Local\Temp\PRODUCT_S3D_HotFix_2_20121114161952_{C1
93CA79-FACC-4874-AF85-6CCC6B10851C}_0_S3DInstallPatch.log' 
[0F98:0E38][2012-11-14T16:19:55]: Setting string variable
'WixBundleRollbackLog_S3DInstallPatch' to value
'C:\Users\sp3dtest\AppData\Local\Temp\PRODUCT_S3D_HotFix_2_20121114161952_{C1
93CA79-FACC-4874-AF85-6CCC6B10851C}_0_S3DInstallPatch_rollback.log' 
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on package
with no dependency providers: RADInstallPatch 
[0F98:0E38][2012-11-14T16:19:55]: Planned package: Netfx4Full, state: 
Present, default requested: Present, ba requested: Present, execute: None, 
rollback: None, cache: No, uncache: No, dependency: None 
[0F98:0E38][2012-11-14T16:19:55]: Planned package: S3DInstallPatch, state: 
Absent, default requested: Present, ba requested: Present, execute: Install, 
rollback: Uninstall, cache: Yes, uncache: No, dependency: None 
[0F98:0E38][2012-11-14T16:19:55]: Planned package: RADInstallPatch, state: 
Present, default requested: Present, ba requested: Present, execute: None, 
rollback: None, cache: No, uncache: No, dependency: None 
*[0F98:0E38][2012-11-14T16:19:55]: Planned related bundle: 
{1ca42db4-c103-4fa2-ba05-d3c20f8f5d70}, type: Dependent,

Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch

No... there is nothing in the documentation about that...
Won't it make the .NET stop working, the assemblies are signed... if some are 
not in the same version, it won't find them...

Thanks for the fast reply. :)



-Original Message-
From: David Watson [mailto:dwat...@sdl.com] 
Sent: יום ד 13 מרץ 2013 16:04
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede 
first Patch

Did you increase the assemblyfileversion of those dlls?

-Original Message-
From: Tomer Cohen [mailto:tome...@qualisystems.com]
Sent: 13 March 2013 13:28
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede 
first Patch

No no, you got me all wrong.
I don't want cumulative patches! The opposite, I want the last patch that I 
install to supersede all others, overwriting the files.

I have the MSP file and in z7 I can see that it has all the right files, that 
is the new files. But if I install it after I installed an earlier patch... 
those files don't get to the installation folder...?! I'm using: 
msiexec.exe /L*v c:\temp\log.txt /p c:\temp\patch2\patch.msp REINSTALL=ALL 
REINSTALLMODE=aumsv ADDLOCAL=ALL REBOOT=ReallySuppress the log of the second 
patch installation:
Note: 1: 2228 2:  3: MsiAssembly 4:  SELECT `MsiAssembly`.`Attributes`, 
`MsiAssembly`.`File_Application`, `MsiAssembly`.`File_Manifest`, 
`Component`.`KeyPath` FROM `MsiAssembly`, `Component` WHERE 
`MsiAssembly`.`Component_` = `Component`.`Component` AND 
`MsiAssembly`.`Component_` = ? 
MSI (s) (48:C4) [15:13:42:791]: Patch Modified Files List:
//it gives only a partial list of the files that are in the MSP file...
allthose files are !NOT! .NET dlls, the .NET dlls are the files that don't get 
overwritten for some reason...

Please help! Thanks.

Tomer Cohen
InSight Team Leader, RD
QualiSystems
Mobile: +972-52-3362846
Email: tome...@qualisystems.com
Web: www.qualisystems.com

-Original Message-
From: Brian_Covington [mailto:briancoving...@yahoo.com]
Sent: יום ד 13 מרץ 2013 06:02
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede 
first Patch

Sorry, no.  We are weeks away from having to release and the plan for now is to 
not use cumulative patches.

 


 From: Tomer Cohen [via Windows Installer XML (WiX) toolset] 
ml-node+s687559n758426...@n2.nabble.com
To: Brian_Covington briancoving...@yahoo.com
Sent: Tuesday, March 12, 2013 10:11 AM
Subject: Re: Managed Bootstrapper - Second Patch does not supersede first Patch
  

Got anywhere with this? I have the same problem 
I don't mind having both patches appear in the add remove - updates side by 
side, but the second patch doesn't replace the files at all... 
If I install it without the first patch already installed then that patch works 
great. 

Tomer. 
Thanks. 

-Original Message-
From: Brian_Covington [mailto:[hidden email]]
Sent: יום ה 15 נובמבר 2012 00:41
To: [hidden email]
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede 
first Patch 

Same results with versions 10.00.35.0004, 10.00.36.0004 (HF1), and
10.00.37.0004 (HF2). 

I am changing the bundle version as well as the version of the msi, but still 
the second patch for the bundle appears alongside the first one, not replacing 
it as I would expect. 

Do I need to do something to hide the first patch when the second one is 
applied?  And if so, how would I undo this when uninstalling the second patch? 

As these are cumulative, removable patches, only one entry must exist in the 
Installed Updates of ARP. 

I do see where it realized the first patch bundle was installed, but did 
nothing with it. 

Plan 3 packages, action: Install
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on package 
with no dependency providers: Netfx4Full
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on package 
with no dependency providers: S3DInstallPatch
[0F98:0E38][2012-11-14T16:19:55]: Setting string variable 
'WixBundleLog_S3DInstallPatch' to value
'C:\Users\sp3dtest\AppData\Local\Temp\PRODUCT_S3D_HotFix_2_20121114161952_{C1
93CA79-FACC-4874-AF85-6CCC6B10851C}_0_S3DInstallPatch.log' 
[0F98:0E38][2012-11-14T16:19:55]: Setting string variable 
'WixBundleRollbackLog_S3DInstallPatch' to value
'C:\Users\sp3dtest\AppData\Local\Temp\PRODUCT_S3D_HotFix_2_20121114161952_{C1
93CA79-FACC-4874-AF85-6CCC6B10851C}_0_S3DInstallPatch_rollback.log' 
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on package 
with no dependency providers: RADInstallPatch
[0F98:0E38][2012-11-14T16:19:55]: Planned package: Netfx4Full, state: 
Present, default requested: Present, ba requested: Present, execute: None,
rollback: None, cache: No, uncache: No, dependency: None
[0F98:0E38][2012-11-14T16:19:55]: Planned package:

Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch

Just to be clear, the files don't have a newer version, but they are different 
in size and binary...

-Original Message-
From: David Watson [mailto:dwat...@sdl.com] 
Sent: יום ד 13 מרץ 2013 16:04
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede 
first Patch

Did you increase the assemblyfileversion of those dlls?

-Original Message-
From: Tomer Cohen [mailto:tome...@qualisystems.com]
Sent: 13 March 2013 13:28
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede 
first Patch

No no, you got me all wrong.
I don't want cumulative patches! The opposite, I want the last patch that I 
install to supersede all others, overwriting the files.

I have the MSP file and in z7 I can see that it has all the right files, that 
is the new files. But if I install it after I installed an earlier patch... 
those files don't get to the installation folder...?! I'm using: 
msiexec.exe /L*v c:\temp\log.txt /p c:\temp\patch2\patch.msp REINSTALL=ALL 
REINSTALLMODE=aumsv ADDLOCAL=ALL REBOOT=ReallySuppress the log of the second 
patch installation:
Note: 1: 2228 2:  3: MsiAssembly 4:  SELECT `MsiAssembly`.`Attributes`, 
`MsiAssembly`.`File_Application`, `MsiAssembly`.`File_Manifest`, 
`Component`.`KeyPath` FROM `MsiAssembly`, `Component` WHERE 
`MsiAssembly`.`Component_` = `Component`.`Component` AND 
`MsiAssembly`.`Component_` = ? 
MSI (s) (48:C4) [15:13:42:791]: Patch Modified Files List:
//it gives only a partial list of the files that are in the MSP file...
allthose files are !NOT! .NET dlls, the .NET dlls are the files that don't get 
overwritten for some reason...

Please help! Thanks.

Tomer Cohen
InSight Team Leader, RD
QualiSystems
Mobile: +972-52-3362846
Email: tome...@qualisystems.com
Web: www.qualisystems.com

-Original Message-
From: Brian_Covington [mailto:briancoving...@yahoo.com]
Sent: יום ד 13 מרץ 2013 06:02
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede 
first Patch

Sorry, no.  We are weeks away from having to release and the plan for now is to 
not use cumulative patches.

 From: Tomer Cohen [via Windows Installer XML (WiX) toolset] 
ml-node+s687559n758426...@n2.nabble.com
To: Brian_Covington briancoving...@yahoo.com
Sent: Tuesday, March 12, 2013 10:11 AM
Subject: Re: Managed Bootstrapper - Second Patch does not supersede first Patch

Got anywhere with this? I have the same problem 
I don't mind having both patches appear in the add remove - updates side by 
side, but the second patch doesn't replace the files at all... 
If I install it without the first patch already installed then that patch works 
great. 

Tomer. 
Thanks. 

-Original Message-
From: Brian_Covington [mailto:[hidden email]]
Sent: יום ה 15 נובמבר 2012 00:41
To: [hidden email]
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede 
first Patch 

Same results with versions 10.00.35.0004, 10.00.36.0004 (HF1), and
10.00.37.0004 (HF2). 

I am changing the bundle version as well as the version of the msi, but still 
the second patch for the bundle appears alongside the first one, not replacing 
it as I would expect. 

Do I need to do something to hide the first patch when the second one is 
applied?  And if so, how would I undo this when uninstalling the second patch? 

As these are cumulative, removable patches, only one entry must exist in the 
Installed Updates of ARP. 

I do see where it realized the first patch bundle was installed, but did 
nothing with it. 

Plan 3 packages, action: Install
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on package 
with no dependency providers: Netfx4Full
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on package 
with no dependency providers: S3DInstallPatch
[0F98:0E38][2012-11-14T16:19:55]: Setting string variable 
'WixBundleLog_S3DInstallPatch' to value
'C:\Users\sp3dtest\AppData\Local\Temp\PRODUCT_S3D_HotFix_2_20121114161952_{C1
93CA79-FACC-4874-AF85-6CCC6B10851C}_0_S3DInstallPatch.log' 
[0F98:0E38][2012-11-14T16:19:55]: Setting string variable 
'WixBundleRollbackLog_S3DInstallPatch' to value
'C:\Users\sp3dtest\AppData\Local\Temp\PRODUCT_S3D_HotFix_2_20121114161952_{C1
93CA79-FACC-4874-AF85-6CCC6B10851C}_0_S3DInstallPatch_rollback.log' 
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on package 
with no dependency providers: RADInstallPatch
[0F98:0E38][2012-11-14T16:19:55]: Planned package: Netfx4Full, state: 
Present, default requested: Present, ba requested: Present, execute: None,
rollback: None, cache: No, uncache: No, dependency: None
[0F98:0E38][2012-11-14T16:19:55]: Planned package: S3DInstallPatch, state: 
Absent, default requested: Present, ba requested: Present, execute: Install,
rollback: Uninstall,

Re: [WiX-users] Managed Bootstrapper - Second Patch doesnot supersede first Patch

2013-03-13 Thread David Watson

You can alter the AssemblyFileVersion without changing the Assembly version,
if you don't have this specified in your AssemblyInfo.cs it will be set to
the same as the assembly version.
e.g.

we bump the build part of assembly file version automatically each build but
assemblyVersion is incremented by hand.

[assembly: AssemblyVersion(1.8.0.0)]
[assembly: AssemblyFileVersion(1.8.3208.0)]


If a binary has a version resource (.net ones do) the windows installer will
update them only if the version is higher.

We have been using cumulative patches for  a few years without too many
issues.
We have not yet used burn though.

-Original Message-
From: Tomer Cohen [mailto:tome...@qualisystems.com] 
Sent: 13 March 2013 14:19
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch doesnot
supersede first Patch

Just to be clear, the files don't have a newer version, but they are
different in size and binary...

-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: יום ד 13 מרץ 2013 16:04
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not
supersede first Patch

Did you increase the assemblyfileversion of those dlls?

-Original Message-
From: Tomer Cohen [mailto:tome...@qualisystems.com]
Sent: 13 March 2013 13:28
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not
supersede first Patch

No no, you got me all wrong.
I don't want cumulative patches! The opposite, I want the last patch that I
install to supersede all others, overwriting the files.

I have the MSP file and in z7 I can see that it has all the right files,
that is the new files. But if I install it after I installed an earlier
patch... those files don't get to the installation folder...?! I'm using: 
msiexec.exe /L*v c:\temp\log.txt /p c:\temp\patch2\patch.msp REINSTALL=ALL
REINSTALLMODE=aumsv ADDLOCAL=ALL REBOOT=ReallySuppress the log of the second
patch installation:
Note: 1: 2228 2:  3: MsiAssembly 4:  SELECT `MsiAssembly`.`Attributes`,
`MsiAssembly`.`File_Application`, `MsiAssembly`.`File_Manifest`,
`Component`.`KeyPath` FROM `MsiAssembly`, `Component` WHERE
`MsiAssembly`.`Component_` = `Component`.`Component` AND
`MsiAssembly`.`Component_` = ? 
MSI (s) (48:C4) [15:13:42:791]: Patch Modified Files List:
//it gives only a partial list of the files that are in the MSP file...
allthose files are !NOT! .NET dlls, the .NET dlls are the files that don't
get overwritten for some reason...

Please help! Thanks.

Tomer Cohen
InSight Team Leader, RD
QualiSystems
Mobile: +972-52-3362846
Email: tome...@qualisystems.com
Web: www.qualisystems.com

-Original Message-
From: Brian_Covington [mailto:briancoving...@yahoo.com]
Sent: יום ד 13 מרץ 2013 06:02
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not
supersede first Patch

Sorry, no.  We are weeks away from having to release and the plan for now is
to not use cumulative patches.

 


 From: Tomer Cohen [via Windows Installer XML (WiX) toolset]
ml-node+s687559n758426...@n2.nabble.com
To: Brian_Covington briancoving...@yahoo.com
Sent: Tuesday, March 12, 2013 10:11 AM
Subject: Re: Managed Bootstrapper - Second Patch does not supersede first
Patch
  

Got anywhere with this? I have the same problem 
I don't mind having both patches appear in the add remove - updates side by
side, but the second patch doesn't replace the files at all... 
If I install it without the first patch already installed then that patch
works great. 

Tomer. 
Thanks. 

-Original Message-
From: Brian_Covington [mailto:[hidden email]]
Sent: יום ה 15 נובמבר 2012 00:41
To: [hidden email]
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not
supersede first Patch 

Same results with versions 10.00.35.0004, 10.00.36.0004 (HF1), and
10.00.37.0004 (HF2). 

I am changing the bundle version as well as the version of the msi, but still
the second patch for the bundle appears alongside the first one, not
replacing it as I would expect. 

Do I need to do something to hide the first patch when the second one is
applied?  And if so, how would I undo this when uninstalling the second
patch? 

As these are cumulative, removable patches, only one entry must exist in the
Installed Updates of ARP. 

I do see where it realized the first patch bundle was installed, but did
nothing with it. 

Plan 3 packages, action: Install
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on package
with no dependency providers: Netfx4Full
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on package
with no dependency providers: S3DInstallPatch
[0F98:0E38][2012-11-14T16:19:55]: Setting string variable
'WixBundleLog_S3DInstallPatch' to value

Re: [WiX-users] issue with fragments in the same project

If the Feature is under the Product element somewhere then I'm at a loss as
to what is actually going wrong. It seems like everything should work. What
is the exact command-line and output you are getting from the tools?


On Wed, Mar 13, 2013 at 1:46 AM, Sean Farrow
sean.far...@seanfarrow.co.ukwrote:

 Hi,

 I't's in the featue, as follows:
 Feature Id=ProductFeature Title=ConnectorMsi Level=1
   ComponentRef Id=Salamander.Host.exe/
 /Feature
 Cheers
 Sean.

 -Original Message-
 From: Rob Mensching [mailto:r...@robmensching.com]
 Sent: 13 March 2013 05:37
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] issue with fragments in the same project

 Where is the ComponentRef to Salamander.Host.exeFile?


 On Tue, Mar 12, 2013 at 5:31 PM, Sean Farrow
 sean.far...@seanfarrow.co.ukwrote:

  Hi,
 
  I'm currently creating an installer.
  In one file I have my folder structure:
  Fragment
  Directory Id=TARGETDIR Name=SourceDir 
Directory Id=ProgramFilesFolder 
  Directory Id=CONPANYFOLDER Name=SalamanderSoft
Directory Id=INSTALLFOLDER Name=Connector
 
/Directory
  /Directory
  /Directory
  /Directory
/Fragment
  in another file in the same project I have fragments with components
  defined.I've tried to refer to the INSTALLFOLDER element with both the
  directory/DirectoryRef element but understandably get a lght0091/92. My
  second file is as follows:
  Fragment
  !--Salamander host executable.--
  DirectoryRef Id=INSTALLFOLDER 
  Component Id=Salamander.Host.exe
  Guid=d535001e-c4cb-4043-9e4b-1abdec33d0f2
File Id=Salamander.Host.exeFile
  Source=..\..\..\bin\obfuscated\Salamander.Host.exe KeyPath=yes
  Checksum=yes/
  /Component
  /DirectoryRef
/FragmentI understand why this is happening, but what is the best
  way around this?
  Any help appreciated.
  Regards
  Sean.
 
 
 --
  Everyone hates slow websites. So do we.
  Make your web apps faster with AppDynamics
  Download AppDynamics Lite for free today:
  http://p.sf.net/sfu/appdyn_d2d_mar
  ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users
 
 

 --
 Everyone hates slow websites. So do we.
 Make your web apps faster with AppDynamics
 Download AppDynamics Lite for free today:
 http://p.sf.net/sfu/appdyn_d2d_mar
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


 --
 Everyone hates slow websites. So do we.
 Make your web apps faster with AppDynamics
 Download AppDynamics Lite for free today:
 http://p.sf.net/sfu/appdyn_d2d_mar
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch

What does the verbose log file in the patch say the action states for the
Components that you expect to be installed? Also, look at the File install
log lines, those usually have quite a bit information about when the file
is being applied and whether it is being patched.


On Wed, Mar 13, 2013 at 7:19 AM, Tomer Cohen tome...@qualisystems.comwrote:

 Just to be clear, the files don't have a newer version, but they are
 different in size and binary...

 -Original Message-
 From: David Watson [mailto:dwat...@sdl.com]
 Sent: יום ד 13 מרץ 2013 16:04
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not
 supersede first Patch

 Did you increase the assemblyfileversion of those dlls?

 -Original Message-
 From: Tomer Cohen [mailto:tome...@qualisystems.com]
 Sent: 13 March 2013 13:28
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not
 supersede first Patch

 No no, you got me all wrong.
 I don't want cumulative patches! The opposite, I want the last patch that
 I install to supersede all others, overwriting the files.

 I have the MSP file and in z7 I can see that it has all the right files,
 that is the new files. But if I install it after I installed an earlier
 patch... those files don't get to the installation folder...?! I'm using:
 msiexec.exe /L*v c:\temp\log.txt /p c:\temp\patch2\patch.msp
 REINSTALL=ALL REINSTALLMODE=aumsv ADDLOCAL=ALL REBOOT=ReallySuppress the
 log of the second patch installation:
 Note: 1: 2228 2:  3: MsiAssembly 4:  SELECT `MsiAssembly`.`Attributes`,
 `MsiAssembly`.`File_Application`, `MsiAssembly`.`File_Manifest`,
 `Component`.`KeyPath` FROM `MsiAssembly`, `Component` WHERE
 `MsiAssembly`.`Component_` = `Component`.`Component` AND
 `MsiAssembly`.`Component_` = ?
 MSI (s) (48:C4) [15:13:42:791]: Patch Modified Files List:
 //it gives only a partial list of the files that are in the MSP file...
 allthose files are !NOT! .NET dlls, the .NET dlls are the files that don't
 get overwritten for some reason...

 Please help! Thanks.

 Tomer Cohen
 InSight Team Leader, RD
 QualiSystems
 Mobile: +972-52-3362846
 Email: tome...@qualisystems.com
 Web: www.qualisystems.com

 -Original Message-
 From: Brian_Covington [mailto:briancoving...@yahoo.com]
 Sent: יום ד 13 מרץ 2013 06:02
 To: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not
 supersede first Patch

 Sorry, no.  We are weeks away from having to release and the plan for now
 is to not use cumulative patches.



 
  From: Tomer Cohen [via Windows Installer XML (WiX) toolset] 
 ml-node+s687559n758426...@n2.nabble.com
 To: Brian_Covington briancoving...@yahoo.com
 Sent: Tuesday, March 12, 2013 10:11 AM
 Subject: Re: Managed Bootstrapper - Second Patch does not supersede first
 Patch


 Got anywhere with this? I have the same problem
 I don't mind having both patches appear in the add remove - updates side
 by side, but the second patch doesn't replace the files at all...
 If I install it without the first patch already installed then that patch
 works great.

 Tomer.
 Thanks.

 -Original Message-
 From: Brian_Covington [mailto:[hidden email]]
 Sent: יום ה 15 נובמבר 2012 00:41
 To: [hidden email]
 Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not
 supersede first Patch

 Same results with versions 10.00.35.0004, 10.00.36.0004 (HF1), and
 10.00.37.0004 (HF2).

 I am changing the bundle version as well as the version of the msi, but
 still the second patch for the bundle appears alongside the first one, not
 replacing it as I would expect.

 Do I need to do something to hide the first patch when the second one is
 applied?  And if so, how would I undo this when uninstalling the second
 patch?

 As these are cumulative, removable patches, only one entry must exist in
 the Installed Updates of ARP.

 I do see where it realized the first patch bundle was installed, but did
 nothing with it.

 Plan 3 packages, action: Install
 [0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on
 package with no dependency providers: Netfx4Full
 [0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on
 package with no dependency providers: S3DInstallPatch
 [0F98:0E38][2012-11-14T16:19:55]: Setting string variable
 'WixBundleLog_S3DInstallPatch' to value

 'C:\Users\sp3dtest\AppData\Local\Temp\PRODUCT_S3D_HotFix_2_20121114161952_{C1
 93CA79-FACC-4874-AF85-6CCC6B10851C}_0_S3DInstallPatch.log'
 [0F98:0E38][2012-11-14T16:19:55]: Setting string variable
 'WixBundleRollbackLog_S3DInstallPatch' to value

 'C:\Users\sp3dtest\AppData\Local\Temp\PRODUCT_S3D_HotFix_2_20121114161952_{C1
 93CA79-FACC-4874-AF85-6CCC6B10851C}_0_S3DInstallPatch_rollback.log'
 [0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on
 package with no dependency

Re: [WiX-users] setup i18n

You can put multiple .wxl Payload files in your Bundle. If you have
Payload/@Name=1041\thm.wxl then that .wxl will change the strings in your
thm.xml when the user language is set to Japanese. There is no option for a
drop down to pick today. If you want to persist the value, you could pass
the value down to the MSI via MsiProperty element.


On Fri, Mar 1, 2013 at 9:48 AM, up2date.cyb...@gmail.com 
up2date.cyb...@gmail.com wrote:

 Hi all,

 I search the web for information about it, but it's quite confusing for me.
 I currently have a bootstrapper (i'm using wix3.7), a custom
 wixstdba.dll, and one setup msi.
 My UI is displayed by the bootstrapper, nothing is displayed from the
 msi itself.

 I'd like to handle more than one languages in the UI. let's say with a
 dropdown list when installing.
 But I'd like to have only one msi, saving in the registry the selected
 language, so that the installed program exe can read it and display the
 correct language.
 I don't want to have many exe each one with one language, the same for
 msi, it would be hard to maintain and distribute.

 Can someone help me or show me the correct way to do it?
 Thanks


 --
 Everyone hates slow websites. So do we.
 Make your web apps faster with AppDynamics
 Download AppDynamics Lite for free today:
 http://p.sf.net/sfu/appdyn_d2d_feb
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Permission

Yeah, that documentation is pretty bad. Feel free to file a bug. I'm not
even sure what it is trying to say.


On Mon, Mar 4, 2013 at 6:43 AM, keith.doug...@statcan.gc.ca wrote:

 Following up on my own previous post,

 The description of Permission has this line in the documentation:

 GenericRead YesNoType   specifying this will fail to grant read
 access

 What does that description mean? The name suggests that I can grant
 GenericRead and that will grant, well, Read in the sense of the security
 tab of the properties pane on a file, but ... fail to grant?? What does
 specifying mean? What permissions do I grant to allow a group or user to
 *just* read a static configuration file? I've determined through
 experimentation that (1) below is not enough, and that (2) *is* that using
 Permission overrides everything else and that (3) yes, you can use a group,
 so I suppose I don't need that information still ...



 Keith Douglas
 Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6
 keith.doug...@statcan.gc.ca
 Telephone | Téléphone 613-951-4405
 Facsimile | Télécopieur 613-951-1966
 Government of Canada | Gouvernement du Canada


 -Original Message-
 From: Douglas, Keith - CoSD/DSCo
 Sent: March-01-13 3:40 PM
 To: General discussion for Windows Installer XML toolset.
 Subject: Permission

 (1) If I grant Read, ReadAttributes, ReadExtendedAttributes to two users
 based on a Permission element, what permissions do other users have?
 (2) Are the permissions exhaustive for those users? If not, how do I clear
 write access? Do I somehow have to use an explicit deny?
 (3) Can the User attribute be used with a local group as the value of the
 parameter instead?

 Finally, is the section in the Wix 3.5 documentation wrong on the
 difference between Permission and Util:PermissionEx? Or is the otherwise
 excellent book by Nick Ramirez wrong? The latter seems to describe
 Permission when talking about Utils:PermissionEx if the built in docs are
 to be believed.



 Keith Douglas
 Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6
 keith.doug...@statcan.gc.ca Telephone | Téléphone 613-951-4405 Facsimile
 | Télécopieur 613-951-1966 Government of Canada | Gouvernement du Canada




 --
 Everyone hates slow websites. So do we.
 Make your web apps faster with AppDynamics
 Download AppDynamics Lite for free today:
 http://p.sf.net/sfu/appdyn_d2d_feb
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] warning CNDL5153: The PerfCounter element has been deprecated

PerfCounter was deprecated a long time ago when Vista came along, I
believe. My memory may be a little fuzzy. I think it has something to do
with lodctr being no longer the recommended way to install perf counters by
MSDN.

Ultimately, if there is a problem in PerformanceCategory and friends, then
it would be great to file it and maybe you can help us fix it. No one has
been in that code for a very long time so you may know more than most do at
this point. smile/

Code is at ca\serverca\scasched\scaperf.cpp and
ca\serverca\scaexec\scaperfexec.cpp. If you'd like to help out, let's take
the conversation to wix-d...@lists.sourceforge.net

Thanks.


On Sun, Mar 3, 2013 at 12:58 PM, Mark Weaver mark.wea...@credit360.comwrote:

 I looked into fixing this warning:

 warning CNDL5153 : The PerfCounter element
 has been deprecated.  Please use the PerformanceCounter element instead.

 Can anyone shed any light on why PerfCounter is deprecated?  The trouble
 is that PerformanceCounter doesn't seem to provide a full replacement
 for what lodctr can do.  The structure I have is:

 perf collection dll
  perf object 1
  counter 1
  counter 2
  ...
  perf object 2
  counter 1
  ...
 ...


 but this doesn't map onto PerformanceCategory/PerformanceCounter.
 Specifically, PerformanceCounter/@Name ends up under
 HKLM\SYSTEM\CurrentControlSet\service\[Name], but is also the perf
 object name.  So I can't have two objects without two entries under the
 service key, and additionally the name of the service can't differ from
 the name of the object.  lodctr can also provide translations of the
 counter names, but PerformanceCounter seems to be limited to a single
 language (that's not actually a problem for me, but it seems to be
 missing from the model).

 Am I just misunderstanding how it's meant to work?

 Thanks,

 Mark


 --
 Everyone hates slow websites. So do we.
 Make your web apps faster with AppDynamics
 Download AppDynamics Lite for free today:
 http://p.sf.net/sfu/appdyn_d2d_feb
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch

Hi,
Thanks for the reply.
I have this in my log, this is the log of the second patch installation. The 
MSP itself has all assemblies, but only installs those files below.
Patch Modified Files List:
MSI (s) (C4:04) [15:51:46:984]: File = 
QualiSystems.ResourceManagement.Service.Plugin.config: Final State = Install
MSI (s) (C4:04) [15:51:46:984]: File = MRV_MCC_4640.exe: Final State = Install
MSI (s) (C4:04) [15:51:46:984]: File = MRV_MCC_4840.exe: Final State = Install
MSI (s) (C4:04) [15:51:46:984]: File = ONPATH_HorizON_0204.exe: Final State = 
Install
MSI (s) (C4:04) [15:51:46:984]: File = ONPATH_HorizON_0204_RuntimeConfig.xml: 
Final State = Install
MSI (s) (C4:04) [15:51:46:984]: File = SNMP_Manager.tslib: Final State = Install
MSI (s) (C4:04) [15:51:46:984]: File = TestShell_API.tslib: Final State = 
Install
MSI (s) (C4:04) [15:51:46:984]: File = ONPATH_HorizON_0244_RuntimeConfig.xml: 
Final State = Install
MSI (s) (C4:04) [15:51:46:984]: File = ONPATH_HorizON_0244.exe: Final State = 
Install

I'll give the AssemblyFileVersion increment a chance.
Thanks.



-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: יום ד 13 מרץ 2013 17:06
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede 
first Patch

What does the verbose log file in the patch say the action states for the 
Components that you expect to be installed? Also, look at the File install log 
lines, those usually have quite a bit information about when the file is being 
applied and whether it is being patched.


On Wed, Mar 13, 2013 at 7:19 AM, Tomer Cohen tome...@qualisystems.comwrote:

 Just to be clear, the files don't have a newer version, but they are 
 different in size and binary...

 -Original Message-
 From: David Watson [mailto:dwat...@sdl.com]
 Sent: יום ד 13 מרץ 2013 16:04
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not 
 supersede first Patch

 Did you increase the assemblyfileversion of those dlls?

 -Original Message-
 From: Tomer Cohen [mailto:tome...@qualisystems.com]
 Sent: 13 March 2013 13:28
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not 
 supersede first Patch

 No no, you got me all wrong.
 I don't want cumulative patches! The opposite, I want the last patch 
 that I install to supersede all others, overwriting the files.

 I have the MSP file and in z7 I can see that it has all the right 
 files, that is the new files. But if I install it after I installed an 
 earlier patch... those files don't get to the installation folder...?! I'm 
 using:
 msiexec.exe /L*v c:\temp\log.txt /p c:\temp\patch2\patch.msp
 REINSTALL=ALL REINSTALLMODE=aumsv ADDLOCAL=ALL REBOOT=ReallySuppress 
 the log of the second patch installation:
 Note: 1: 2228 2:  3: MsiAssembly 4:  SELECT 
 `MsiAssembly`.`Attributes`, `MsiAssembly`.`File_Application`, 
 `MsiAssembly`.`File_Manifest`, `Component`.`KeyPath` FROM 
 `MsiAssembly`, `Component` WHERE `MsiAssembly`.`Component_` = 
 `Component`.`Component` AND `MsiAssembly`.`Component_` = ?
 MSI (s) (48:C4) [15:13:42:791]: Patch Modified Files List:
 //it gives only a partial list of the files that are in the MSP file...
 allthose files are !NOT! .NET dlls, the .NET dlls are the files that 
 don't get overwritten for some reason...

 Please help! Thanks.

 Tomer Cohen
 InSight Team Leader, RD
 QualiSystems
 Mobile: +972-52-3362846
 Email: tome...@qualisystems.com
 Web: www.qualisystems.com

 -Original Message-
 From: Brian_Covington [mailto:briancoving...@yahoo.com]
 Sent: יום ד 13 מרץ 2013 06:02
 To: wix-users@lists.sourceforge.net
 Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not 
 supersede first Patch

 Sorry, no.  We are weeks away from having to release and the plan for 
 now is to not use cumulative patches.



 
  From: Tomer Cohen [via Windows Installer XML (WiX) toolset] 
 ml-node+s687559n758426...@n2.nabble.com
 To: Brian_Covington briancoving...@yahoo.com
 Sent: Tuesday, March 12, 2013 10:11 AM
 Subject: Re: Managed Bootstrapper - Second Patch does not supersede 
 first Patch


 Got anywhere with this? I have the same problem
 I don't mind having both patches appear in the add remove - updates 
 side by side, but the second patch doesn't replace the files at all...
 If I install it without the first patch already installed then that 
 patch works great.

 Tomer.
 Thanks.

 -Original Message-
 From: Brian_Covington [mailto:[hidden email]]
 Sent: יום ה 15 נובמבר 2012 00:41
 To: [hidden email]
 Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not 
 supersede first Patch

 Same results with versions 10.00.35.0004, 10.00.36.0004 (HF1), and
 10.00.37.0004 (HF2).

 I am changing the bundle version as well as the

Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch

What does the action state for the *Components* show? That's what the
Windows Installer is basing it's decision on. It would root cause the
issue. It very likely could be the version of the files not changing but it
would be best to *know* what fixed it, right?


On Wed, Mar 13, 2013 at 8:18 AM, Tomer Cohen tome...@qualisystems.comwrote:

 Hi,
 Thanks for the reply.
 I have this in my log, this is the log of the second patch installation.
 The MSP itself has all assemblies, but only installs those files below.
 Patch Modified Files List:
 MSI (s) (C4:04) [15:51:46:984]: File =
 QualiSystems.ResourceManagement.Service.Plugin.config: Final State = Install
 MSI (s) (C4:04) [15:51:46:984]: File = MRV_MCC_4640.exe: Final State =
 Install
 MSI (s) (C4:04) [15:51:46:984]: File = MRV_MCC_4840.exe: Final State =
 Install
 MSI (s) (C4:04) [15:51:46:984]: File = ONPATH_HorizON_0204.exe: Final
 State = Install
 MSI (s) (C4:04) [15:51:46:984]: File =
 ONPATH_HorizON_0204_RuntimeConfig.xml: Final State = Install
 MSI (s) (C4:04) [15:51:46:984]: File = SNMP_Manager.tslib: Final State =
 Install
 MSI (s) (C4:04) [15:51:46:984]: File = TestShell_API.tslib: Final State =
 Install
 MSI (s) (C4:04) [15:51:46:984]: File =
 ONPATH_HorizON_0244_RuntimeConfig.xml: Final State = Install
 MSI (s) (C4:04) [15:51:46:984]: File = ONPATH_HorizON_0244.exe: Final
 State = Install

 I'll give the AssemblyFileVersion increment a chance.
 Thanks.



 -Original Message-
 From: Rob Mensching [mailto:r...@robmensching.com]
 Sent: יום ד 13 מרץ 2013 17:06
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not
 supersede first Patch

 What does the verbose log file in the patch say the action states for the
 Components that you expect to be installed? Also, look at the File install
 log lines, those usually have quite a bit information about when the file
 is being applied and whether it is being patched.


 On Wed, Mar 13, 2013 at 7:19 AM, Tomer Cohen tome...@qualisystems.com
 wrote:

  Just to be clear, the files don't have a newer version, but they are
  different in size and binary...
 
  -Original Message-
  From: David Watson [mailto:dwat...@sdl.com]
  Sent: יום ד 13 מרץ 2013 16:04
  To: General discussion for Windows Installer XML toolset.
  Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not
  supersede first Patch
 
  Did you increase the assemblyfileversion of those dlls?
 
  -Original Message-
  From: Tomer Cohen [mailto:tome...@qualisystems.com]
  Sent: 13 March 2013 13:28
  To: General discussion for Windows Installer XML toolset.
  Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not
  supersede first Patch
 
  No no, you got me all wrong.
  I don't want cumulative patches! The opposite, I want the last patch
  that I install to supersede all others, overwriting the files.
 
  I have the MSP file and in z7 I can see that it has all the right
  files, that is the new files. But if I install it after I installed an
  earlier patch... those files don't get to the installation folder...?!
 I'm using:
  msiexec.exe /L*v c:\temp\log.txt /p c:\temp\patch2\patch.msp
  REINSTALL=ALL REINSTALLMODE=aumsv ADDLOCAL=ALL REBOOT=ReallySuppress
  the log of the second patch installation:
  Note: 1: 2228 2:  3: MsiAssembly 4:  SELECT
  `MsiAssembly`.`Attributes`, `MsiAssembly`.`File_Application`,
  `MsiAssembly`.`File_Manifest`, `Component`.`KeyPath` FROM
  `MsiAssembly`, `Component` WHERE `MsiAssembly`.`Component_` =
  `Component`.`Component` AND `MsiAssembly`.`Component_` = ?
  MSI (s) (48:C4) [15:13:42:791]: Patch Modified Files List:
  //it gives only a partial list of the files that are in the MSP file...
  allthose files are !NOT! .NET dlls, the .NET dlls are the files that
  don't get overwritten for some reason...
 
  Please help! Thanks.
 
  Tomer Cohen
  InSight Team Leader, RD
  QualiSystems
  Mobile: +972-52-3362846
  Email: tome...@qualisystems.com
  Web: www.qualisystems.com
 
  -Original Message-
  From: Brian_Covington [mailto:briancoving...@yahoo.com]
  Sent: יום ד 13 מרץ 2013 06:02
  To: wix-users@lists.sourceforge.net
  Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not
  supersede first Patch
 
  Sorry, no.  We are weeks away from having to release and the plan for
  now is to not use cumulative patches.
 
 
 
  
   From: Tomer Cohen [via Windows Installer XML (WiX) toolset] 
  ml-node+s687559n758426...@n2.nabble.com
  To: Brian_Covington briancoving...@yahoo.com
  Sent: Tuesday, March 12, 2013 10:11 AM
  Subject: Re: Managed Bootstrapper - Second Patch does not supersede
  first Patch
 
 
  Got anywhere with this? I have the same problem
  I don't mind having both patches appear in the add remove - updates
  side by side, but the second patch doesn't replace the files at all...
  If I install it without the first patch already

Re: [WiX-users] Does anyone have a VSIX example

2013-03-13 Thread Thomas

Hi,

I'm also having some issue with this with VsixPackage. I can build the
installer fine but when it runs I get an error.

I have installed latest Wix. Does this wxs look ok?

?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:VSExtension=http://schemas.microsoft.com/wix/VSExtension;
Product Id=* Name=TemplateInstaller Language=1033
Version=1.0.0.0 Manufacturer=ThomasSoft
UpgradeCode=52cf0ec5-a9cb-4617-8f69-ef45f389d965
Package InstallerVersion=200 Compressed=yes
InstallScope=perMachine /

MajorUpgrade DowngradeErrorMessage=A newer version of
[ProductName] is already installed. /
MediaTemplate EmbedCab=yes /

Feature Id=ProductFeature Title=TemplateInstaller Level=1
ComponentGroupRef Id=ProductComponents /
/Feature
/Product

Fragment
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ProgramFilesFolder
Directory Id=INSTALLFOLDER Name=TemplateInstaller /
/Directory
/Directory
/Fragment

Fragment
ComponentGroup Id=ProductComponents Directory=INSTALLFOLDER
Component Id=ProductComponent
VSExtension:VsixPackage File=MyVSIX_ID
PackageId=MyVSIX..2df7ae50-f029-40a6-af69-49aa4a76e3f5
Target=professional TargetVersion=11.0 Vital=yes Permanent=yes/
File Id=MyVSIX_ID Name=MyVSIX.vsix
Source=..\MyVSIX\bin\Debug\MyVSIX.vsix/
/Component
/ComponentGroup
/Fragment
/Wix

I get a generic error saying There is a problem with this Windows Installer
package. A program run as part of the setup did not finish as expected.
Contact your support personnel or package vendor

If I only run the vsix like this:
C:\Program Files (x86)\Microsoft Visual Studio
11.0\Common7\IDE\VSIXInstaller.exe /q /skuName:Pro /skuVersion:11.0 /admin
C:\Dev\Temp\MyVSIX.vsix

it works.

I have built my vsix with VS2012 SDK and tried with the option The VSIX is
installed by Windows Installer both enabled and not. 


please advice :)

Thanks,
//Thomas



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Does-anyone-have-a-VSIX-example-tp7580711p7584296.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Does anyone have a VSIX example

That error means the VsixInstaller failed. Doesn't the VsixInstaller create
a log file somewhere? That's your best bet.

On Wed, Mar 13, 2013 at 8:25 AM, Thomas thomas.wu...@hotmail.com wrote:

Hi,

I'm also having some issue with this with VsixPackage. I can build the
installer fine but when it runs I get an error.

I have installed latest Wix. Does this wxs look ok?

?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:VSExtension=http://schemas.microsoft.com/wix/VSExtension;
Product Id=* Name=TemplateInstaller Language=1033
Version=1.0.0.0 Manufacturer=ThomasSoft
UpgradeCode=52cf0ec5-a9cb-4617-8f69-ef45f389d965
Package InstallerVersion=200 Compressed=yes
InstallScope=perMachine /

MajorUpgrade DowngradeErrorMessage=A newer version of
[ProductName] is already installed. /
MediaTemplate EmbedCab=yes /

Feature Id=ProductFeature Title=TemplateInstaller Level=1
ComponentGroupRef Id=ProductComponents /
/Feature
/Product

Fragment
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ProgramFilesFolder
Directory Id=INSTALLFOLDER Name=TemplateInstaller /
/Directory
/Directory
/Fragment

Fragment
ComponentGroup Id=ProductComponents Directory=INSTALLFOLDER
Component Id=ProductComponent
VSExtension:VsixPackage File=MyVSIX_ID
PackageId=MyVSIX..2df7ae50-f029-40a6-af69-49aa4a76e3f5
Target=professional TargetVersion=11.0 Vital=yes Permanent=yes/
File Id=MyVSIX_ID Name=MyVSIX.vsix
Source=..\MyVSIX\bin\Debug\MyVSIX.vsix/
/Component
/ComponentGroup
/Fragment
/Wix

I get a generic error saying There is a problem with this Windows
Installer
package. A program run as part of the setup did not finish as expected.
Contact your support personnel or package vendor

If I only run the vsix like this:
C:\Program Files (x86)\Microsoft Visual Studio
11.0\Common7\IDE\VSIXInstaller.exe /q /skuName:Pro /skuVersion:11.0 /admin
C:\Dev\Temp\MyVSIX.vsix

it works.

I have built my vsix with VS2012 SDK and tried with the option The VSIX is
installed by Windows Installer both enabled and not.

please advice :)

Thanks,
//Thomas

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Does-anyone-have-a-VSIX-example-tp7580711p7584296.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Project with merge modules defeating incremental build facility

What more information would you like about the feature? Also, why would
you want to turn it off? Other projects types do not let you turn off their
incremental build facility. What could have been done better (other than
just have it auotmatically work, which was the intent smile/)?

Very possibly. Sounds like Merge Modules may not be handled correctly by
the incremental build change. Want to help us fix the root issue? If so,
love to start a discussion on wix-d...@lists.sourceforge.net about the best
way to fix the targets to correctly handle the situation.

On Tue, Mar 12, 2013 at 4:25 PM, Rennie Petersen r...@merlinia.com wrote:

This was not a problem in WiX 3.5, but apparently as part of 3.6 support
was
added to the MSBuild targets for incremental builds by testing the
timestamps on all input files to the link task to see if they were newer
than the output files. I haven't been able to find any documentation - Bob
Arnson mentions it at the end of this thread in May 2011,

http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Developer-with-WiX-experience-needed-proper-incremental-build-support-td6380785.html#a6383958

and it's mentioned with a single line in the 3.6 release notes, .wixproj
MSBuild projects support incremental build.

http://wix.codeplex.com/releases/view/93929

This is a nice facility, although it would have been even nicer with more
information and maybe an option to turn it off.

Anyway, my problem with it is that when I have the C++ runtime merge module
in my project this forces a link to be done every time, even if no input is
changed. As far as I can determine the processing of the merge module
involves the creation of three temporary files:

C:\Users\rp\AppData\Local\Temp\4q3ufw1n\MergeId.49012\F_CENTRAL_msvcp110_x86.D371D00B_69EC_3F8E_A622_74710A89ADC1

C:\Users\rp\AppData\Local\Temp\4q3ufw1n\MergeId.49012\F_CENTRAL_msvcr110_x86.D371D00B_69EC_3F8E_A622_74710A89ADC1

C:\Users\rp\AppData\Local\Temp\4q3ufw1n\MergeId.49012\F_CENTRAL_vccorlib110_x86.D371D00B_69EC_3F8E_A622_74710A89ADC1

I've extracted these filenames from the BindContentsFileList file, and I
see
them in the MSBuild log. I've never actually seen these files themselves
with my own eyes - they are apparently created, consumed, and then deleted
so quickly that human reflexes can't cope. But my guess is that they have a
timestamp of now, instead of being given a timestamp corresponding to the
merge module, and this sabotages the incremental build testing. Which in
turn sabotages all of the following incremental builds in the overall
project.

For now I've modified the WiX target so the link task no longer includes
_BindInputs as part of its Inputs= list.

Have I understood the situation correctly?

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Project-with-merge-modules-defeating-incremental-build-facility-tp7584279.html
Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] Using Update Element of the Bundle?

In WiX v3.7 (and maybe all of WiX v3.7+) the Update/@Location really is
just information provided to the BootstrapperApplication. Basically if you
have an update location, the engine will say, Hey, BA, now would be a good
time to use this string and figure out if there is an update.  Technically
speaking, you don't even need to use update location to look updates (WiX
v3.6 did updates without the feature existing) but now you get a pretty
good hint when to go do the search.

After that, I created the application syndication idea a long time ago,
using ATOM/RSS to track updates. It was trendy back then and I'm trying to
decide how much to push it going forward. I have a small spec kicking
around here somewhere for the implementation that is in the WiX toolset and
there is helper code in src\dutil\apup.cpp. I'm now wondering if the
web-world has moved far enough to JSON if I should pull the important
information into there... however, IE renders ATOM really nicely, ala:
http://wixtoolset.org/releases/feed/v3.8


On Tue, Mar 12, 2013 at 1:31 PM, Wheeler, Blaine (DSHS/DCS) 
bwhee...@dshs.wa.gov wrote:

 I want to create a self updating setup.exe with Burn. I hope that using
 the Update element of the Bundle with Wix 3.7 will work.  The Help says
 this piece wasn't working yet but it looks like you use it for Wix updates.
  True?


 Is there a reason you use a feed or was it just convenience?

 My plan:
 Set up a folder and file tree off a web server. From the Wix 3.7 source it
 looks like the UpdateURL attribute of the Bundle element in the refers to
 the root URL  where all subsequent updates of this version of product will
 be.  For example: http://ourhouse/releases/myAppName.   Or Is Update
 Location='' / the critical element?  Or are both necessary?

 For each update we would add a folder under MyAppName with a unique ID
 such as the setup.exe version number (1.0.0.0,  1.0.0.1 etc)

 If we have 4 packages per setup.exe would each sub folder have to all of
 the packages referenced by the bundle?

 I'm open to other ideas and I'd be happy to contribute code back or to the
 Help if I am on a useful track?


 Blaine Wheeler
 Department of Social and Health Services
 Project Coordinator
 SEMS Operations
 360.664.5416
 blaine.whee...@dshs.wa.gov



 --
 Everyone hates slow websites. So do we.
 Make your web apps faster with AppDynamics
 Download AppDynamics Lite for free today:
 http://p.sf.net/sfu/appdyn_d2d_mar
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Does anyone have a VSIX example

2013-03-13 Thread John Ludlow

See this:

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

Apparently it's a bad idea to run VSIXInstaller from an MSI.

On 13 March 2013 15:31, Rob Mensching r...@robmensching.com wrote:
That error means the VsixInstaller failed. Doesn't the VsixInstaller create
a log file somewhere? That's your best bet.

On Wed, Mar 13, 2013 at 8:25 AM, Thomas thomas.wu...@hotmail.com wrote:

Hi,

I'm also having some issue with this with VsixPackage. I can build the
installer fine but when it runs I get an error.

I have installed latest Wix. Does this wxs look ok?

MajorUpgrade DowngradeErrorMessage=A newer version of
[ProductName] is already installed. /
MediaTemplate EmbedCab=yes /

Feature Id=ProductFeature Title=TemplateInstaller Level=1
ComponentGroupRef Id=ProductComponents /
/Feature
/Product

Fragment
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ProgramFilesFolder
Directory Id=INSTALLFOLDER Name=TemplateInstaller /
/Directory
/Directory
/Fragment

I get a generic error saying There is a problem with this Windows
Installer
package. A program run as part of the setup did not finish as expected.
Contact your support personnel or package vendor

If I only run the vsix like this:
C:\Program Files (x86)\Microsoft Visual Studio
11.0\Common7\IDE\VSIXInstaller.exe /q /skuName:Pro /skuVersion:11.0 /admin
C:\Dev\Temp\MyVSIX.vsix

it works.

I have built my vsix with VS2012 SDK and tried with the option The VSIX is
installed by Windows Installer both enabled and not.

please advice :)

Thanks,
//Thomas

Re: [WiX-users] Project with merge modules defeating incremental build facility

2013-03-13 Thread Rennie Petersen

Hi Rob, and thanks for your reply.


robmen wrote
 Want to help us fix the root issue? If so, love to start a discussion on 

 wix-devs@.sourceforge

  about the best way to fix the targets to correctly handle the situation.

First off, I tried answering via the [hidden email] link, but then I get a
Nabble error Domain starts with dot. Please fix the error and try again.
Which I don't understand at all.

About the problem ...

Is it a part of WiX that creates (and later deletes) those three temporary
files? If so, am I correct in suspecting that the files are created without
fixing their timestamp after creation? 

If so, then the fix should be simple: set the timestamp of those three files
to match the timestamp on the merge module file. Then the three temporary
files will not trigger a re-link in most cases, but if the merge module is
updated then they will trigger a re-link. Case solved!

Yours,
Rennie



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Project-with-merge-modules-defeating-incremental-build-facility-tp7584279p7584302.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Does anyone have a VSIX example

2013-03-13 Thread David Watson

I had problems with installing VSIX from msi too and eventually read that you
should install 'by hand' if you are using MSI.
There is some very helpful code in the wix installer itself to help you with
registrations etc.

-Original Message-
From: John Ludlow [mailto:john.ludlow...@gmail.com] 
Sent: 13 March 2013 15:55
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Does anyone have a VSIX example

See this:

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

Apparently it's a bad idea to run VSIXInstaller from an MSI.

On 13 March 2013 15:31, Rob Mensching r...@robmensching.com wrote:
 That error means the VsixInstaller failed. Doesn't the VsixInstaller 
 create a log file somewhere? That's your best bet.

 On Wed, Mar 13, 2013 at 8:25 AM, Thomas thomas.wu...@hotmail.com wrote:

 Hi,

 I'm also having some issue with this with VsixPackage. I can build 
 the installer fine but when it runs I get an error.

 I have installed latest Wix. Does this wxs look ok?

 ?xml version=1.0 encoding=UTF-8? Wix 
 xmlns=http://schemas.microsoft.com/wix/2006/wi;
 xmlns:VSExtension=http://schemas.microsoft.com/wix/VSExtension;
 Product Id=* Name=TemplateInstaller Language=1033
 Version=1.0.0.0 Manufacturer=ThomasSoft
 UpgradeCode=52cf0ec5-a9cb-4617-8f69-ef45f389d965
 Package InstallerVersion=200 Compressed=yes
 InstallScope=perMachine /

 MajorUpgrade DowngradeErrorMessage=A newer version of 
 [ProductName] is already installed. /
 MediaTemplate EmbedCab=yes /

 Feature Id=ProductFeature Title=TemplateInstaller Level=1
 ComponentGroupRef Id=ProductComponents /
 /Feature
 /Product

 Fragment
 Directory Id=TARGETDIR Name=SourceDir
 Directory Id=ProgramFilesFolder
 Directory Id=INSTALLFOLDER Name=TemplateInstaller /
 /Directory
 /Directory
 /Fragment

 Fragment
 ComponentGroup Id=ProductComponents Directory=INSTALLFOLDER
 Component Id=ProductComponent
 VSExtension:VsixPackage File=MyVSIX_ID
 PackageId=MyVSIX..2df7ae50-f029-40a6-af69-49aa4a76e3f5
 Target=professional TargetVersion=11.0 Vital=yes Permanent=yes/
 File Id=MyVSIX_ID Name=MyVSIX.vsix
 Source=..\MyVSIX\bin\Debug\MyVSIX.vsix/
 /Component
 /ComponentGroup
 /Fragment
 /Wix

 I get a generic error saying There is a problem with this Windows 
 Installer package. A program run as part of the setup did not finish 
 as expected.
 Contact your support personnel or package vendor

 If I only run the vsix like this:
 C:\Program Files (x86)\Microsoft Visual Studio 
 11.0\Common7\IDE\VSIXInstaller.exe /q /skuName:Pro /skuVersion:11.0 
 /admin C:\Dev\Temp\MyVSIX.vsix

 it works.

 I have built my vsix with VS2012 SDK and tried with the option The 
 VSIX is installed by Windows Installer both enabled and not.

 please advice :)

 Thanks,
 //Thomas

 --
 View this message in context:
 http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Does-an
 yone-have-a-VSIX-example-tp7580711p7584296.html
 Sent from the wix-users mailing list archive at Nabble.com.

 -
 - Everyone hates slow websites. So do we.
 Make your web apps faster with AppDynamics Download AppDynamics Lite 
 for free today:
 http://p.sf.net/sfu/appdyn_d2d_mar
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

 --
  Everyone hates slow websites. So do we.
 Make your web apps faster with AppDynamics Download AppDynamics Lite 
 for free today:
 http://p.sf.net/sfu/appdyn_d2d_mar
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

-
-
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics Download AppDynamics Lite for free
today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
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.

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics

Re: [WiX-users] Project with merge modules defeating incremental build facility

I don't use Nabble. I join via here:
http://wix.sourceforge.net/mailinglists.html. I know that works. smile/

This conversation is better for wix-devs, short answer: no WiX does not
create those files. The mergemod.dll from the MSI SDK creates those files
so we're going to have to be more creative with them.

On Wed, Mar 13, 2013 at 8:56 AM, Rennie Petersen r...@merlinia.com wrote:

Hi Rob, and thanks for your reply.

robmen wrote
Want to help us fix the root issue? If so, love to start a discussion on

wix-devs@.sourceforge

about the best way to fix the targets to correctly handle the situation.

First off, I tried answering via the [hidden email] link, but then I get a
Nabble error Domain starts with dot. Please fix the error and try again.
Which I don't understand at all.

About the problem ...

Is it a part of WiX that creates (and later deletes) those three temporary
files? If so, am I correct in suspecting that the files are created without
fixing their timestamp after creation?

If so, then the fix should be simple: set the timestamp of those three
files
to match the timestamp on the merge module file. Then the three temporary
files will not trigger a re-link in most cases, but if the merge module is
updated then they will trigger a re-link. Case solved!

Yours,
Rennie

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Project-with-merge-modules-defeating-incremental-build-facility-tp7584279p7584302.html
Sent from the wix-users mailing list archive at Nabble.com.

[WiX-users] Platform-specific references (difxapp_x64 etc.)

2013-03-13 Thread Bruce Cran

Does the Visual Studio plugin for WiX 3.7 have logic for selecting the 
correct platform-specific reference when building both 32-bit and 64-bit 
configurations so workarounds like 
http://stackoverflow.com/questions/8713683/installing-32-64-bit-drivers-with-wix
 
are unnecessary now?

For example I have to choose to reference either difxapp_x86 _or_ 
difxapp_x64, but building a 32-bit msi with difxapp_x64 referenced seems 
to work.

-- 
Bruce Cran

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch

2013-03-13 Thread Phil Wilson

...and to exapand on that, look for your files in the log. There should be a
FileCopy that will say something like  Won't Overwrite;Won't patch;
 and give you a reason. 

If your patch is incorrect because of component rules, look for SELMGR in
the log and any remarks about removing components not supported. 


Phil  

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: Wednesday, March 13, 2013 8:24 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not
supersede first Patch

What does the action state for the *Components* show? That's what the
Windows Installer is basing it's decision on. It would root cause the issue.
It very likely could be the version of the files not changing but it would
be best to *know* what fixed it, right?


On Wed, Mar 13, 2013 at 8:18 AM, Tomer Cohen
tome...@qualisystems.comwrote:

 Hi,
 Thanks for the reply.
 I have this in my log, this is the log of the second patch installation.
 The MSP itself has all assemblies, but only installs those files below.
 Patch Modified Files List:
 MSI (s) (C4:04) [15:51:46:984]: File =
 QualiSystems.ResourceManagement.Service.Plugin.config: Final State = 
 Install MSI (s) (C4:04) [15:51:46:984]: File = MRV_MCC_4640.exe: Final 
 State = Install MSI (s) (C4:04) [15:51:46:984]: File = 
 MRV_MCC_4840.exe: Final State = Install MSI (s) (C4:04) 
 [15:51:46:984]: File = ONPATH_HorizON_0204.exe: Final State = Install 
 MSI (s) (C4:04) [15:51:46:984]: File =
 ONPATH_HorizON_0204_RuntimeConfig.xml: Final State = Install MSI (s) 
 (C4:04) [15:51:46:984]: File = SNMP_Manager.tslib: Final State = 
 Install MSI (s) (C4:04) [15:51:46:984]: File = TestShell_API.tslib: 
 Final State = Install MSI (s) (C4:04) [15:51:46:984]: File =
 ONPATH_HorizON_0244_RuntimeConfig.xml: Final State = Install MSI (s) 
 (C4:04) [15:51:46:984]: File = ONPATH_HorizON_0244.exe: Final State = 
 Install

 I'll give the AssemblyFileVersion increment a chance.
 Thanks.



 -Original Message-
 From: Rob Mensching [mailto:r...@robmensching.com]
 Sent: יום ד 13 מרץ 2013 17:06
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not 
 supersede first Patch

 What does the verbose log file in the patch say the action states for 
 the Components that you expect to be installed? Also, look at the File 
 install log lines, those usually have quite a bit information about 
 when the file is being applied and whether it is being patched.


 On Wed, Mar 13, 2013 at 7:19 AM, Tomer Cohen tome...@qualisystems.com
 wrote:

  Just to be clear, the files don't have a newer version, but they are 
  different in size and binary...
 
  -Original Message-
  From: David Watson [mailto:dwat...@sdl.com]
  Sent: יום ד 13 מרץ 2013 16:04
  To: General discussion for Windows Installer XML toolset.
  Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does 
  not supersede first Patch
 
  Did you increase the assemblyfileversion of those dlls?
 
  -Original Message-
  From: Tomer Cohen [mailto:tome...@qualisystems.com]
  Sent: 13 March 2013 13:28
  To: General discussion for Windows Installer XML toolset.
  Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does 
  not supersede first Patch
 
  No no, you got me all wrong.
  I don't want cumulative patches! The opposite, I want the last patch 
  that I install to supersede all others, overwriting the files.
 
  I have the MSP file and in z7 I can see that it has all the right
  files, that is the new files. But if I install it after I installed 
  an earlier patch... those files don't get to the installation
folder...?!
 I'm using:
  msiexec.exe /L*v c:\temp\log.txt /p c:\temp\patch2\patch.msp
  REINSTALL=ALL REINSTALLMODE=aumsv ADDLOCAL=ALL REBOOT=ReallySuppress 
  the log of the second patch installation:
  Note: 1: 2228 2:  3: MsiAssembly 4:  SELECT 
  `MsiAssembly`.`Attributes`, `MsiAssembly`.`File_Application`, 
  `MsiAssembly`.`File_Manifest`, `Component`.`KeyPath` FROM 
  `MsiAssembly`, `Component` WHERE `MsiAssembly`.`Component_` = 
  `Component`.`Component` AND `MsiAssembly`.`Component_` = ?
  MSI (s) (48:C4) [15:13:42:791]: Patch Modified Files List:
  //it gives only a partial list of the files that are in the MSP file...
  allthose files are !NOT! .NET dlls, the .NET dlls are the files that 
  don't get overwritten for some reason...
 
  Please help! Thanks.
 
  Tomer Cohen
  InSight Team Leader, RD
  QualiSystems
  Mobile: +972-52-3362846
  Email: tome...@qualisystems.com
  Web: www.qualisystems.com
 
  -Original Message-
  From: Brian_Covington [mailto:briancoving...@yahoo.com]
  Sent: יום ד 13 מרץ 2013 06:02
  To: wix-users@lists.sourceforge.net
  Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does 
  not supersede first Patch
 
  Sorry, no.  We are weeks away from having to release and the plan

Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch

2013-03-13 Thread Phil Wilson

WiX doesn't make a habit of documenting (duplicating) Windows Installer
docs. These are the update rules for versioned files:

http://msdn.microsoft.com/en-us/library/windows/desktop/aa367835(v=vs.85).as
px

And you are probably confusing AssemblyVersion that's used for client
binding with AssemblyFileVersion, which isn't (because file version isn't
one the namimg attributes of an assembly).  

Phil  

-Original Message-
From: Tomer Cohen [mailto:tome...@qualisystems.com] 
Sent: Wednesday, March 13, 2013 7:18 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not
supersede first Patch

No... there is nothing in the documentation about that...
Won't it make the .NET stop working, the assemblies are signed... if some
are not in the same version, it won't find them...

Thanks for the fast reply. :)



-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: יום ד 13 מרץ 2013 16:04
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not
supersede first Patch

Did you increase the assemblyfileversion of those dlls?

-Original Message-
From: Tomer Cohen [mailto:tome...@qualisystems.com]
Sent: 13 March 2013 13:28
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not
supersede first Patch

No no, you got me all wrong.
I don't want cumulative patches! The opposite, I want the last patch that I
install to supersede all others, overwriting the files.

I have the MSP file and in z7 I can see that it has all the right files,
that is the new files. But if I install it after I installed an earlier
patch... those files don't get to the installation folder...?! I'm using: 
msiexec.exe /L*v c:\temp\log.txt /p c:\temp\patch2\patch.msp REINSTALL=ALL
REINSTALLMODE=aumsv ADDLOCAL=ALL REBOOT=ReallySuppress the log of the second
patch installation:
Note: 1: 2228 2:  3: MsiAssembly 4:  SELECT `MsiAssembly`.`Attributes`,
`MsiAssembly`.`File_Application`, `MsiAssembly`.`File_Manifest`,
`Component`.`KeyPath` FROM `MsiAssembly`, `Component` WHERE
`MsiAssembly`.`Component_` = `Component`.`Component` AND
`MsiAssembly`.`Component_` = ? 
MSI (s) (48:C4) [15:13:42:791]: Patch Modified Files List:
//it gives only a partial list of the files that are in the MSP file...
allthose files are !NOT! .NET dlls, the .NET dlls are the files that don't
get overwritten for some reason...

Please help! Thanks.

Tomer Cohen
InSight Team Leader, RD
QualiSystems
Mobile: +972-52-3362846
Email: tome...@qualisystems.com
Web: www.qualisystems.com

-Original Message-
From: Brian_Covington [mailto:briancoving...@yahoo.com]
Sent: יום ד 13 מרץ 2013 06:02
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not
supersede first Patch

Sorry, no.  We are weeks away from having to release and the plan for now is
to not use cumulative patches.

 


 From: Tomer Cohen [via Windows Installer XML (WiX) toolset]
ml-node+s687559n758426...@n2.nabble.com
To: Brian_Covington briancoving...@yahoo.com
Sent: Tuesday, March 12, 2013 10:11 AM
Subject: Re: Managed Bootstrapper - Second Patch does not supersede first
Patch
  

Got anywhere with this? I have the same problem 
I don't mind having both patches appear in the add remove - updates side by
side, but the second patch doesn't replace the files at all... 
If I install it without the first patch already installed then that patch
works great. 

Tomer. 
Thanks. 

-Original Message-
From: Brian_Covington [mailto:[hidden email]]
Sent: יום ה 15 נובמבר 2012 00:41
To: [hidden email]
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not
supersede first Patch 

Same results with versions 10.00.35.0004, 10.00.36.0004 (HF1), and
10.00.37.0004 (HF2). 

I am changing the bundle version as well as the version of the msi, but
still the second patch for the bundle appears alongside the first one, not
replacing it as I would expect. 

Do I need to do something to hide the first patch when the second one is
applied?  And if so, how would I undo this when uninstalling the second
patch? 

As these are cumulative, removable patches, only one entry must exist in the
Installed Updates of ARP. 

I do see where it realized the first patch bundle was installed, but did
nothing with it. 

Plan 3 packages, action: Install
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on
package with no dependency providers: Netfx4Full
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on
package with no dependency providers: S3DInstallPatch
[0F98:0E38][2012-11-14T16:19:55]: Setting string variable
'WixBundleLog_S3DInstallPatch' to value
'C:\Users\sp3dtest\AppData\Local\Temp\PRODUCT_S3D_HotFix_2_20121114161952_{C
1

[WiX-users] Can Wix Boostrapper project be a VS Startup project?

I have a solution with a Wix Boostrapper project, and several other c++/c# 
projects.  The Boostrapper project, the project that creates the EXE file, 
cannot be set to be the startup project.   Although the solution compiles and a 
setup.exe gets build, nothing happens when I run the setup.exe.  If I try to 
run from VS, it says that my startup project is a DLL.

Is it possible to make the Boostrapper project the startup project?  Or is 
there some other way to build?

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] issue with fragments in the same project

2013-03-13 Thread Sean Farrow

Hi:
This is sorted, I had a stray fragment at the bottom, and didn't see it!
Sean.

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: 13 March 2013 15:08
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] issue with fragments in the same project

If the Feature is under the Product element somewhere then I'm at a loss as
to what is actually going wrong. It seems like everything should work. What
is the exact command-line and output you are getting from the tools?

On Wed, Mar 13, 2013 at 1:46 AM, Sean Farrow
sean.far...@seanfarrow.co.ukwrote:

 Hi,

 I't's in the featue, as follows:
 Feature Id=ProductFeature Title=ConnectorMsi Level=1
   ComponentRef Id=Salamander.Host.exe/
 /Feature
 Cheers
 Sean.

 -Original Message-
 From: Rob Mensching [mailto:r...@robmensching.com]
 Sent: 13 March 2013 05:37
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] issue with fragments in the same project

 Where is the ComponentRef to Salamander.Host.exeFile?

 On Tue, Mar 12, 2013 at 5:31 PM, Sean Farrow
 sean.far...@seanfarrow.co.ukwrote:

  Hi,

  I'm currently creating an installer.
  In one file I have my folder structure:
  Fragment
  Directory Id=TARGETDIR Name=SourceDir 
Directory Id=ProgramFilesFolder 
  Directory Id=CONPANYFOLDER Name=SalamanderSoft
Directory Id=INSTALLFOLDER Name=Connector

/Directory
  /Directory
  /Directory
  /Directory
/Fragment
  in another file in the same project I have fragments with components
  defined.I've tried to refer to the INSTALLFOLDER element with both the
  directory/DirectoryRef element but understandably get a lght0091/92. My
  second file is as follows:
  Fragment
  !--Salamander host executable.--
  DirectoryRef Id=INSTALLFOLDER 
  Component Id=Salamander.Host.exe
  Guid=d535001e-c4cb-4043-9e4b-1abdec33d0f2
File Id=Salamander.Host.exeFile
  Source=..\..\..\bin\obfuscated\Salamander.Host.exe KeyPath=yes
  Checksum=yes/
  /Component
  /DirectoryRef
/FragmentI understand why this is happening, but what is the best
  way around this?
  Any help appreciated.
  Regards
  Sean.

 --
  Everyone hates slow websites. So do we.
  Make your web apps faster with AppDynamics
  Download AppDynamics Lite for free today:
  http://p.sf.net/sfu/appdyn_d2d_mar
  ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users

 --
 Everyone hates slow websites. So do we.
 Make your web apps faster with AppDynamics
 Download AppDynamics Lite for free today:
 http://p.sf.net/sfu/appdyn_d2d_mar
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

 --
 Everyone hates slow websites. So do we.
 Make your web apps faster with AppDynamics
 Download AppDynamics Lite for free today:
 http://p.sf.net/sfu/appdyn_d2d_mar
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Using Update Element of the Bundle?

2013-03-13 Thread Wheeler, Blaine (DSHS/DCS)

So I did you get the Wix3.6 bundle to know 3.7 exists and to fetch and execute 
it?
Is it going to be code in the BA?  A property I can detect?

It seems like it will work to always execute a setup.exe from the same URL and 
just keep replacing it with an updated version that gets the latest stuff.  I 
wonder what pitfall I'm not spotting?

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: Wednesday, March 13, 2013 8:40 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Using Update Element of the Bundle?

In WiX v3.7 (and maybe all of WiX v3.7+) the Update/@Location really is
just information provided to the BootstrapperApplication. Basically if you
have an update location, the engine will say, Hey, BA, now would be a good
time to use this string and figure out if there is an update.  Technically
speaking, you don't even need to use update location to look updates (WiX
v3.6 did updates without the feature existing) but now you get a pretty
good hint when to go do the search.

After that, I created the application syndication idea a long time ago,
using ATOM/RSS to track updates. It was trendy back then and I'm trying to
decide how much to push it going forward. I have a small spec kicking
around here somewhere for the implementation that is in the WiX toolset and
there is helper code in src\dutil\apup.cpp. I'm now wondering if the
web-world has moved far enough to JSON if I should pull the important
information into there... however, IE renders ATOM really nicely, ala:
http://wixtoolset.org/releases/feed/v3.8


On Tue, Mar 12, 2013 at 1:31 PM, Wheeler, Blaine (DSHS/DCS) 
bwhee...@dshs.wa.gov wrote:

 I want to create a self updating setup.exe with Burn. I hope that using
 the Update element of the Bundle with Wix 3.7 will work.  The Help says
 this piece wasn't working yet but it looks like you use it for Wix updates.
  True?


 Is there a reason you use a feed or was it just convenience?

 My plan:
 Set up a folder and file tree off a web server. From the Wix 3.7 source it
 looks like the UpdateURL attribute of the Bundle element in the refers to
 the root URL  where all subsequent updates of this version of product will
 be.  For example: http://ourhouse/releases/myAppName.   Or Is Update
 Location='' / the critical element?  Or are both necessary?

 For each update we would add a folder under MyAppName with a unique ID
 such as the setup.exe version number (1.0.0.0,  1.0.0.1 etc)

 If we have 4 packages per setup.exe would each sub folder have to all of
 the packages referenced by the bundle?

 I'm open to other ideas and I'd be happy to contribute code back or to the
 Help if I am on a useful track?


 Blaine Wheeler
 Department of Social and Health Services
 Project Coordinator
 SEMS Operations
 360.664.5416
 blaine.whee...@dshs.wa.gov



 --
 Everyone hates slow websites. So do we.
 Make your web apps faster with AppDynamics
 Download AppDynamics Lite for free today:
 http://p.sf.net/sfu/appdyn_d2d_mar
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Using Update Element of the Bundle?

2013-03-13 Thread Neil Sleightholm

I implemented auto update in the extended BA (http://wixextba.codeplex.com/) I 
am not sure it is the best way to do it but it works. Check out the discussion 
on the site for information on how to use it. There was also a recent discuss 
on wix-devs about it.

On Tue, Mar 12, 2013 at 1:31 PM, Wheeler, Blaine (DSHS/DCS)  
bwhee...@dshs.wa.gov wrote:

 I want to create a self updating setup.exe with Burn. I hope that 
 using the Update element of the Bundle with Wix 3.7 will work.  The 
 Help says this piece wasn't working yet but it looks like you use it for Wix 
 updates.
  True?


 Is there a reason you use a feed or was it just convenience?

 My plan:
 Set up a folder and file tree off a web server. From the Wix 3.7 
 source it looks like the UpdateURL attribute of the Bundle element in 
 the refers to the root URL  where all subsequent updates of this version of 
 product will
 be.  For example: http://ourhouse/releases/myAppName.   Or Is Update
 Location='' / the critical element?  Or are both necessary?

 For each update we would add a folder under MyAppName with a unique ID 
 such as the setup.exe version number (1.0.0.0,  1.0.0.1 etc)

 If we have 4 packages per setup.exe would each sub folder have to all 
 of the packages referenced by the bundle?

 I'm open to other ideas and I'd be happy to contribute code back or to 
 the Help if I am on a useful track?


 Blaine Wheeler
 Department of Social and Health Services Project Coordinator SEMS 
 Operations
 360.664.5416
 blaine.whee...@dshs.wa.gov



 --
  Everyone hates slow websites. So do we.
 Make your web apps faster with AppDynamics Download AppDynamics Lite 
 for free today:
 http://p.sf.net/sfu/appdyn_d2d_mar
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics Download AppDynamics Lite for free 
today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Obsoleted msi exists after minor update.

2013-03-13 Thread AK

Yes, behavior should have been like you sad.
I`m sorry, I didn't know the minor udate rules. 
Changing some components guid (autogenerated by heat) and changing file
locations of the same components did cause of my problems.

Thank you.
Best regards, Alexey.




--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Obsoleted-msi-exists-after-minor-update-tp7583777p7584312.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Building Wix 3.6

2013-03-13 Thread jeamis

Ok, I see that on http://wix.codeplex.com/releases/view/93929 there is a zip
file that contains source.  What is needed to build the wix 3.6 toolkit?

Can I build it using DevStudio 2010?   Is the source complete?   

I tried to open the wix.sln (which my machine says it is 2010 sln file, but
it wants to covert all the sub projects - that does not seem right if it is
a 2010 sln file.

Thanks

Jon





-
- jon
--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Building-Wix-3-6-tp7584313.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Using Update Element of the Bundle?

The BA does the look up, there is nothing built into the engine (as of yet)
since there are so many ways to do it. smile/

The question is do you want people that are installing an old setup.exe to
know that there is a newer one available? That's what the Bundle Update
does.


On Wed, Mar 13, 2013 at 10:38 AM, Wheeler, Blaine (DSHS/DCS) 
bwhee...@dshs.wa.gov wrote:

 So I did you get the Wix3.6 bundle to know 3.7 exists and to fetch and
 execute it?
 Is it going to be code in the BA?  A property I can detect?

 It seems like it will work to always execute a setup.exe from the same URL
 and just keep replacing it with an updated version that gets the latest
 stuff.  I wonder what pitfall I'm not spotting?

 -Original Message-
 From: Rob Mensching [mailto:r...@robmensching.com]
 Sent: Wednesday, March 13, 2013 8:40 AM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Using Update Element of the Bundle?

 In WiX v3.7 (and maybe all of WiX v3.7+) the Update/@Location really is
 just information provided to the BootstrapperApplication. Basically if you
 have an update location, the engine will say, Hey, BA, now would be a good
 time to use this string and figure out if there is an update.  Technically
 speaking, you don't even need to use update location to look updates (WiX
 v3.6 did updates without the feature existing) but now you get a pretty
 good hint when to go do the search.

 After that, I created the application syndication idea a long time ago,
 using ATOM/RSS to track updates. It was trendy back then and I'm trying to
 decide how much to push it going forward. I have a small spec kicking
 around here somewhere for the implementation that is in the WiX toolset and
 there is helper code in src\dutil\apup.cpp. I'm now wondering if the
 web-world has moved far enough to JSON if I should pull the important
 information into there... however, IE renders ATOM really nicely, ala:
 http://wixtoolset.org/releases/feed/v3.8


 On Tue, Mar 12, 2013 at 1:31 PM, Wheeler, Blaine (DSHS/DCS) 
 bwhee...@dshs.wa.gov wrote:

  I want to create a self updating setup.exe with Burn. I hope that using
  the Update element of the Bundle with Wix 3.7 will work.  The Help says
  this piece wasn't working yet but it looks like you use it for Wix
 updates.
   True?
 
 
  Is there a reason you use a feed or was it just convenience?
 
  My plan:
  Set up a folder and file tree off a web server. From the Wix 3.7 source
 it
  looks like the UpdateURL attribute of the Bundle element in the refers to
  the root URL  where all subsequent updates of this version of product
 will
  be.  For example: http://ourhouse/releases/myAppName.   Or Is Update
  Location='' / the critical element?  Or are both necessary?
 
  For each update we would add a folder under MyAppName with a unique ID
  such as the setup.exe version number (1.0.0.0,  1.0.0.1 etc)
 
  If we have 4 packages per setup.exe would each sub folder have to all of
  the packages referenced by the bundle?
 
  I'm open to other ideas and I'd be happy to contribute code back or to
 the
  Help if I am on a useful track?
 
 
  Blaine Wheeler
  Department of Social and Health Services
  Project Coordinator
  SEMS Operations
  360.664.5416
  blaine.whee...@dshs.wa.gov
 
 
 
 
 --
  Everyone hates slow websites. So do we.
  Make your web apps faster with AppDynamics
  Download AppDynamics Lite for free today:
  http://p.sf.net/sfu/appdyn_d2d_mar
  ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users
 
 

 --
 Everyone hates slow websites. So do we.
 Make your web apps faster with AppDynamics
 Download AppDynamics Lite for free today:
 http://p.sf.net/sfu/appdyn_d2d_mar
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


 --
 Everyone hates slow websites. So do we.
 Make your web apps faster with AppDynamics
 Download AppDynamics Lite for free today:
 http://p.sf.net/sfu/appdyn_d2d_mar
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Can Wix Boostrapper project be a VS Startup project?

Not today. You can build the bootstrapper project but there are no
debugging/launch features built into Votive. So all that F5 related stuff
doesn't do anything.


On Wed, Mar 13, 2013 at 9:58 AM, George Fleming gef...@microsoft.comwrote:

 I have a solution with a Wix Boostrapper project, and several other c++/c#
 projects.  The Boostrapper project, the project that creates the EXE file,
 cannot be set to be the startup project.   Although the solution compiles
 and a setup.exe gets build, nothing happens when I run the setup.exe.  If I
 try to run from VS, it says that my startup project is a DLL.

 Is it possible to make the Boostrapper project the startup project?  Or
 is there some other way to build?


 --
 Everyone hates slow websites. So do we.
 Make your web apps faster with AppDynamics
 Download AppDynamics Lite for free today:
 http://p.sf.net/sfu/appdyn_d2d_mar
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Building Wix 3.6

You need to enlist in the Mercurial repository to build. The sources.zip is
availble for debugging purposes (along with the pdbs.zip) it is not
buildable. To build wix36, you use make.bat. It requires lots of stuff
installed on your machine to build correctly.

On Wed, Mar 13, 2013 at 11:07 AM, jeamis jonathan.a...@intergraph.comwrote:

Ok, I see that on http://wix.codeplex.com/releases/view/93929 there is a
zip
file that contains source. What is needed to build the wix 3.6 toolkit?

Can I build it using DevStudio 2010? Is the source complete?

I tried to open the wix.sln (which my machine says it is 2010 sln file, but
it wants to covert all the sub projects - that does not seem right if it is
a 2010 sln file.

Thanks

Jon

-
- jon
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Building-Wix-3-6-tp7584313.html
Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] Looking at WiX to generate a Chained install package.

That or a embedded UI would need to be implemented in the WiX toolset.
Personally, I jumped over that feature and went for the full blown
bootstrapper/chainer with Burn... but GPO functionality does suffer a bit.
Might be an interesting feature to implement in the future to provide a
stock embedded UI from WiX toolset.


On Wed, Feb 27, 2013 at 6:22 AM, TimM timmay...@smarttech.com wrote:

 Since we still have a lot of our customers that still use GPO for pushing
 out
 our software we still have to have a .msi solution. So again it looks like
 we have to stay with InstallShield for all our chained projects.

 Tim.



 --
 View this message in context:
 http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Looking-at-WiX-to-generate-a-Chained-install-package-tp7583963p7583998.html
 Sent from the wix-users mailing list archive at Nabble.com.


 --
 Everyone hates slow websites. So do we.
 Make your web apps faster with AppDynamics
 Download AppDynamics Lite for free today:
 http://p.sf.net/sfu/appdyn_d2d_feb
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Can Wix Boostrapper project be a VS Startup project?

So any tip on how I can debug my problem?  My Setup.exe doesn't seem to do 
anything (it just silently returns, with no screen pop up).  Is there any way 
to invoke logging, like with msiexec?

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: Wednesday, March 13, 2013 11:11 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Can Wix Boostrapper project be a VS Startup project?

Not today. You can build the bootstrapper project but there are no 
debugging/launch features built into Votive. So all that F5 related stuff 
doesn't do anything.

On Wed, Mar 13, 2013 at 9:58 AM, George Fleming gef...@microsoft.comwrote:

 I have a solution with a Wix Boostrapper project, and several other 
 c++/c# projects.  The Boostrapper project, the project that creates the EXE 
 file,
 cannot be set to be the startup project.   Although the solution compiles
 and a setup.exe gets build, nothing happens when I run the setup.exe.  
 If I try to run from VS, it says that my startup project is a DLL.

 Is it possible to make the Boostrapper project the startup project?  
 Or is there some other way to build?

 --
  Everyone hates slow websites. So do we.
 Make your web apps faster with AppDynamics Download AppDynamics Lite 
 for free today:
 http://p.sf.net/sfu/appdyn_d2d_mar
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics Download AppDynamics Lite for free 
today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Any ideas on how to solve MessageBox focus, can be lost (using Custom Action DLL)

2013-03-13 Thread StevenOgilvie

Hi all,

I have a Custom Action DLL (C#)

Within the Welcome page to the ready to install page I have been able to
populate a MSI Property for any error messages/exceptions that are caused by
the Custom Action calls..
i.e.
At beginning of the Custom Action method:
SetSessionProperty(session, CUSTOM_ACTION_ERROR, 1);
within the Catch of the exception:
SetSessionProperty(session, CUSTOM_ACTION_ERROR, 0);
SetSessionProperty(session, CUSTOM_ACTION_ERROR_MESSAGE,Message for the
generic error dialog + ex.message);
then in the custom dialog WXS file I check when user select Next to see if
the CUSTOM_ACTION_ERROR is 0, and then spawn the generic error dialog with
the CUSTOM_ACTION_ERROR_MESSAGE

This works great, during that time frame, but when the Progress dialog
happens I can't do the same thing since I get an error within the custom
action dll that Cannot access session details from a non-immediate custom
action

Does anyone know how I can pass along info back to the MSI during the
Progress dialog or how to make the MessageBox modal to the MSI?

thanks,

Steve



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Any-ideas-on-how-to-solve-MessageBox-focus-can-be-lost-using-Custom-Action-DLL-tp7584319.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Can Wix Boostrapper project be a VS Startup project?

OK, I found the log file in %TEMP%.  Here's basically what it says:

[127C:12C0][2013-03-13T11:54:57]i001: Burn v3.7.1224.0, Windows v6.1 (Build 
7601: Service Pack 1), path: C:\...\Setup.exe, cmdline: ''
[127C:12C0][2013-03-13T11:54:57]i000: Initializing string variable 
'InstallFolder' to value 'PlaceHolder'
...
 [127C:12C0][2013-03-13T11:54:57]i000: Setting string variable 'WixBundleName' 
to value 'Worker'
[127C:12C0][2013-03-13T11:54:57]i000: Loading managed bootstrapper application.
[127C:12C0][2013-03-13T11:54:57]e000: Error 0x80131040: Failed to create the 
managed UX.
[127C:12C0][2013-03-13T11:54:57]e000: Error 0x80131040: Failed to create UX.
[127C:12C0][2013-03-13T11:54:57]e000: Error 0x80131040: Failed to load UX.
[127C:12C0][2013-03-13T11:54:57]e000: Error 0x80131040: Failed while running

Any pointer on what's wrong?

-Original Message-
From: George Fleming [mailto:gef...@microsoft.com] 
Sent: Wednesday, March 13, 2013 11:28 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Can Wix Boostrapper project be a VS Startup project?

So any tip on how I can debug my problem?  My Setup.exe doesn't seem to do 
anything (it just silently returns, with no screen pop up).  Is there any way 
to invoke logging, like with msiexec?

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Wednesday, March 13, 2013 11:11 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Can Wix Boostrapper project be a VS Startup project?

Not today. You can build the bootstrapper project but there are no 
debugging/launch features built into Votive. So all that F5 related stuff 
doesn't do anything.


On Wed, Mar 13, 2013 at 9:58 AM, George Fleming gef...@microsoft.comwrote:

 I have a solution with a Wix Boostrapper project, and several other
 c++/c# projects.  The Boostrapper project, the project that creates 
 c++the EXE file,
 cannot be set to be the startup project.   Although the solution compiles
 and a setup.exe gets build, nothing happens when I run the setup.exe.  
 If I try to run from VS, it says that my startup project is a DLL.

 Is it possible to make the Boostrapper project the startup project?  
 Or is there some other way to build?


 --
  Everyone hates slow websites. So do we.
 Make your web apps faster with AppDynamics Download AppDynamics Lite 
 for free today:
 http://p.sf.net/sfu/appdyn_d2d_mar
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics Download AppDynamics Lite for free 
today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics Download AppDynamics Lite for free 
today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users




--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] WXL schema recognized by WixStdBA

2013-03-13 Thread Milan Kaše

The compiler recognizes the UI element in the WixLocalization schema that
allows a localization to override the position, size, and text of dialogs
and controls. The WixStdBA also supports this WXL feature however the
corresponding element is named Control instead of UI. Is this
difference intentional or is it a bug?

The responsible code is in functionParseWxlControls in
src/dutil/locutil.cpp:

@@ -337,7 +337,7 @@
 IXMLDOMNodeList* pixnl = NULL;
 DWORD dwIdx = 0;

-hr = XmlSelectNodes(pElement, LControl, pixnl);
+hr = XmlSelectNodes(pElement, LUI, pixnl);
 ExitOnLastError(hr, Failed to get Control child nodes of Wxl File.);

 hr =
pixnl-get_length(reinterpret_castlong*(pWixLoc-cLocControls));
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] SOLVED: Execute a custom action only on uninstall?

2013-03-13 Thread Vern Graner

OK, Thanks to Steven for pointing me in the right direction, I now have 
a solution that works fine for me. Here's the WiX source:

   InstallExecuteSequence
   Custom Action=ScriptForInstall After=InstallInitialize /
   Custom Action='ScriptForRemove' 
Before='ScriptForInstall'(NOT UPGRADINGPRODUCTCODE) AND 
(REMOVE=ALL)/Custom
   /InstallExecuteSequence


   CustomAction Id=ScriptForInstall
  Directory=MyProgram_1
 ExeCommand=cmd.exe /c quot;[MyProgram_1]Util1.batquot;
 Return=ignore
Execute=commit
Impersonate=no/

   CustomAction Id=ScriptForRemove
  Directory=MyProgram_1
 ExeCommand=cmd.exe /c quot;[MyProgram_1]Util2.batquot;
 Return=check
Execute=deferred
Impersonate=no/

The above causes a script (util1.bat) to be kicked off after all the 
files have been unpacked and causes a different script (util2.bat) to be 
run BEFORE removing the files that were unpacked by the original 
install. Works great! thanks for the help!

Vern


On 3/12/2013 3:05 PM, Steven Ogilvie wrote:

 You could have a custom action that has an execute sequence for both 
 install and uninstall or one or the other...

 Depends on what custom actions you need...

 On install, it is not installed yet, so NOT Installed custom action 
 would only occur when the product has not been installed. Setting the 
 Custom action sequence to Installed means only run this when the 
 product has been installed(but that could mean a 
 Change/Repair/Remove so you have to be careful, hence I put 
 Installed and Not REINSTALL which means it would not run on an 
 Install or repair but a remove...

 Steve

 *From:*Vern Graner [mailto:v...@txis.com]
 *Sent:* March-12-13 2:59 PM
 *To:* General discussion for Windows Installer XML toolset.
 *Subject:* Re: [WiX-users] Execute a custom action only on uninstall?

 Steve:

 Thanks for the reply. I hadn't had a chance to experiment with this 
 till today. I was looking at the two InstallExecuteSequence 
 sections you show below and I guess I'm just not getting what makes 
 the script only execute the customaction only on *UNinstall*, and 
 not on install?

 Also, is the second example (the one labeled Now let's do something 
 for uninstall:) an addition to the first one as in would both of 
 those code pieces be included to make a working example?

 Vern

 On 3/5/2013 1:02 PM, Steven Ogilvie wrote:

 Classification: Public

   

   

 You use the install sequence to set up your custom actions...

   

 So let's say I have custom action 1 which does something during install:

   

 CustomAction Id= CA_Set_Something  Property=SOME_PROPERTY 
 Value=[ComputerName]/ UI

   ProgressText Action= CA_Set_Something CA: Setting a 
 property.../ProgressText /UI

   

 InstallExecuteSequence

 Custom Action=CA_Set_Something After=InstallValidateNOT 
 Installed/Custom

   

 Now let's do something for uninstall:

   

 CustomAction Id=CA_Set_DELETE_SOME_FILE Property= CA_DELETE_SOME_FILE 
  Value=[SOME_PATH]\MyFile.txt|/ CustomAction Id=CA_ DELETE_SOME_FILE  
 BinaryKey=BIN_CustomAction DllEntry=RemoveFileOnUninstall 
 Impersonate=no Execute=deferred Return=ignore/ UI

  ProgressText Action=CA_ DELETE_SOME_FILE CA: Delete some 
 file.../ProgressText /UI

   

 [InstallExecuteSequence]

 Custom Action= CA_Set_DELETE_SOME_FILE 
 After=InstallValidateInstalled and Not REINSTALL/Custom

   

 Custom Action=CA_DELETE_SOME_FILE After=InstallFilesInstalled and 
 Not REINSTALL/Custom

   

 Steve



 -- 
 Vern Graner CNE/CNA/SSE| If the network is down, then you're
 Senior Systems Engineer| obviously incompetent so why are we
 Texas Information Services | paying you? Of course, if the network
 http://www.txis.com | is up, then we obviously don't need
 Austin Office 512 328-8947 | you, so why are we paying you? ©VLG

-- 
Vern Graner CNE/CNA/SSE| If the network is down, then you're
Senior Systems Engineer| obviously incompetent so why are we
Texas Information Services | paying you? Of course, if the network
http://www.txis.com| is up, then we obviously don't need
Austin Office 512 328-8947 | you, so why are we paying you? ©VLG

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Building Wix 3.6

2013-03-13 Thread jeamis

Thanks Rob,

So how do I enlist to the Mercurial repository?   All I want to do is
compile burn.  I want to confirm our static analysis and debugging. 

Any direction is appreciated.

-Jon



-
- jon
--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Building-Wix-3-6-tp7584313p7584326.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Any ideas on how to solve MessageBox focus, can be lost (using Custom Action DLL)

2013-03-13 Thread gapearce

Try this - it will keep the messagebox on top of everything.

MessageBox(NULL, LPlease click ok to continue., LSetup messageBox title,
MB_OK | MB_SYSTEMMODAL);



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Any-ideas-on-how-to-solve-MessageBox-focus-can-be-lost-using-Custom-Action-DLL-tp7584319p7584327.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Can Wix Boostrapper project be a VS Startup project?

This is an area to improve for debugging Bootstrapper Applications. The
error code will help but hard sometimes to figure out all the different
things that can go wrong in a managed BA. I often drop down to do 
devenv.com /debugexe path\to\bundle.exe and then start debugging through
the Burn code using the pdbs.zip and sources.zip files.  Brute force, but
very, very effective.


On Wed, Mar 13, 2013 at 12:05 PM, George Fleming gef...@microsoft.comwrote:

 OK, I found the log file in %TEMP%.  Here's basically what it says:

 [127C:12C0][2013-03-13T11:54:57]i001: Burn v3.7.1224.0, Windows v6.1
 (Build 7601: Service Pack 1), path: C:\...\Setup.exe, cmdline: ''
 [127C:12C0][2013-03-13T11:54:57]i000: Initializing string variable
 'InstallFolder' to value 'PlaceHolder'
 ...
  [127C:12C0][2013-03-13T11:54:57]i000: Setting string variable
 'WixBundleName' to value 'Worker'
 [127C:12C0][2013-03-13T11:54:57]i000: Loading managed bootstrapper
 application.
 [127C:12C0][2013-03-13T11:54:57]e000: Error 0x80131040: Failed to create
 the managed UX.
 [127C:12C0][2013-03-13T11:54:57]e000: Error 0x80131040: Failed to create
 UX.
 [127C:12C0][2013-03-13T11:54:57]e000: Error 0x80131040: Failed to load UX.
 [127C:12C0][2013-03-13T11:54:57]e000: Error 0x80131040: Failed while
 running

 Any pointer on what's wrong?

 -Original Message-
 From: George Fleming [mailto:gef...@microsoft.com]
 Sent: Wednesday, March 13, 2013 11:28 AM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Can Wix Boostrapper project be a VS Startup
 project?

 So any tip on how I can debug my problem?  My Setup.exe doesn't seem to do
 anything (it just silently returns, with no screen pop up).  Is there any
 way to invoke logging, like with msiexec?

 -Original Message-
 From: Rob Mensching [mailto:r...@robmensching.com]
 Sent: Wednesday, March 13, 2013 11:11 AM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Can Wix Boostrapper project be a VS Startup
 project?

 Not today. You can build the bootstrapper project but there are no
 debugging/launch features built into Votive. So all that F5 related stuff
 doesn't do anything.


 On Wed, Mar 13, 2013 at 9:58 AM, George Fleming gef...@microsoft.com
 wrote:

  I have a solution with a Wix Boostrapper project, and several other
  c++/c# projects.  The Boostrapper project, the project that creates
  c++the EXE file,
  cannot be set to be the startup project.   Although the solution compiles
  and a setup.exe gets build, nothing happens when I run the setup.exe.
  If I try to run from VS, it says that my startup project is a DLL.
 
  Is it possible to make the Boostrapper project the startup project?
  Or is there some other way to build?
 
 
  --
   Everyone hates slow websites. So do we.
  Make your web apps faster with AppDynamics Download AppDynamics Lite
  for free today:
  http://p.sf.net/sfu/appdyn_d2d_mar
  ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users
 
 

 --
 Everyone hates slow websites. So do we.
 Make your web apps faster with AppDynamics Download AppDynamics Lite for
 free today:
 http://p.sf.net/sfu/appdyn_d2d_mar
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users





 --
 Everyone hates slow websites. So do we.
 Make your web apps faster with AppDynamics Download AppDynamics Lite for
 free today:
 http://p.sf.net/sfu/appdyn_d2d_mar
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users





 --
 Everyone hates slow websites. So do we.
 Make your web apps faster with AppDynamics
 Download AppDynamics Lite for free today:
 http://p.sf.net/sfu/appdyn_d2d_mar
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Managed Boostrapper Application and Wix 3.7

I have an Burn app that works with Wix 3.6.  The Bundle.wxs looks something 
like this:

BootstrapperApplication Id='ManagedBootstrapperApplicationHost' 
SourceFile=$(var.WixToolsDir)\Burn\mbahost.dll
  Payload SourceFile=$(var.WixToolsDir)\SDK\BootstrapperCore.dll 
Name=BootstrapperCore.dll /
  Payload SourceFile=BootstrapperCore.config  
Name=BootstrapperCore.config /

Trying to do the same thing with Wix 3.7, and I ran into problems (see my 
previous posts under Can Wix Bootstrapper project be a VS Startup project).  
Since Wix 3.7 doesn't have a mbahost.dll as part of the package, I copied the 
mbahost.dll from Wix 3.6, and I guess that's probably the source of the 
problem.  Using this old dll, my application fails to create UX, according to 
the log file.

So I guess the question is, for Wix 3.7, what is the correct way to do this?

--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Can Wix Boostrapper project be a VS Startup project?

Just kind of a general question on how to do this.  Since my Setup.exe only has 
a Setup.wixpdb, and not a Setup.pdb, VS does not allow me to step into it.  How 
do I utilize pdbs.zip and sources.zip to debug?

-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: Wednesday, March 13, 2013 1:54 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Can Wix Boostrapper project be a VS Startup project?

This is an area to improve for debugging Bootstrapper Applications. The error 
code will help but hard sometimes to figure out all the different things that 
can go wrong in a managed BA. I often drop down to do 
devenv.com /debugexe path\to\bundle.exe and then start debugging through the 
Burn code using the pdbs.zip and sources.zip files.  Brute force, but very, 
very effective.

On Wed, Mar 13, 2013 at 12:05 PM, George Fleming gef...@microsoft.comwrote:

 OK, I found the log file in %TEMP%.  Here's basically what it says:

 [127C:12C0][2013-03-13T11:54:57]i001: Burn v3.7.1224.0, Windows v6.1 
 (Build 7601: Service Pack 1), path: C:\...\Setup.exe, cmdline: ''
 [127C:12C0][2013-03-13T11:54:57]i000: Initializing string variable 
 'InstallFolder' to value 'PlaceHolder'
 ...
  [127C:12C0][2013-03-13T11:54:57]i000: Setting string variable 
 'WixBundleName' to value 'Worker'
 [127C:12C0][2013-03-13T11:54:57]i000: Loading managed bootstrapper 
 application.
 [127C:12C0][2013-03-13T11:54:57]e000: Error 0x80131040: Failed to 
 create the managed UX.
 [127C:12C0][2013-03-13T11:54:57]e000: Error 0x80131040: Failed to 
 create UX.
 [127C:12C0][2013-03-13T11:54:57]e000: Error 0x80131040: Failed to load UX.
 [127C:12C0][2013-03-13T11:54:57]e000: Error 0x80131040: Failed while 
 running

 Any pointer on what's wrong?

 -Original Message-
 From: George Fleming [mailto:gef...@microsoft.com]
 Sent: Wednesday, March 13, 2013 11:28 AM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Can Wix Boostrapper project be a VS Startup 
 project?

 So any tip on how I can debug my problem?  My Setup.exe doesn't seem 
 to do anything (it just silently returns, with no screen pop up).  Is 
 there any way to invoke logging, like with msiexec?

 -Original Message-
 From: Rob Mensching [mailto:r...@robmensching.com]
 Sent: Wednesday, March 13, 2013 11:11 AM
 To: General discussion for Windows Installer XML toolset.
 Subject: Re: [WiX-users] Can Wix Boostrapper project be a VS Startup 
 project?

 Not today. You can build the bootstrapper project but there are no 
 debugging/launch features built into Votive. So all that F5 related 
 stuff doesn't do anything.

 On Wed, Mar 13, 2013 at 9:58 AM, George Fleming gef...@microsoft.com
 wrote:

  I have a solution with a Wix Boostrapper project, and several other
  c++/c# projects.  The Boostrapper project, the project that creates 
  c++the EXE file,
  cannot be set to be the startup project.   Although the solution compiles
  and a setup.exe gets build, nothing happens when I run the setup.exe.
  If I try to run from VS, it says that my startup project is a DLL.

  Is it possible to make the Boostrapper project the startup project?
  Or is there some other way to build?

  --
   Everyone hates slow websites. So do we.
  Make your web apps faster with AppDynamics Download AppDynamics Lite 
  for free today:
  http://p.sf.net/sfu/appdyn_d2d_mar
  ___
  WiX-users mailing list
  WiX-users@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wix-users

 --
  Everyone hates slow websites. So do we.
 Make your web apps faster with AppDynamics Download AppDynamics Lite 
 for free today:
 http://p.sf.net/sfu/appdyn_d2d_mar
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

 --
  Everyone hates slow websites. So do we.
 Make your web apps faster with AppDynamics Download AppDynamics Lite 
 for free today:
 http://p.sf.net/sfu/appdyn_d2d_mar
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

 --
  Everyone hates slow websites. So do we.
 Make your web apps faster with AppDynamics Download AppDynamics Lite 
 for free today:
 http://p.sf.net/sfu/appdyn_d2d_mar
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--

Re: [WiX-users] Managed Boostrapper Application and Wix 3.7

You must have something from very early in WiX v3.6. The correct way to
reference the mbahost is like so:

BootstrapperApplicationRef Id='ManagedBootstrapperApplicationHost'


On Wed, Mar 13, 2013 at 8:58 PM, George Fleming gef...@microsoft.comwrote:

 I have an Burn app that works with Wix 3.6.  The Bundle.wxs looks
 something like this:

 BootstrapperApplication Id='ManagedBootstrapperApplicationHost'
 SourceFile=$(var.WixToolsDir)\Burn\mbahost.dll
   Payload SourceFile=$(var.WixToolsDir)\SDK\BootstrapperCore.dll
 Name=BootstrapperCore.dll /
   Payload SourceFile=BootstrapperCore.config 
 Name=BootstrapperCore.config /

 Trying to do the same thing with Wix 3.7, and I ran into problems (see my
 previous posts under Can Wix Bootstrapper project be a VS Startup
 project).  Since Wix 3.7 doesn't have a mbahost.dll as part of the
 package, I copied the mbahost.dll from Wix 3.6, and I guess that's probably
 the source of the problem.  Using this old dll, my application fails to
 create UX, according to the log file.

 So I guess the question is, for Wix 3.7, what is the correct way to do
 this?


 --
 Everyone hates slow websites. So do we.
 Make your web apps faster with AppDynamics
 Download AppDynamics Lite for free today:
 http://p.sf.net/sfu/appdyn_d2d_mar
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users


--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Can Wix Boostrapper project be a VS Startup project?