Are you Creating Packages for Vista ?
I've seen a few packaging jobs come along lately with the requirement of "experience creating packages for Vista"
I thought the majority of companies had skipped vista and were holding out for Windows 7 which according to the email I got with the Win 7 RC1 download link may have a final public release version in 3-5 months.
I'd like to know if you are currently creating packages for Vista in your IT organization or if your company is planning on deploying vista in the next few months.
Thanks for your poll vote and replies
I thought the majority of companies had skipped vista and were holding out for Windows 7 which according to the email I got with the Win 7 RC1 download link may have a final public release version in 3-5 months.
I'd like to know if you are currently creating packages for Vista in your IT organization or if your company is planning on deploying vista in the next few months.
Thanks for your poll vote and replies
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
kkaminsk
14 years ago
Yep we are, had to get off Win2K because we cannot get new hardware with Win2K drivers and Win7 was too far off. Also you have to look at it from a risk perspective, do you want to be packaging on a beta OS in anticipation of the release date or go with something that has at least one service pack behind it?
Posted by:
nheim
14 years ago
Hi folks,
yes, we create all our packages for Vista and XP.
Normally, this is no big deal, you just have to follow the guidelines for MSI.
Most important: Don't run a custom action, which changes the system, outside of the script.
Regards, Nick
yes, we create all our packages for Vista and XP.
Normally, this is no big deal, you just have to follow the guidelines for MSI.
Most important: Don't run a custom action, which changes the system, outside of the script.
Regards, Nick
Posted by:
LB3
14 years ago
Thanks for your replies and info so far...
I haven't had the chance to package for vista yet just XP mostly the last few years.
I haven't had the chance to package for vista yet just XP mostly the last few years.
Posted by:
turbokitty
14 years ago
ORIGINAL: nheim
Most important: Don't run a custom action, which changes the system, outside of the script.
Could you clarify this statement please?
Posted by:
nheim
14 years ago
Hi TK,
make changes outside of the script has never been a good one.
But in Vista, things like this can trigger UAC or even worse, make use of virtual store.
In my experience, follow the guidelines and there are not more problems as with XP/W2k.
Regards, Nick
make changes outside of the script has never been a good one.
But in Vista, things like this can trigger UAC or even worse, make use of virtual store.
In my experience, follow the guidelines and there are not more problems as with XP/W2k.
Regards, Nick
Posted by:
AngelD
14 years ago
In MSI-language that would mean "outside of script" = immediate execution
The guidelines has always been; system changes should always be made in deferred execution.
The guidelines has always been; system changes should always be made in deferred execution.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.