Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MsiPropertyGroup, MsiPropertyGroupRef, and MsiPropertyRef. #4531

Closed
wixbot opened this issue Sep 19, 2014 · 2 comments
Closed

MsiPropertyGroup, MsiPropertyGroupRef, and MsiPropertyRef. #4531

wixbot opened this issue Sep 19, 2014 · 2 comments

Comments

@wixbot
Copy link

wixbot commented Sep 19, 2014

Use Case 1: Identical copies of MsiProperty elements, such as the following, are used in many different Fragments which include MsiPackage elements. (I assume that this applies to any MxxPackage.). In some cases there are groups of MsiProperty elements which are copied and used for similar types of applications (services) defined in multiple MsiPackages.

Use Case 2: Based on advice to avoid using MSI language transforms with Burn driven deployment, I have multiple MsiPackage fragments which are identical, except for the localized path to the msi package (and a localized specific identifier). The MsiProperties are repeated identically in each MsiPackage fragment.

In the above situations it seems like creating groups of MsiProperty(s) and using references to those groups, or a reference to a single MsiProperty used in many places would be a useful construct.

Originally opened by phogland

@wixbot wixbot added this to the v4.x milestone Dec 20, 2015
@barnson
Copy link
Member

barnson commented Mar 21, 2016

Duplicate of wixtoolset/issues/issues#3276.

@barnson barnson closed this as completed Mar 21, 2016
@barnson
Copy link
Member

barnson commented Mar 21, 2016

#3276

@rseanhall rseanhall removed this from the v4.x milestone May 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants