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

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Yes. Any feature/component which might be different under W7 can be conditioned using the built-in OS property 'VersionNT'.
Answered 10/14/2009 by: VBScab
Red Belt

Please log in to comment
0
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?
Answered 10/14/2009 by: Scazy
Senior Yellow Belt

Please log in to comment
0
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.
Answered 10/14/2009 by: ghosh.kunal
Senior Yellow Belt

Please log in to comment
0
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
Answered 10/14/2009 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity