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

Figure out how to handle .NET 4.x detection properties #4662

Closed
wixbot opened this issue Jan 26, 2015 · 3 comments
Closed

Figure out how to handle .NET 4.x detection properties #4662

wixbot opened this issue Jan 26, 2015 · 3 comments
Assignees
Milestone

Comments

@wixbot
Copy link

wixbot commented Jan 26, 2015

.NET 4.5, 4.5.1, 4.5.2, and 4.6 are all in-place updates and have the same detection methods and therefore have the same detection property names (i.e., NETFRAMEWORK45__). Do we want to duplicate them for 4.6 as NETFRAMEWORK46__? Do we want to do so in the future for a theoretical .NET 4.7? 4.10? Add NETFRAMEWORK4X_*?

Brain trust, activate!

Originally opened by wixbot

@wixbot
Copy link
Author

wixbot commented Jan 27, 2015

Add a way of identifying each version "or later" -- e.g., NETFRAMEWORK46ORLATER -- and verify NETFRAMEWORK40FULL works for all 4.x.

AssignedTo set to bobarnson

@wixbot
Copy link
Author

wixbot commented Feb 2, 2015

wixtoolset/wix3#199

Originally posted by barnson

@wixbot
Copy link
Author

wixbot commented Feb 4, 2015

f223fe9a7c6f2bf5e2f62b8ef67dc37201e68974

Originally posted by barnson
Resolution set to fixed
Status changed from Open to Resolved

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

2 participants