[wix-devs] BundleCustomData and WixCop

[Rob Mensching]

Yeah, any elements that require linking are probably out of scope for conversion. I haven't seen enough examples of the new BootstrapperApplicationData usage to have any better ideas.

-----Original Message-----
From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf Of Sean Hall via wix-devs
Sent: Saturday, June 20, 2020 10:22 PM
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Cc: Sean Hall <r.sean.hall at gmail.com>
Subject: Re: [wix-devs] BundleCustomData and WixCop

I have another problem, there's no way for WixCop ("wix convert"?) to know whether a CustomTable element was for BootstrapperApplicationData unless it's the element that defined the table.

On Sat, Jun 20, 2020 at 2:54 AM Rob Mensching <rob at firegiant.com> wrote:

> v3 BootstrapperApplicationData should be migrated to the new way of 
> defining "bundle data" in v4.
>
> Unreal can be treated as a new concept with no conversion path from v3.
>
>
> -----Original Message-----
> From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf Of 
> Sean Hall via wix-devs
> Sent: Friday, June 19, 2020 4:36 AM
> To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
> Cc: Sean Hall <r.sean.hall at gmail.com>
> Subject: [wix-devs] BundleCustomData and WixCop
>
> I updated the WIP to match the change from Burn to Bundle, added the 
> ExtensionId attribute for Type=BundleExtension, and removed the 
> removal of CustomTable/@Unreal.
>
> Since we're not getting rid of CustomTable/@Unreal, the migration of 
> v3's CustomTable/@BootstrapperApplicationData is now ambiguous. What 
> is WixCop supposed to do?
> ____________________________________________________________________
> WiX Toolset Developer Mailing List provided by FireGiant 
> http://www.firegiant.com/
>
____________________________________________________________________
WiX Toolset Developer Mailing List provided by FireGiant http://www.firegiant.com/