[wix-devs] Redesign RemotePayload

[Bob Arnson]

The binder grabs a bunch of data from MSIs in the chain, so you're not addressing a source-less RemotePayload implementation for MsiPackage here, right?

I'm -1 on requiring two elements for the most common use cases that today require one. I'm +1 on supporting the separation to allow for the mix you discuss for NetFx. ("Simple things should be simple, complex things should be possible.")

-----Original Message-----
From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf Of Sean Hall via wix-devs
Sent: Monday, 28 December, 2020 17:53
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Cc: Sean Hall <r.sean.hall at gmail.com>
Subject: [wix-devs] Redesign RemotePayload

I created a WIP to redesign RemotePayload at https://wixtoolset.org/development/wips/4183-redesign-remote-payload. It also gets rid of the magic behavior of using the first payload for the package payload if neither SourceFile nor RemotePayload is specified. I associated it with 4183 (Allow separation of package and payload in chain) since that's how I'm proposing to change it, but that's not really what I'm interested in if we want to do this differently. Any feedback?
____________________________________________________________________
WiX Toolset Developer Mailing List provided by FireGiant http://www.firegiant.com/