Allocate a new installer object for each nested installer so that changes in one nested installer object do not propagate into another
As a consequence of the above change, logic needs to be added for merging nested installer files into a single installer in case of NestedInstallerType: portable. This is done as:
If two (or more) nested portable installers have the same architecture and hash, the only difference would be of RelativeFilePath in both of them; so we merge the two installers
Display name of NestedInstallerFile for better clarity before a prompt asking for additional metadata or asking whether the package is a portable.
Refactor PortableCommandAliasIfApplicable() as we expect a single NestedInstallerFiles node for each installer inside the method body now.
I've listed some test URLs/manifests in the linked issue
371
Brief Description
NestedInstallerType: portable
. This is done as:I've listed some test URLs/manifests in the linked issue
Microsoft Reviewers: Open in CodeFlow