I'm not in the habit of replying to myself, but it probably would make more sense to support Upgrade and UpgradeVersion from within a burn Bundle. Having explicit properties for the Language/Version would prevent the need for fragile string parsing, and simply returning the ProductCode would allow us to query for further information in a different element or UX.
-----Original Message----- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Friday, October 14, 2011 10:24 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn in 3.6 3. I asked about a burn custom action as that would allow me to inject my code which I currently have hacked into the Engine for finding related products. I'm looking for an elegant solution for detecting the presence of future installers (Ex: Visual C++ Runtime). I'm trying to prevent attempting to install older versions of a product when a newer version is all ready installed. 4. I realize there isn't an array implementation in the BURN_VARIANT, but wouldn't it be possible to provide search parameters such as ProductVersion>=1.2.3 and a parameter for output variable name and property. Ex: <MsiRelatedProductSearch Id="{1F4F1D2A-D9DA-32CF-9909-48485DA06DD5}" Property="VCR2010_Version" Condition="ProductVersion>=1.2.3" Result="version, language, or productcode" /> This would be somewhat of a hybrid implementation between ProductSearch and UpgradeVersion. A custom action option would allow me to encapsulate any proposed new logic without fighting for it to be added to the core engine or having to constantly merge my changes into the latest codebase. -----Original Message----- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Thursday, October 13, 2011 9:56 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn in 3.6 1. Documentation in Burn is lacking. I personally still tend to optimize fixing bugs over writing documentation. If find this to be optimal because fixing bugs sometimes changes what the documentation would say. <smile/> You might argue that lack of documentation prevents people from finding bugs (because they can't even get started with Burn) and I wouldn't disagree. It's all about hours in the day. <smile/> 2. We definitely should get a set of .wixlibs that wrap up all that information. There have been suggestions in the past about sucking up the "predefined templates" from VS and getting that all in Burn. I think that sounds like a great idea. <smile/> 3. CustomActions can affect a great many different parts of the install. Burn is extensible in many directions but not all. If you can be more specific about the examples you are interested in, I can probably answer whether they are supported in Burn now. 4. Searching for UpgradeCode is difficult because it returns an array. Burn Variables do not support arrays. That's why this feature request is difficult. 5. See #1. <smile/> Others may have better answer right now... of course, documentation will improve as there are fewer bugs. On Thu, Oct 13, 2011 at 11:49 AM, Hoover, Jacob <jacob.hoo...@greenheck.com>wrote: > I know 3.6 is still under development, but documentation on Burn is > few and far between. I've long wondered if wouldn't be nice to have a > dumping spot to put some predefined templates. Ex: There are a lot of > common prerequisites (.Net frameworks, Visual C++ runtimes, SQL Server > CE, etc) that a lot of applications require. For Visual Studio, there > are predefined templates for their bootstrapper. While it is possible > for everyone to translate these templates to suite their needs, I think > it would be helpful to have a standard translation for each. > > > > In Wix, for an installer there is a sequence table that can be used to > invoke custom logic at various points in time. There is also the > concept of a CustomAction which allows you to write and execute custom > code. Does burn have any similar abstraction? (I'm betting this will > point me to a custom UX, but I am not certain if logic like > FindRelatedProduct should exist in a UX or within the base engine.) > > > > Another issue I am running into is a documented feature request > http://sourceforge.net/tracker/?func=detail&aid=3300401&group_id=105970&; > atid=642717<http://sourceforge.net/tracker/?func=detail&aid=3300401&grou p_id=105970&%0Aatid=642717>. > In the case of some installers, we only want to install > prerequisites if a product of version X or higher is not installed. Is > it purely a timing thing as to why a feature like this (at least scoped > to burn) is not in existence? For burn, I've hacked in a prototype into > the engine's search.cpp, but due to the lack of documentation I haven't > gotten a clear understanding on what all else needs to be modified to > get the burn compiler to accept a new element and to properly embed the > XML into the burn output. > > > > Finally, has anyone found any good resources for documentation on Burn > and the changes happening in Wix 3.6? > > > > Thanks, > > Jacob > > > ------------------------------------------------------------------------ ------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC ------------------------------------------------------------------------ ------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------ ------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
