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

[Brian_Covington]

Forgive me, but, I do not quite understand what you are asking.  The first
application is dependant upon the second and cannot exist in singular (i.e.
it is built on top of the others' dlls).



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Managed-Bootstrapper-Second-Patch-does-not-supersede-first-Patch-tp7581779p7581796.html
Sent from the wix-users mailing list archive at Nabble.com.

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

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

[Brian C]

Yes.  RTM is 10.00.35.0002, HF1 is 10.00.35.0003, and HF2 is 10.00.35.0004.  
The versions are so close together because we are testing, before our release.  
I am rerunning the testing rolling the revision number (i.e. 10.00.35.0002, 
10.00.36.0003, 10.00.37.0004).  I will post the results.





From: Rob Mensching 
To: General discussion for Windows Installer XML toolset. 
 
Sent: Tuesday, November 6, 2012 10:27 AM
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede 
first Patch

Is the second bundle version higher? If not, then it doesn't upgrade the
old bundle.


On Tue, Nov 6, 2012 at 7:13 AM, Brian_Covington wrote:

> Hi all,
>  I have created a managed bootstrapper to install my 2 product msis.  I
> have peared down the source of this bootstrapper to create a patch
> bootstrapper, to install the msp files for these products.  Everything
> works
> as expected until I try to install the second patch.  It installs along
> side
> the first patch, not superseding it.  The patches are created with
> superseding in the patch.wxs file, and are applied appropriately, just not
> the ARP entry for the bundle:
>
> ARP:
>
> Product
> -HotFix1
> -HotFix2
>
> instead of
>
> Product
> -HotFix2
>
> Is there something extra I need to do to the second patch bundle to tell it
> to supersede the first patch bundle? I use the same upgrade code for all
> bundles, figuring that should not change.  The second patch bundle looks
> exacly the same as the first, only the version number and patch files used
> are different.
>
> Here are my files:
> Initial bundle:
>
> 
> http://schemas.microsoft.com/wix/2006/wi";
>        xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";>
>
>          Name="PRODUCT2013"
>        Version="$(prod.AppVersion)"
>        Manufacturer="MANUFACT"
>        UpgradeCode="GUID"
>    Condition="(VersionNT >= v6.1)">
>
>                    Id="WixMbaPrereqPackageId"
>                Value="Netfx4Full" />
>                    Id="WixMbaPrereqLicenseUrl"
>                Value="NetfxLicense.rtf" />
>
>    
>      
>
> SourceFile="..\..\Bootstrapper_WIX\ClassLibrary1\MyApplication.BootstrapperCore.config"
> />
>       SourceFile="..\..\Bootstrapper_WIX\ClassLibrary1\bin\Release\MyBA.dll" />
>       SourceFile="..\..\BootstrapperPatch_WIX\Bootstrapper1\NetfxLicense.rtf" />
>    
>
>                    Root="HKLM"
>                Key="SOFTWARE\Microsoft\Net Framework Setup\NDP\v4\Full"
>                Value="Version"
>                Variable="Netfx4FullVersion" />
>                    Root="HKLM"
>                Key="SOFTWARE\Microsoft\Net Framework Setup\NDP\v4\Full"
>                Value="Version"
>                Variable="Netfx4x64FullVersion"
>                Win64="yes" />
>
>    
>                      Cache="no"
>                Compressed="yes"
>                PerMachine="yes"
>                Permanent="yes"
>                Vital="yes"
>
> SourceFile="X:\Tools\Setup\WiX\Resources\dotnetfx40_full_x86_x64.exe"
>        DetectCondition="Netfx4FullVersion AND (NOT VersionNT64 OR
> Netfx4x64FullVersion)" >
>      
>      
>      
>    
>  
> 
>
>
> Patch bundle:
>
> 
> http://schemas.microsoft.com/wix/2006/wi";
> xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";>
>
>          Name="PRODUCT2013 HotFix 1"
>        ParentName="PRODUCT2013"
>        Version="$(prod.AppVersion)"
>    Manufacturer="MANU"
>        UpgradeCode="SAME_UPGRADE_CODE_AS_ORIGINAL_BUNDLE"
>        Condition="(VersionNT >= v6.1)"
>        DisableModify="yes">
>
>                    Id="WixMbaPrereqPackageId"
>                Value="Netfx4Full" />
>                    Id="WixMbaPrereqLicenseUrl"
>                Value="NetfxLicense.rtf" />
>
>    
>      
>
> SourceFile="..\..\BootstrapperPatch_WIX\ClassLibrary1\MyApplication.BootstrapperCore.config"
> />
>      
> SourceFile="..\..\BootstrapperPatch_WIX\ClassLibrary1\bin\Release\MyPatchBA.dll"
> />
>       SourceFile="..\..\BootstrapperPatch_WIX\Bootstrapper1\NetfxLicense.rtf" />
>    
>
>     Action="Patch"/>
>
>                    Root="HKLM"
>                Key="SOFTWARE\Microsoft\Net Framework Setup\NDP\v4\Full"
>                Value="Version"
>                Variable="Netfx4FullVersion" />
>                    Root="HKLM"
>                Key="SOFTWARE\Microsoft\Net Framework Setup\NDP\v4\Full"
>                Value="Version"
>                Variable="Netfx4x64FullVersion"
>                Win64="yes" />
>
>    
>                      Cache="no"
>                Compressed="yes"
>                PerMachine="yes"
>                Permanent="yes"
>                Vital="yes"
>
> SourceFile="X:\Tools\Setup\WiX\Resources\dotnetfx40_full_x86_x64.exe"
>        DetectCondition="Netfx4FullVersion AND (NOT VersionNT64 OR
> Netfx4x64FullVersion)" >
>      
>      
>      
>    
>  
> 
>
> Any help would be greatly appreciated.
>
> Cheers,
> Brian
>
>
>
> --
> View this message in context:
> http://wind

