2015-11-02 38 views
1

我试图检测以前安装的捆绑软件的版本号是多少。然而,尽管它能够适当地检测到它会进行重大升级,但似乎并没有发现它。使用Wix Burn检测以前的捆绑版本

这是我的包XML的相关部分的样子:

<?define BUNDLE_UPGRADE_CODE=my_upgrade_code_guid?> 

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

    <Bundle UpgradeCode="$(var.BUNDLE_UPGRADE_CODE)" DisableModify="yes" ...> 

    <util:ProductSearch UpgradeCode="$(var.BUNDLE_UPGRADE_CODE)" Variable="PreviousVersion" /> 

    <BootstrapperApplicationRef ... /> 

    <Chain> 
     <ExePackage Id="my_exe_package".../> 
     <MsiPackage Id="my_msi_package" .../> 
    </Chain> 
    </Bundle> 
</Wix> 

的思想在于产品搜索应该使用升级代码检测到任何产品,并把版本号在变量PreviousVersion供以后使用。但是,刻录似乎无法检测到任何具有此升级代码的现有产品,而是始终将版本设置为“0.0.0.0”。以下是日志文件(有些编辑的清晰度)的相关部分:

...: Detect begin, 2 packages 
...: Product or related product not found: {my_upgrade_code_guid} 
...: Setting version variable 'PreviousVersion' to value '0.0.0.0' 
...: Detected related bundle: {previous_bundle_product_code}, type: Upgrade, scope: PerMachine, version: 1.0.0.0, operation: MajorUpgrade 
...: Detected related package: {previous_msi_product_code}, scope: PerMachine, version: 1.0.0.0, language: 0 operation: MajorUpgrade 
...: Detected package: my_exe_package, state: Absent, cached: Complete 
...: Detected package: my_msi_package, state: Absent, cached: None 
...: Detect complete, result: 0x0 
...: Plan begin, 2 packages, action: Install 
...: Skipping dependency registration on package with no dependency providers: my_exe_package 
... 
...: Planned package: my_exe_package, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: None, cache: No, uncache: No, dependency: None 
...: Planned package: my_msi_package, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register 
...: Planned related bundle: {previous_bundle_product_code}, type: Upgrade, default requested: Absent, ba requested: Absent, execute: Uninstall, rollback: Install, dependency: None 
...: Plan complete, result: 0x0 

如果我“手动”查询使用升级代码使用MsiEnumRelatedProducts我也找不到它的产品,而查询从升级代码msi包正确返回msi产品。

我的期望是否关闭?在这种情况下,我可以避开查询msi升级代码,因为该版本对我而言始终是相同的。我更感兴趣的是为什么这不起作用,因为我认为它会。

回答

3

ProductSearchMsiEnumRelatedProducts寻找MSI包,而不是烧伤包。自定义引导程序应用程序在其OnDetectRelatedBundle回调中获取现有捆绑软件的版本。