how to avoid repackaging Xps apps to Windows7?

If applications need to be packaged during the period that the customer is migrating from XP to Windows v7 is there any way to avoid having to do the package twice i.e. once in XP and once in Windows v7?

0 Comments   [ + ] Show comments

Answers (4)

Posted by: anonymous_9363 13 years ago
Red Belt
Yes. Any feature/component which might be different under W7 can be conditioned using the built-in OS property 'VersionNT'.
Posted by: Scazy 13 years ago
Senior Yellow Belt
VBScab, thank you for the quick answer .... and .... do you have any additinal information that might help me to work the problem out I mean links, best practises or whatever?
Posted by: ghosh.kunal 13 years ago
Senior Yellow Belt
When you try to deploy your XP production applications onto Vista or Windows 7, you need to do a lot of testing to make sure it works fine. I have not worked on Windows 7, but in Windows Vista, there are a whole lot of issues to look out for like Standard User Mode, File and Registry Virtualization, UAC etc.
Posted by: turbokitty 13 years ago
6th Degree Black Belt
What they're trying to say is:
- find out what's not working with the XP-comaptible MSI on W7 by testing and using the "Setup Analysis Tool" in the ACT Toolkit.
- build your MSI with feature conditions that will prevent XP-only bits going to a W7 box and vice-versa
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