Re: [WiX-users] Burn package ref counting

[Rob Mensching]

Automatic for MSIs in v3.6 and MSI + MSP in v3.7. Exes need to have a
provider key set for them in the ExePackage. MSUs are weird and I recommend
just making them permanent.


On Tue, Nov 6, 2012 at 10:26 AM, Nick Ramirez  wrote:

> I wasn't able to find much information about this. Does Burn handle package
> ref counting automatically? Is there nothing we need to do? Or should we be
> using the DependencyExtension in some way? Do install devs need to handle
> adding to the package ref count and subtracting?
>
> Thanks.
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-package-ref-counting-tp7581786.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> --
> LogMeIn Central: Instant, anywhere, Remote PC access and management.
> Stay in control, update software, and manage PCs from one command center
> Diagnose problems and improve visibility into emerging IT issues
> Automate, monitor and manage. Do more in less time with Central
> http://p.sf.net/sfu/logmein12331_d2d
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



-- 
virtually,

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

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

[Goran]

I am guessing that you have intentionally do that, in order to allow two
parallel installations of the same application on one PC? In cases where
only one application can exist on one PC, is it possible to deny existence
of parallel applications, so it will always upgrade?



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Managed-Bootstrapper-Second-Patch-does-not-supersede-first-Patch-tp7581779p7581788.html
Sent from the wix-users mailing list archive at Nabble.com.

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

Re: [WiX-users] WiX 3.6 MergeModule creation regression?

[Michael Turner]

Dirk Ziegelmeier wrote
> here is a minimal mergemodule showing the error:
> 
> 
> http://schemas.microsoft.com/wix/2006/wi";>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  KeyPath="yes" Checksum="yes" />
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> W:\tmp\CommonFiles.wxs(14) : error LGHT0231 : The component
> 'cComSTAHelper.63744358_CA08_4563_B039_4BE7181B668E' has a key file with
> path 'TARGETDIR\acme\comstahelper\comstahelper.dll'.  Since this path is
> not rooted in one of the standard directories (like ProgramFilesFolder),
> this component does not fit the criteria for having an automatically
> generated guid.  (This error may also occur if a path contains a likely
> standard directory such as nesting a directory
> with name "Common Files" under ProgramFilesFolder.)

Apologies for the necropost, but this ( Bug #3121
  ) looks similar to  Bug #2938
   that I filed in May, where I
demonstrated that this differed from the behavior in WiX 3.5.  Rob, your
response at the time was that "Auto-generated Component GUIDs were never
supported in Merge Modules unless you used
Directory@ComponentGuidGenerationSeed."

