[wix-devs] Testing late-bound properties

[Sean Hall]

Sorry if I confused you. I pointed them out to explain why the collision
detection needs to be done later, you don't have to actually test them.
Those are broken right now: https://github.com/wixtoolset/issues/issues/6431

I'm not sure if ProductCode is a supported package bind variable. That
might be a separate issue if it's really not generating any warning or
errors and staying unresolved.

On Sat, Apr 17, 2021 at 12:45 AM Ron Martin via wix-devs <
wix-devs at lists.wixtoolset.org> wrote:

> I'm having trouble coming up with a good scenario for testing late-bound
> "properties". I'm trying to come up with an expression that requires
> late binding to complete the definition of a CacheId. At the moment, I'm
> using:
>
> <?xml version="1.0" encoding="utf-8"?>
> <Wix xmlns="http://wixtoolset.org/schemas/v4/wxs">
>      <Fragment>
>          <PackageGroup Id="BundlePackages">
>              <ExePackage Id="Manual1" SourceFile="test.msi"
> Name="manual1\test.msi" DetectCondition="anything"
> CacheId="!(bind.ProductCode.test.msi)" />
>              <ExePackage Id="Manual2" SourceFile="test.msi"
> Name="manual2\test.msi" DetectCondition="anything"
> CacheId="!(bind.ProductCode.test.msi)" />
>          </PackageGroup>
>      </Fragment>
> </Wix>
>
> This is late bound, but the symbol resolution fails. It does not
> generate an error or a warning, but it remains in its unresolved state.
> The test.msi file appears to be referenced, but not opened, according to
> ProcMon.
>
> I can send more code if that will help. If my approach is wrong, I'd
> appreciate your suggestions. There really is a paucity of good examples
> that I can find via Google.
>
> Thanks.
>
> Ron
>
> ____________________________________________________________________
> WiX Toolset Developer Mailing List provided by FireGiant
> http://www.firegiant.com/
>