LinkBack URL
About LinkBacks
Reply With QuoteIn my opinion, you should upgrade. Changing the package and redeploying (at least for me) hasn't been the most reliable way to do it.
100+ Helpful Posts!
50+ Helpful Posts
I have a software package that installs a .dll and makes some registry changes. When I develop an upgraded version of the package, what is the best way to deploy the upgrade?
Should I create a new package and upgrade the existing package with it?
Should I overwrite the existing package with the new one and select the redeploy option?
seems like either method is just as effective.
100+ Helpful Posts!
50+ Helpful Posts
In my opinion, you should upgrade. Changing the package and redeploying (at least for me) hasn't been the most reliable way to do it.
100+ Helpful Posts!
50+ Helpful Posts
hmmmmm....thanks for the reply. Interesting that msoft recommends re-deploy (KB816102), or appears to do so. I'm not 100% confident with microsoft recommendations however ;-)
Any thoughts on why you would upgrade? Have you run into specific problems?
100+ Helpful Posts!
50+ Helpful Posts
The experience I delt with had an MST (Transform) with the package so maybe that is why I had issues. I modified the transform file for an Office installation and tried to Redeploy it but it was hit and miss on some of the workstations. In your case it's probably safe to Redeploy as it's not a very complex install to start with.
Posting Permissions