My understanding is that is that "CommonFilesFolder" must be modularized
because of the way that MSI handles merges (Directory table can't reconcile
identical primary keys from multiple sources), and after it is modularized,
it is no longer a well-known root directory.  My best guess it that WiX 3.6
changed the Component GUID auto-generation to occur after property/directory
modularization rather than before.  

Rob, could you confirm whether this is considered a regression or working as
designed?

Thanks,
Mike



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-3-6-MergeModule-creation-regression-tp7581302p7581787.html
Sent from the wix-users mailing list archive at Nabble.com.

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

[WiX-users] Burn package ref counting

[Nick Ramirez]

I wasn't able to find much information about this. Does Burn handle package
ref counting automatically? Is there nothing we need to do? Or should we be
using the DependencyExtension in some way? Do install devs need to handle
adding to the package ref count and subtracting?

Thanks.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-package-ref-counting-tp7581786.html
Sent from the wix-users mailing list archive at Nabble.com.

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

Re: [WiX-users] How to reference a preprocessor which is imported by the wixproj file?

[Rob Mensching]

See the DefineConstants here:
http://wix.sourceforge.net/manual-wix3/msbuild_task_reference_candle.htm


On Tue, Nov 6, 2012 at 1:11 AM, tetelee  wrote:

> I know that if I define a preprocessor directly in the wixproj file, I can
> use it in wxs file just like this: $(var.PROPERTYNAME). However, the
> problem
> with this kind of preprocessor is it is Configuration/Platform specific. We
> want to define a SW version number(which needs to be used in wxs file as
> well as wixproj file for AfterBuild target) so it will easily become out of
> sync(for example, build engineer only modifies the version for the current
> Configuration/Platform combination in Visual Studio IDE, and it becomes
> different from other combinations).
>
> I got one suggestion from a thread. I created one txt file which only
> defines a MSBuild project and inside this project, I defined a version
> number property in the common PropertyGroup. After that, I imported this
> project in my wixproj file. By doing this, my main wix project file can
> reference this property(so that I can rename my output file using the
> version number, which is my ultimate goal) and yet this property will not
> show up in the project's properties window so we won't mess it up.
>
> My txt file looks like this:
>
> 
> http://schemas.microsoft.com/developer/msbuild/2003";
> ToolsVersion="4.0">
> 
>   1.2.3.4
> 
> 
>
>
> And in my wixproj file, I import it by:
> Import Project="Version.txt" />
>
>
> So now in my project file I can reference just simply by $(Version). But if
> I reference it inside my wxs file like this:
> 
>
>
> It is complaining about undefined preprocessor. So can anyone tell me how
> to
> reference it correctly? Thanks!
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-reference-a-preprocessor-which-is-imported-by-the-wixproj-file-tp7581769.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> --
> LogMeIn Central: Instant, anywhere, Remote PC access and management.
> Stay in control, update software, and manage PCs from one command center
> Diagnose problems and improve visibility into emerging IT issues
> Automate, monitor and manage. Do more in less time with Central
> http://p.sf.net/sfu/logmein12331_d2d
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>



-- 
virtually,

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

