Re: [WiX-users] R: Extend ProductSearch for working with Burn exe Package
The component (child) package can't add referrence to its main package
(parent).I have a component package that can be included in differents main
packages and when I make this package I don't know the possible packages that
could be include it.As this component package is released by a company and the
main package is released by another later.So I can only add a reference in the
main package to its component package.
I have tried to add a tag to the component package as I can get this BundleTag
from the main package when it detect the related bundle added in the main
package using the Upgrade code of the component package.In this case in the
main package I have added the RelatedBundle element using the UpgradeCode of
the component package.
I don't have understood if the RelatedBundle must be declared in the main
package using the UpgradeCode of the component package and using the mode
Detect or Addon?
Thanks.
Date: Tue, 19 May 2015 13:44:57 -0700
From: phogl...@rimage.com
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] R: Extend ProductSearch for working with Burn exe
Package
I have done some experiments with 'bob' (bundle of bundles). I may not have
it all figured out yet, but what I have done is this:
1) Add this to the parent bundle (I do this for every bundle, even when not
planning to do 'bob', so that in the future I can decide to create a related
Addon or Upgrade as needed.):
RelatedBundle Action='Detect' Id='RelatedBundle_GUID_For_This_Bundle' /
2) in the child bundle:
RelatedBundle Action='Detect'
Id='RelatedBundle_GUID_For_This_Bundle-different than above' /
RelatedBundle Action='Addon' Id='The above Parent bundle's
RelatedBundle_GUID' /
You may want to pick a different Action behavior from 'Addon'.
3) In the parent bundle I add the child bundle using an ExePackage like
this:
lt;Fragment
lt;!-- Contrary to the chm, DetectCondition must be specified when the
package is a Bundle. http://wixtoolset.org/issues/3693/ --
lt;PackageGroup Id=DistISsetup
lt;ExePackage Id=DistISsetup PerMachine=yes Permanent=no
Vital=yes Protocol=burn
Compressed=no
DownloadUrl=!(wix.myReleaseUrl){2}
Name=myChildBundle\myChildBundle.exe
SourceFile=myChildBundle.exe
InstallCondition=1=1
DetectCondition=1=0
lt;ExitCode Value=3010 Behavior=scheduleReboot /
lt;/ExePackage
lt;/PackageGroup
lt;/Fragment
When I added all of the event handlers that are related to Related Bundles
to my mba with logging messages (or debug) I found that the default
behaviour of Burn made it unnecessary for me to try and 'detect' whether the
child bundle is installed, as I indicated earlier. In the situation where I
do not use a RelatedBundle then I write a registry key to a known location
using the child bundle and use that info in the non-bundle parent to detect
the child bundle. But when using Burn for both bundles, so far for me, it
just works and I don't do anything to detect the child bundle. Thanks wix
devs!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/R-Extend-ProductSearch-for-working-with-Burn-exe-Package-tp7600279p7600372.html
Sent from the wix-users mailing list archive at Nabble.com.
--
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] R: Extend ProductSearch for working with Burn exe Package
I think that there may be different ways to approach RelatedBundle. I can only share the approach that I have been using. For every bundle I create I assign a relatedBundleGuid (which is different than the UpgradeCode for that bundle), along with a BundleTag: RelatedBundle Action='Detect' Id='$(var.ThisSetup_RelatedBundleGuid)' / Then at the later time, in the addon bundle I also designate the bundle that the addon should target. Here I am using the UpgradeCode of those other previously deployed Suite Bundles (in addition to also defining the above RelatedBundleGuid for this new Addon bundle, in the event that I need to target it with another related bundle). RelatedBundle Action='Addon' Id='$(var.SuiteBundleA_UpgradeCode)' / RelatedBundle Action='Addon' Id='$(var.SuiteBundleB_UpgradeCode)' / I hear your concern that the 'addon' is built without knowledge of the other bundles. Maybe someone else has some ideas for that issue. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/R-Extend-ProductSearch-for-working-with-Burn-exe-Package-tp7600279p7600454.html Sent from the wix-users mailing list archive at Nabble.com. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] R: Extend ProductSearch for working with Burn exe Package
So how can I detect if a Burn Bundle Exe package is installed, from another
bundle setup package?Can you provide some kind of example?I have seen the
RelatedBundle, but how can I use it to set the Detect condition of an exe
package?Thanks
From: jacob.hoo...@greenheck.com
To: wix-users@lists.sourceforge.net
Date: Sun, 17 May 2015 22:24:41 +
Subject: Re: [WiX-users] R: Extend ProductSearch for working with Burn exe
Package
I believe the confusion you are having stems from the usage of
util:ProductSearch inside your BA. That search would mirror the functionality
of the ProductSearch within a MSI, which only populates the Upgrade table in
the MSI with the Upgrade code of a MSI. Windows Installer only knows or
cares about Windows Installer based installs, so it's going to use Msi* API's
to query based on the upgrade code.
In short, util:ProductSearch is working as intended, but it isn't intended to
work with a bundle upgrade code.
-Original Message-
From: Marco Tognacci [mailto:mark...@live.it]
Sent: Sunday, May 17, 2015 4:10 PM
To: WiX - users
Subject: Re: [WiX-users] R: Extend ProductSearch for working with Burn exe
Package
Is there any mistake in my code or is there a bug in the util:ProductSearch
extension?How can I make this code working?Thanks
From: mark...@live.it
To: wix-users@lists.sourceforge.net
Date: Wed, 13 May 2015 01:02:45 +0200
Subject: Re: [WiX-users] R: Extend ProductSearch for working with
Burn exe Package
I have used util:ProductSearch to detect condition for my BurnPackage,
but it doesn't work, I use the last official release 3.9R2, the variable
assigned is equal to 2 (absent) even if the package is installed (I can
check manually the registry and I can find the UpgradeCode of the package
in a variable BundleUpgradeCode inside the installed product sections)
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;
Fragmentutil:ProductSearch
UpgradeCode={----}
Variable=MyBurnPackage_Installed Result=state /
PackageGroup Id=MyBurnPackageGroup ExePackage
Id=MyBurnPackage Cache=no Compressed=no Permanent=yes Vital=yes
SourceFile=..\Externals\MyBurnPackage.exe
Name=MyBurnPackage.exe
DetectCondition=MyBurnPackage_Installed 2//PackageGroup
/Fragment /Wix
Is there any mistake in my code or is there a bug in the
util:ProductSearch extension?How can I make this code working?Thanks
From: jocoo...@jackhenry.com
To: wix-users@lists.sourceforge.net
Date: Mon, 11 May 2015 12:52:57 +
Subject: Re: [WiX-users] R: Extend ProductSearch for working with
Burnexe Package
I think there is some confusion. 1) util:ProductSearch works with
Burn/Bundle. Whether it will do exactly what you want (as pointed out
by Phil) is another matter, but it does work. 2) the standard
ProductSearch is desiged to work in the WiX schema and is not suitable
for Burn/Bundle. 3) As is pointed out, there are very few limitations
if you write a custom BA. That would be my recommendation too.
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group |
Enterprise Notification Service Jack Henry Associates, Inc.® |
Lenexa, KS 66214 | Ext: 431050 |jocoo...@jackhenry.com
-Original Message-
From: Marco Tognacci [mailto:mark...@live.it]
Sent: Monday, May 11, 2015 2:06 AM
To: General discussion about the WiX toolset.
Subject: [WiX-users] R: Extend ProductSearch for working with Burn
exe Package
I have user the Extension ProductSearch from UtilExtension, and this
only works for msi packages, any other suggestion?
Inviata dal mio Windows Phone
Da: Phill Hoglandmailto:phogl...@rimage.com
Inviato: 09/05/2015 16:56
A:
wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge
.net
Oggetto: Re: [WiX-users] Extend ProductSearch for working with
Burn exe Package
ProductSearch element works only with msi package, is true of the
wix:ProductSearch (which can only be used in a msi context). However
in another thread to answer your question John suggested that you look
at util:ProductSearch (which is a Bundle related WixExtension).
I have not needed any of this when including a Burn bundle in a Burn
bundle.
As others have responded, look at the RelatedBundle support already in
Burn.
With regard to finding a Bundle from a non-wix application I have
previously detailed for you the approach that my legacy setup uses to
to find a child bundle (which relies on defining Bundle/@dep:
ProviderKey, getting the BundleId in the mba
Re: [WiX-users] R: Extend ProductSearch for working with Burn exe Package
I have done some experiments with 'bob' (bundle of bundles). I may not have
it all figured out yet, but what I have done is this:
1) Add this to the parent bundle (I do this for every bundle, even when not
planning to do 'bob', so that in the future I can decide to create a related
Addon or Upgrade as needed.):
RelatedBundle Action='Detect' Id='RelatedBundle_GUID_For_This_Bundle' /
2) in the child bundle:
RelatedBundle Action='Detect'
Id='RelatedBundle_GUID_For_This_Bundle-different than above' /
RelatedBundle Action='Addon' Id='The above Parent bundle's
RelatedBundle_GUID' /
You may want to pick a different Action behavior from 'Addon'.
3) In the parent bundle I add the child bundle using an ExePackage like
this:
lt;Fragment
lt;!-- Contrary to the chm, DetectCondition must be specified when the
package is a Bundle. http://wixtoolset.org/issues/3693/ --
lt;PackageGroup Id=DistISsetup
lt;ExePackage Id=DistISsetup PerMachine=yes Permanent=no
Vital=yes Protocol=burn
Compressed=no
DownloadUrl=!(wix.myReleaseUrl){2}
Name=myChildBundle\myChildBundle.exe
SourceFile=myChildBundle.exe
InstallCondition=1=1
DetectCondition=1=0
lt;ExitCode Value=3010 Behavior=scheduleReboot /
lt;/ExePackage
lt;/PackageGroup
lt;/Fragment
When I added all of the event handlers that are related to Related Bundles
to my mba with logging messages (or debug) I found that the default
behaviour of Burn made it unnecessary for me to try and 'detect' whether the
child bundle is installed, as I indicated earlier. In the situation where I
do not use a RelatedBundle then I write a registry key to a known location
using the child bundle and use that info in the non-bundle parent to detect
the child bundle. But when using Burn for both bundles, so far for me, it
just works and I don't do anything to detect the child bundle. Thanks wix
devs!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/R-Extend-ProductSearch-for-working-with-Burn-exe-Package-tp7600279p7600372.html
Sent from the wix-users mailing list archive at Nabble.com.
--
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] R: Extend ProductSearch for working with Burn exe Package
I believe the confusion you are having stems from the usage of
util:ProductSearch inside your BA. That search would mirror the functionality
of the ProductSearch within a MSI, which only populates the Upgrade table in
the MSI with the Upgrade code of a MSI. Windows Installer only knows or cares
about Windows Installer based installs, so it's going to use Msi* API's to
query based on the upgrade code.
In short, util:ProductSearch is working as intended, but it isn't intended to
work with a bundle upgrade code.
-Original Message-
From: Marco Tognacci [mailto:mark...@live.it]
Sent: Sunday, May 17, 2015 4:10 PM
To: WiX - users
Subject: Re: [WiX-users] R: Extend ProductSearch for working with Burn exe
Package
Is there any mistake in my code or is there a bug in the util:ProductSearch
extension?How can I make this code working?Thanks
From: mark...@live.it
To: wix-users@lists.sourceforge.net
Date: Wed, 13 May 2015 01:02:45 +0200
Subject: Re: [WiX-users] R: Extend ProductSearch for working with
Burn exe Package
I have used util:ProductSearch to detect condition for my BurnPackage, but
it doesn't work, I use the last official release 3.9R2, the variable
assigned is equal to 2 (absent) even if the package is installed (I can
check manually the registry and I can find the UpgradeCode of the package
in a variable BundleUpgradeCode inside the installed product sections)
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;Fragment
util:ProductSearch UpgradeCode={----}
Variable=MyBurnPackage_Installed Result=state / PackageGroup
Id=MyBurnPackageGroup ExePackage Id=MyBurnPackage Cache=no
Compressed=no Permanent=yes Vital=yes
SourceFile=..\Externals\MyBurnPackage.exe Name=MyBurnPackage.exe
DetectCondition=MyBurnPackage_Installed 2//PackageGroup
/Fragment /Wix
Is there any mistake in my code or is there a bug in the
util:ProductSearch extension?How can I make this code working?Thanks
From: jocoo...@jackhenry.com
To: wix-users@lists.sourceforge.net
Date: Mon, 11 May 2015 12:52:57 +
Subject: Re: [WiX-users] R: Extend ProductSearch for working with Burn
exe Package
I think there is some confusion. 1) util:ProductSearch works with
Burn/Bundle. Whether it will do exactly what you want (as pointed out by
Phil) is another matter, but it does work. 2) the standard ProductSearch
is desiged to work in the WiX schema and is not suitable for Burn/Bundle.
3) As is pointed out, there are very few limitations if you write a
custom BA. That would be my recommendation too.
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group |
Enterprise Notification Service Jack Henry Associates, Inc.® |
Lenexa, KS 66214 | Ext: 431050 |jocoo...@jackhenry.com
-Original Message-
From: Marco Tognacci [mailto:mark...@live.it]
Sent: Monday, May 11, 2015 2:06 AM
To: General discussion about the WiX toolset.
Subject: [WiX-users] R: Extend ProductSearch for working with Burn
exe Package
I have user the Extension ProductSearch from UtilExtension, and this only
works for msi packages, any other suggestion?
Inviata dal mio Windows Phone
Da: Phill Hoglandmailto:phogl...@rimage.com
Inviato: 09/05/2015 16:56
A:
wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge
.net
Oggetto: Re: [WiX-users] Extend ProductSearch for working with
Burn exe Package
ProductSearch element works only with msi package, is true of the
wix:ProductSearch (which can only be used in a msi context). However in
another thread to answer your question John suggested that you look at
util:ProductSearch (which is a Bundle related WixExtension).
I have not needed any of this when including a Burn bundle in a Burn
bundle.
As others have responded, look at the RelatedBundle support already in
Burn.
With regard to finding a Bundle from a non-wix application I have
previously detailed for you the approach that my legacy setup uses to to
find a child bundle (which relies on defining Bundle/@dep: ProviderKey,
getting the BundleId in the mba, and passing it to a chained MSI for
storage in a known location in the registry). Also in other threads on
this issue Jacob has provided another approach related to using dutil
functions.
I don't think that your current line of thinking, trying toextend a MSI
ProductSearch CA to work in Burn, is even possible.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Exte
nd-ProductSearch-for-working-with-Burn-exe-Package-tp7600271p76002
72.html Sent from the wix
Re: [WiX-users] R: Extend ProductSearch for working with Burn exe Package
Is there any mistake in my code or is there a bug in the util:ProductSearch
extension?How can I make this code working?Thanks
From: mark...@live.it
To: wix-users@lists.sourceforge.net
Date: Wed, 13 May 2015 01:02:45 +0200
Subject: Re: [WiX-users] R: Extend ProductSearch for working with Burn exe
Package
I have used util:ProductSearch to detect condition for my BurnPackage, but
it doesn't work, I use the last official release 3.9R2, the variable
assigned is equal to 2 (absent) even if the package is installed (I can
check manually the registry and I can find the UpgradeCode of the package
in a variable BundleUpgradeCode inside the installed product sections)
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;Fragment
util:ProductSearch UpgradeCode={----}
Variable=MyBurnPackage_Installed Result=state / PackageGroup
Id=MyBurnPackageGroup ExePackage Id=MyBurnPackage Cache=no
Compressed=no Permanent=yes Vital=yes
SourceFile=..\Externals\MyBurnPackage.exe Name=MyBurnPackage.exe
DetectCondition=MyBurnPackage_Installed 2//PackageGroup
/Fragment /Wix
Is there any mistake in my code or is there a bug in the util:ProductSearch
extension?How can I make this code working?Thanks
From: jocoo...@jackhenry.com
To: wix-users@lists.sourceforge.net
Date: Mon, 11 May 2015 12:52:57 +
Subject: Re: [WiX-users] R: Extend ProductSearch for working with Burn
exe Package
I think there is some confusion. 1) util:ProductSearch works with
Burn/Bundle. Whether it will do exactly what you want (as pointed out by
Phil) is another matter, but it does work. 2) the standard ProductSearch
is desiged to work in the WiX schema and is not suitable for Burn/Bundle.
3) As is pointed out, there are very few limitations if you write a
custom BA. That would be my recommendation too.
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise
Notification Service
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original Message-
From: Marco Tognacci [mailto:mark...@live.it]
Sent: Monday, May 11, 2015 2:06 AM
To: General discussion about the WiX toolset.
Subject: [WiX-users] R: Extend ProductSearch for working with Burn exe
Package
I have user the Extension ProductSearch from UtilExtension, and this only
works for msi packages, any other suggestion?
Inviata dal mio Windows Phone
Da: Phill Hoglandmailto:phogl...@rimage.com
Inviato: 09/05/2015 16:56
A: wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net
Oggetto: Re: [WiX-users] Extend ProductSearch for working with Burn exe
Package
ProductSearch element works only with msi package, is true of the
wix:ProductSearch (which can only be used in a msi context). However in
another thread to answer your question John suggested that you look at
util:ProductSearch (which is a Bundle related WixExtension).
I have not needed any of this when including a Burn bundle in a Burn
bundle.
As others have responded, look at the RelatedBundle support already in
Burn.
With regard to finding a Bundle from a non-wix application I have
previously detailed for you the approach that my legacy setup uses to to
find a child bundle (which relies on defining Bundle/@dep: ProviderKey,
getting the BundleId in the mba, and passing it to a chained MSI for
storage in a known location in the registry). Also in other threads on
this issue Jacob has provided another approach related to using dutil
functions.
I don't think that your current line of thinking, trying toextend a MSI
ProductSearch CA to work in Burn, is even possible.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Extend-ProductSearch-for-working-with-Burn-exe-Package-tp7600271p7600272.html
Sent from the wix-users mailing list archive at Nabble.com.
--
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
One dashboard
Re: [WiX-users] R: Extend ProductSearch for working with Burn exe Package
Is there any mistake in my code or is there a bug in the util:ProductSearch
extension?How can I make this code working?Thanks
From: mark...@live.it
To: wix-users@lists.sourceforge.net
Date: Wed, 13 May 2015 01:02:45 +0200
Subject: Re: [WiX-users] R: Extend ProductSearch for working with Burn exe
Package
I have used util:ProductSearch to detect condition for my BurnPackage, but it
doesn't work, I use the last official release 3.9R2, the variable assigned is
equal to 2 (absent) even if the package is installed (I can check manually
the registry and I can find the UpgradeCode of the package in a variable
BundleUpgradeCode inside the installed product sections)
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;Fragment
util:ProductSearch UpgradeCode={----}
Variable=MyBurnPackage_Installed Result=state / PackageGroup
Id=MyBurnPackageGroup ExePackage Id=MyBurnPackage Cache=no
Compressed=no Permanent=yes Vital=yes
SourceFile=..\Externals\MyBurnPackage.exe Name=MyBurnPackage.exe
DetectCondition=MyBurnPackage_Installed 2//PackageGroup
/Fragment /Wix
Is there any mistake in my code or is there a bug in the util:ProductSearch
extension?How can I make this code working?Thanks
From: jocoo...@jackhenry.com
To: wix-users@lists.sourceforge.net
Date: Mon, 11 May 2015 12:52:57 +
Subject: Re: [WiX-users] R: Extend ProductSearch for working with Burn
exe Package
I think there is some confusion. 1) util:ProductSearch works with
Burn/Bundle. Whether it will do exactly what you want (as pointed out by
Phil) is another matter, but it does work. 2) the standard ProductSearch
is desiged to work in the WiX schema and is not suitable for Burn/Bundle.
3) As is pointed out, there are very few limitations if you write a custom
BA. That would be my recommendation too.
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise
Notification Service
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original Message-
From: Marco Tognacci [mailto:mark...@live.it]
Sent: Monday, May 11, 2015 2:06 AM
To: General discussion about the WiX toolset.
Subject: [WiX-users] R: Extend ProductSearch for working with Burn exe
Package
I have user the Extension ProductSearch from UtilExtension, and this only
works for msi packages, any other suggestion?
Inviata dal mio Windows Phone
Da: Phill Hoglandmailto:phogl...@rimage.com
Inviato: 09/05/2015 16:56
A: wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net
Oggetto: Re: [WiX-users] Extend ProductSearch for working with Burn exe
Package
ProductSearch element works only with msi package, is true of the
wix:ProductSearch (which can only be used in a msi context). However in
another thread to answer your question John suggested that you look at
util:ProductSearch (which is a Bundle related WixExtension).
I have not needed any of this when including a Burn bundle in a Burn bundle.
As others have responded, look at the RelatedBundle support already in Burn.
With regard to finding a Bundle from a non-wix application I have
previously detailed for you the approach that my legacy setup uses to to
find a child bundle (which relies on defining Bundle/@dep: ProviderKey,
getting the BundleId in the mba, and passing it to a chained MSI for
storage in a known location in the registry). Also in other threads on
this issue Jacob has provided another approach related to using dutil
functions.
I don't think that your current line of thinking, trying toextend a MSI
ProductSearch CA to work in Burn, is even possible.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Extend-ProductSearch-for-working-with-Burn-exe-Package-tp7600271p7600272.html
Sent from the wix-users mailing list archive at Nabble.com.
--
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications Performance
metrics, stats and reports that give you Actionable Insights Deep dive
visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support
Re: [WiX-users] R: Extend ProductSearch for working with Burn exe Package
I have used util:ProductSearch to detect condition for my BurnPackage, but it
doesn't work, I use the last official release 3.9R2, the variable assigned is
equal to 2 (absent) even if the package is installed (I can check manually the
registry and I can find the UpgradeCode of the package in a variable
BundleUpgradeCode inside the installed product sections)
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;Fragment
util:ProductSearch UpgradeCode={----}
Variable=MyBurnPackage_Installed Result=state / PackageGroup
Id=MyBurnPackageGroup ExePackage Id=MyBurnPackage Cache=no
Compressed=no Permanent=yes Vital=yes
SourceFile=..\Externals\MyBurnPackage.exe Name=MyBurnPackage.exe
DetectCondition=MyBurnPackage_Installed 2//PackageGroup /Fragment
/Wix
Is there any mistake in my code or is there a bug in the util:ProductSearch
extension?How can I make this code working?Thanks
From: jocoo...@jackhenry.com
To: wix-users@lists.sourceforge.net
Date: Mon, 11 May 2015 12:52:57 +
Subject: Re: [WiX-users] R: Extend ProductSearch for working with Burn
exe Package
I think there is some confusion. 1) util:ProductSearch works with
Burn/Bundle. Whether it will do exactly what you want (as pointed out by
Phil) is another matter, but it does work. 2) the standard ProductSearch is
desiged to work in the WiX schema and is not suitable for Burn/Bundle. 3) As
is pointed out, there are very few limitations if you write a custom BA.
That would be my recommendation too.
--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise
Notification Service
Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050
|jocoo...@jackhenry.com
-Original Message-
From: Marco Tognacci [mailto:mark...@live.it]
Sent: Monday, May 11, 2015 2:06 AM
To: General discussion about the WiX toolset.
Subject: [WiX-users] R: Extend ProductSearch for working with Burn exe Package
I have user the Extension ProductSearch from UtilExtension, and this only
works for msi packages, any other suggestion?
Inviata dal mio Windows Phone
Da: Phill Hoglandmailto:phogl...@rimage.com
Inviato: 09/05/2015 16:56
A: wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net
Oggetto: Re: [WiX-users] Extend ProductSearch for working with Burn exe
Package
ProductSearch element works only with msi package, is true of the
wix:ProductSearch (which can only be used in a msi context). However in
another thread to answer your question John suggested that you look at
util:ProductSearch (which is a Bundle related WixExtension).
I have not needed any of this when including a Burn bundle in a Burn bundle.
As others have responded, look at the RelatedBundle support already in Burn.
With regard to finding a Bundle from a non-wix application I have previously
detailed for you the approach that my legacy setup uses to to find a child
bundle (which relies on defining Bundle/@dep: ProviderKey, getting the
BundleId in the mba, and passing it to a chained MSI for storage in a known
location in the registry). Also in other threads on this issue Jacob has
provided another approach related to using dutil functions.
I don't think that your current line of thinking, trying toextend a MSI
ProductSearch CA to work in Burn, is even possible.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Extend-ProductSearch-for-working-with-Burn-exe-Package-tp7600271p7600272.html
Sent from the wix-users mailing list archive at Nabble.com.
--
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications Performance
metrics, stats and reports that give you Actionable Insights Deep dive
visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications Performance
metrics, stats and reports that give you Actionable Insights Deep dive
visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
NOTICE: This electronic mail
Re: [WiX-users] R: Extend ProductSearch for working with Burn exe Package
I think there is some confusion. 1) util:ProductSearch works with Burn/Bundle. Whether it will do exactly what you want (as pointed out by Phil) is another matter, but it does work. 2) the standard ProductSearch is desiged to work in the WiX schema and is not suitable for Burn/Bundle. 3) As is pointed out, there are very few limitations if you write a custom BA. That would be my recommendation too. -- John Merryweather Cooper Senior Software Engineer | Integration Development Group | Enterprise Notification Service Jack Henry Associates, Inc.® | Lenexa, KS 66214 | Ext: 431050 |jocoo...@jackhenry.com -Original Message- From: Marco Tognacci [mailto:mark...@live.it] Sent: Monday, May 11, 2015 2:06 AM To: General discussion about the WiX toolset. Subject: [WiX-users] R: Extend ProductSearch for working with Burn exe Package I have user the Extension ProductSearch from UtilExtension, and this only works for msi packages, any other suggestion? Inviata dal mio Windows Phone Da: Phill Hoglandmailto:phogl...@rimage.com Inviato: 09/05/2015 16:56 A: wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net Oggetto: Re: [WiX-users] Extend ProductSearch for working with Burn exe Package ProductSearch element works only with msi package, is true of the wix:ProductSearch (which can only be used in a msi context). However in another thread to answer your question John suggested that you look at util:ProductSearch (which is a Bundle related WixExtension). I have not needed any of this when including a Burn bundle in a Burn bundle. As others have responded, look at the RelatedBundle support already in Burn. With regard to finding a Bundle from a non-wix application I have previously detailed for you the approach that my legacy setup uses to to find a child bundle (which relies on defining Bundle/@dep: ProviderKey, getting the BundleId in the mba, and passing it to a chained MSI for storage in a known location in the registry). Also in other threads on this issue Jacob has provided another approach related to using dutil functions. I don't think that your current line of thinking, trying toextend a MSI ProductSearch CA to work in Burn, is even possible. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Extend-ProductSearch-for-working-with-Burn-exe-Package-tp7600271p7600272.html Sent from the wix-users mailing list archive at Nabble.com. -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