Re: [WiX-users] New bundle installs new application (doesn't upgrade)

[Goran]

Thanks.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/New-bundle-installs-new-application-doesn-t-upgrade-tp7581742p7581784.html
Sent from the wix-users mailing list archive at Nabble.com.

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

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

[Rob Mensching]

Is the second bundle version higher? If not, then it doesn't upgrade the
old bundle.


On Tue, Nov 6, 2012 at 7:13 AM, Brian_Covington wrote:

> Hi all,
>   I have created a managed bootstrapper to install my 2 product msis.  I
> have peared down the source of this bootstrapper to create a patch
> bootstrapper, to install the msp files for these products.  Everything
> works
> as expected until I try to install the second patch.  It installs along
> side
> the first patch, not superseding it.  The patches are created with
> superseding in the patch.wxs file, and are applied appropriately, just not
> the ARP entry for the bundle:
>
> ARP:
>
> Product
> -HotFix1
> -HotFix2
>
> instead of
>
> Product
> -HotFix2
>
> Is there something extra I need to do to the second patch bundle to tell it
> to supersede the first patch bundle? I use the same upgrade code for all
> bundles, figuring that should not change.  The second patch bundle looks
> exacly the same as the first, only the version number and patch files used
> are different.
>
> Here are my files:
> Initial bundle:
>
> 
> http://schemas.microsoft.com/wix/2006/wi";
> xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";>
>
>Name="PRODUCT2013"
> Version="$(prod.AppVersion)"
> Manufacturer="MANUFACT"
> UpgradeCode="GUID"
> Condition="(VersionNT >= v6.1)">
>
>  Id="WixMbaPrereqPackageId"
> Value="Netfx4Full" />
>  Id="WixMbaPrereqLicenseUrl"
> Value="NetfxLicense.rtf" />
>
> 
>   
>
> SourceFile="..\..\Bootstrapper_WIX\ClassLibrary1\MyApplication.BootstrapperCore.config"
> />
>SourceFile="..\..\Bootstrapper_WIX\ClassLibrary1\bin\Release\MyBA.dll" />
>SourceFile="..\..\BootstrapperPatch_WIX\Bootstrapper1\NetfxLicense.rtf" />
> 
>
>  Root="HKLM"
> Key="SOFTWARE\Microsoft\Net Framework Setup\NDP\v4\Full"
> Value="Version"
> Variable="Netfx4FullVersion" />
>  Root="HKLM"
> Key="SOFTWARE\Microsoft\Net Framework Setup\NDP\v4\Full"
> Value="Version"
> Variable="Netfx4x64FullVersion"
> Win64="yes" />
>
> 
>Cache="no"
> Compressed="yes"
> PerMachine="yes"
> Permanent="yes"
> Vital="yes"
>
> SourceFile="X:\Tools\Setup\WiX\Resources\dotnetfx40_full_x86_x64.exe"
> DetectCondition="Netfx4FullVersion AND (NOT VersionNT64 OR
> Netfx4x64FullVersion)" >
>   
>   
>   
> 
>   
> 
>
>
> Patch bundle:
>
> 
> http://schemas.microsoft.com/wix/2006/wi";
> xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";>
>
>Name="PRODUCT2013 HotFix 1"
> ParentName="PRODUCT2013"
> Version="$(prod.AppVersion)"
> Manufacturer="MANU"
> UpgradeCode="SAME_UPGRADE_CODE_AS_ORIGINAL_BUNDLE"
> Condition="(VersionNT >= v6.1)"
> DisableModify="yes">
>
>  Id="WixMbaPrereqPackageId"
> Value="Netfx4Full" />
>  Id="WixMbaPrereqLicenseUrl"
> Value="NetfxLicense.rtf" />
>
> 
>   
>
> SourceFile="..\..\BootstrapperPatch_WIX\ClassLibrary1\MyApplication.BootstrapperCore.config"
> />
>   
> SourceFile="..\..\BootstrapperPatch_WIX\ClassLibrary1\bin\Release\MyPatchBA.dll"
> />
>SourceFile="..\..\BootstrapperPatch_WIX\Bootstrapper1\NetfxLicense.rtf" />
> 
>
>  Action="Patch"/>
>
>  Root="HKLM"
> Key="SOFTWARE\Microsoft\Net Framework Setup\NDP\v4\Full"
> Value="Version"
> Variable="Netfx4FullVersion" />
>  Root="HKLM"
> Key="SOFTWARE\Microsoft\Net Framework Setup\NDP\v4\Full"
> Value="Version"
> Variable="Netfx4x64FullVersion"
> Win64="yes" />
>
> 
>Cache="no"
> Compressed="yes"
> PerMachine="yes"
> Permanent="yes"
> Vital="yes"
>
> SourceFile="X:\Tools\Setup\WiX\Resources\dotnetfx40_full_x86_x64.exe"
> DetectCondition="Netfx4FullVersion AND (NOT VersionNT64 OR
> Netfx4x64FullVersion)" >
>   
>   
>   
> 
>   
> 
>
> Any help would be greatly appreciated.
>
> Cheers,
> Brian
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Managed-Bootstrapper-Second-Patch-does-not-supersede-first-Patch-tp7581779.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> --
> LogMeIn Central: Instant, anywhere, Remote PC access and management.
> Stay in control, update software, and manage PCs from one command center
> Diagnose problems and improve visi

Re: [WiX-users] Setting the version number...

[Goran]

Thanks, that worked fine.




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

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

Re: [WiX-users] How to use FeaturesDlg

[Miller, Nick (GE Intelligent Platforms)]

Yes! Thank you.  I did find that I had to wrap it in CDATA.




-Original Message-
From: Rohit Sharma (AIDC) [mailto:rohit.sha...@accelrys.com] 
Sent: Tuesday, November 06, 2012 10:13 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to use FeaturesDlg

This should do


(&DB_FEAT=3) AND NOT(!DB_FEAT=3) 

Cheers
Rohit

-Original Message-
From: Miller, Nick (GE Intelligent Platforms)
[mailto:nick.mil...@ge.com]
Sent: Tuesday, November 06, 2012 7:53 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to use FeaturesDlg

I have 2 features.  One installs and configures a service.  The other
installs the database components.  The database components are optional.
So I try to use FeaturesDlg from Wix to collect whether or not to
install the feature.  This would work, except I also have a CustomAction
that should run only if the database components are installed.  How can
I put a condition in the CustomAction so it won't execute if the Feature
was deselected in the FeaturesDlg.

Here's an abbreviation of the .wxs code.

 
  

YES
YES

> 

 

NOT Installed

NOT Installed  <
NOT Installed

NOT Installed 









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




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

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

Re: [WiX-users] How to use FeaturesDlg

[Rohit Sharma (AIDC)]

This should do


(&DB_FEAT=3) AND 
NOT(!DB_FEAT=3)


Cheers
Rohit

-Original Message-
From: Miller, Nick (GE Intelligent Platforms) [mailto:nick.mil...@ge.com] 
Sent: Tuesday, November 06, 2012 7:53 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to use FeaturesDlg

I have 2 features.  One installs and configures a service.  The other
installs the database components.  The database components are optional.
So I try to use FeaturesDlg from Wix to collect whether or not to
install the feature.  This would work, except I also have a CustomAction
that should run only if the database components are installed.  How can
I put a condition in the CustomAction so it won't execute if the Feature
was deselected in the FeaturesDlg.

Here's an abbreviation of the .wxs code.






  


YES
YES

>





NOT Installed

NOT Installed
 <
NOT Installed

NOT Installed 








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



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

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

[Brian_Covington]

Hi all,
  I have created a managed bootstrapper to install my 2 product msis.  I
have peared down the source of this bootstrapper to create a patch
bootstrapper, to install the msp files for these products.  Everything works
as expected until I try to install the second patch.  It installs along side
the first patch, not superseding it.  The patches are created with
superseding in the patch.wxs file, and are applied appropriately, just not
the ARP entry for the bundle:

ARP:

Product
-HotFix1
-HotFix2

instead of

Product
-HotFix2

Is there something extra I need to do to the second patch bundle to tell it
to supersede the first patch bundle? I use the same upgrade code for all
bundles, figuring that should not change.  The second patch bundle looks
exacly the same as the first, only the version number and patch files used
are different.

Here are my files:
Initial bundle:


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

  





  
  
  






  
  
  
  

  



Patch bundle:


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

  





  
  
  








  
  
  
  

  


Any help would be greatly appreciated.

Cheers,
Brian



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Managed-Bootstrapper-Second-Patch-does-not-supersede-first-Patch-tp7581779.html
Sent from the wix-users mailing list archive at Nabble.com.

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

Re: [WiX-users] Major Upgrade

[Chris Lord]

Chaitanya,

Best place to start is reading the documnetation.

First there is this is from the Wix Documentation
http://wix.sourceforge.net/manual-wix3/major_upgrade.htm

And then there is this from the excellent Wix Tutorial
http://wix.tramontana.co.hu/tutorial/upgrades-and-modularization

Beyond that, if you have a more specific question I am sure someone will 
be able to answer it.

Chris Lord
Attero Tech, LLC


-Original Message-
From: Chaitanya [mailto:chaita...@pointcross.com] 
Sent: Tuesday, November 06, 2012 9:19 AM
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] Major Upgrade

Hi,

Can anyone please help me in major upgrade..

Thanks,

Chaitanya.


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



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

[WiX-users] How to use FeaturesDlg

[Miller, Nick (GE Intelligent Platforms)]

I have 2 features.  One installs and configures a service.  The other
installs the database components.  The database components are optional.
So I try to use FeaturesDlg from Wix to collect whether or not to
install the feature.  This would work, except I also have a CustomAction
that should run only if the database components are installed.  How can
I put a condition in the CustomAction so it won't execute if the Feature
was deselected in the FeaturesDlg.

Here's an abbreviation of the .wxs code.






  


YES
YES

>





NOT Installed

NOT Installed
 <
NOT Installed

NOT Installed 








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

[WiX-users] Major Upgrade

[Chaitanya]

Hi,

Can anyone please help me in major upgrade..

Thanks,

Chaitanya.

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

[WiX-users] WIX Patches: Windows restores patched files and can't uninstall patch

[Farrukhw]

Hi Experts, 
I'm generating a patch using following code:


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




http://www.xyz.com/";
Classification="Update"
DisplayName="My Patch for 8.11.10.111"
 
/>


  

  
  






  


It generates my msp properly which I tried to install using following
command line:
* msiexec /p MyPatch.msp REINSTALLMODE=oums REINSTALL=ALL /qb
 And 
msiexec /p MyPatch.msp REINSTALL=ALL /qb
*
In both cases, it is first patch my application partially i.e. *.exe files
are patched, but not dlls. And it refused to get uninstalled from Add-Remove
programs applet.
*
**But when I launched my application, Windows Installer Dialog appeared and
it restored its patched files :(**
*

If I apply this patch again, it patched properly all files, but still
refusing to uninstall. 
*
**AllowRemoval="yes" doesn't seems to be working.***

So I'm quite confused with this behavior. 

Any help/suggestion would be really appreciated.

Thanks a bunch.





--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WIX-Patches-Windows-restores-patched-files-and-can-t-uninstall-patch-tp7581775.html
Sent from the wix-users mailing list archive at Nabble.com.

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

Re: [WiX-users] Setting the version number...

[Dirk Ziegelmeier]

See http://wix.sourceforge.net/manual-wix3/light.htm

Section "Package Properties"

Dirk



On Tue, Nov 6, 2012 at 12:39 PM, Goran  wrote:

> Has there been an improvement regarding this issue? We can use !bind
> without
> any problems from the msi wxs file, but I could not find a way to get
> version from the wxi (or from the bundle, if we are able to reference the
> version of msi package)?
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Setting-the-version-number-tp5942903p7581771.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> --
> LogMeIn Central: Instant, anywhere, Remote PC access and management.
> Stay in control, update software, and manage PCs from one command center
> Diagnose problems and improve visibility into emerging IT issues
> Automate, monitor and manage. Do more in less time with Central
> http://p.sf.net/sfu/logmein12331_d2d
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Wix Burn: How to customize MBA prerequisites

[vasjko]

Found the answer here: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/customizing-burn-prerequisite-boostrapper-image-in-theme-td7205852.html

06.11.2012 14:20, vasjko 
>Hi,
> 
> My MBA requires .Net framework to be installed. If .Net is not present the 
> standard dialog appears with .Net installation confimation.
> Is there any way to customize this confimation dialog or just change the logo 
> image for this dialog?
> 
> p.s. I've found that theme of this dialog is in mbapreq.thm file, is there 
> any way to set custom theme for prerequisites?
> 
> Thanks
> Vasyl
> 
> -- реклама ---
> Телефоны по самым лучшим ценам! 
> http://mobile.aukro.ua/
> 
> 
> --
> LogMeIn Central: Instant, anywhere, Remote PC access and management.
> Stay in control, update software, and manage PCs from one command center
> Diagnose problems and improve visibility into emerging IT issues
> Automate, monitor and manage. Do more in less time with Central
> http://p.sf.net/sfu/logmein12331_d2d
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users

-- реклама ---
Телефоны по самым лучшим ценам! 
http://mobile.aukro.ua/


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

[WiX-users] Wix Burn: How to customize MBA prerequisites

[vasjko]

Hi,

My MBA requires .Net framework to be installed. If .Net is not present the 
standard dialog appears with .Net installation confimation.
Is there any way to customize this confimation dialog or just change the logo 
image for this dialog?

p.s. I've found that theme of this dialog is in mbapreq.thm file, is there any 
way to set custom theme for prerequisites?

Thanks
Vasyl

-- реклама ---
Телефоны по самым лучшим ценам! 
http://mobile.aukro.ua/


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

Re: [WiX-users] Setting the version number...

[Goran]

Has there been an improvement regarding this issue? We can use !bind without
any problems from the msi wxs file, but I could not find a way to get
version from the wxi (or from the bundle, if we are able to reference the
version of msi package)?



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

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

[WiX-users] Error: The harvest type was not found in the list of loaded Heat extensions

[Donatas Vyzas]

Hi,

I am using Wix 3.6 with Visual Studio 2012. I am using this section in wixproj 
file to harvest required files from ASP.NET MVC application:




  
BasePath=%(ProjectReference.RootDir)%(ProjectReference.Directory);
  
%(ProjectReference.RootDir)%(ProjectReference.Directory)obj\$(Configuration)\Package\PackageTmp\
  
MySourcePath=%(ProjectReference.RootDir)%(ProjectReference.Directory)obj\$(Configuration)\Package\PackageTmp\


  

The above section is working fine in other three solutions, but fails in one 
solution with this particular error:
heat.exe(0,0): error HEAT0321: The harvest type was not found in the list of 
loaded Heat extensions.

The whole output (first few lines are from msdeploy packaging command):
22>  Sample script for deploying this package 
is generated at the following location:
22>C:\MVCStarterBase\BBCStartProject\Web\obj\Debug\Package\Web.deploy.cmd
22>For this sample script, you can change the deploy parameters by changing the 
following file:
22>C:\MVCStarterBase\BBCStartProject\Web\obj\Debug\Package\Web.SetParameters.xml
22> C:\Program Files (x86)\WiX Toolset v3.6\bin\Heat.exe dir 
C:\MVCStarterBase\BBCStartProject\Web\obj\Debug\Package\PackageTmp\ -cg 
Web_Project -dr INSTALLFOLDER -scom -sreg -srd -var var.BasePath -ag -sfrag 
-out Web.wxs
22>heat.exe(0,0): error HEAT0321: The harvest type was not found in the list of 
loaded Heat extensions.
22>Done building project "Setup.wixproj" -- FAILED.
22>
22>Build FAILED.

If I run the above command in cmd window, no error occurs (I just have to 
include quotes for heat.exe path). As I understand, "The harvest type was not 
found in the list of loaded Heat extensions" error occurs if I specify bad 
harvest type name, but "dir" is a legitimate harvest type name.

Any help is appreciated.

Regards,

Donatas Vyzas
Blue Bridge Code, UAB

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

[WiX-users] How to reference a preprocessor which is imported by the wixproj file?

[tetelee]

I know that if I define a preprocessor directly in the wixproj file, I can
use it in wxs file just like this: $(var.PROPERTYNAME). However, the problem
with this kind of preprocessor is it is Configuration/Platform specific. We
want to define a SW version number(which needs to be used in wxs file as
well as wixproj file for AfterBuild target) so it will easily become out of
sync(for example, build engineer only modifies the version for the current
Configuration/Platform combination in Visual Studio IDE, and it becomes
different from other combinations).

I got one suggestion from a thread. I created one txt file which only
defines a MSBuild project and inside this project, I defined a version
number property in the common PropertyGroup. After that, I imported this
project in my wixproj file. By doing this, my main wix project file can
reference this property(so that I can rename my output file using the
version number, which is my ultimate goal) and yet this property will not
show up in the project's properties window so we won't mess it up.

My txt file looks like this:


http://schemas.microsoft.com/developer/msbuild/2003";
ToolsVersion="4.0">

  1.2.3.4




And in my wixproj file, I import it by:
Import Project="Version.txt" />


So now in my project file I can reference just simply by $(Version). But if
I reference it inside my wxs file like this:



It is complaining about undefined preprocessor. So can anyone tell me how to
reference it correctly? Thanks!



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-reference-a-preprocessor-which-is-imported-by-the-wixproj-file-tp7581769.html
Sent from the wix-users mailing list archive at Nabble.com.

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