Viewers are cumulative
DesertJerry
14 Nov 2009
According to the Microsoft Office web site Viewers are cumulative. If a user downloads the latest; Excel, PowerPoint, Visio, Word, etc then prevous Viewers are no longer required.
So, would it not make things easier for AutoPatcher to only list the latest, in this case Office 2007 Viewers, and offer to remove/uninstall Office 2003 Viewers if detected on the same system? After all, even if the user is running Office XP they would only need the Office 2007 Viewers and they do not need the Office 2003, or earlier, Viewers.
So, would it not make things easier for AutoPatcher to only list the latest, in this case Office 2007 Viewers, and offer to remove/uninstall Office 2003 Viewers if detected on the same system? After all, even if the user is running Office XP they would only need the Office 2007 Viewers and they do not need the Office 2003, or earlier, Viewers.
dkdk_it
15 Nov 2009
DesertJerry, on 14 November 2009 - 08:17 PM, said:
According to the Microsoft Office web site Viewers are cumulative. If a user downloads the latest; Excel, PowerPoint, Visio, Word, etc then prevous Viewers are no longer required.
Quote
So, would it not make things easier for AutoPatcher to only list the latest, in this case Office 2007 Viewers, and offer to remove/uninstall Office 2003 Viewers if detected on the same system? After all, even if the user is running Office XP they would only need the Office 2007 Viewers and they do not need the Office 2003, or earlier, Viewers.
Bye.
click-click
15 Nov 2009
dkdk_it, on 15 November 2009 - 12:53 PM, said:
Of course...
No... actually, AutoPatcher doesn't remove old Office Viewer. I'm thinking to make a series of "remove modules" for each Office Viewers. I need a virtual machine to test it. Any days and I'll report results.
Bye.
No... actually, AutoPatcher doesn't remove old Office Viewer. I'm thinking to make a series of "remove modules" for each Office Viewers. I need a virtual machine to test it. Any days and I'll report results.
Bye.
How are you planning on flagging the remove modules?
Lets's say you run it and remove XYZ. What indication will the user have in the AP
listing that something is already removed? Will the entry be blue instead of black? How would
this kind of detection be accomplished?
dkdk_it
16 Nov 2009
click-click, on 15 November 2009 - 01:17 PM, said:
How are you planning on flagging the remove modules?
Lets's say you run it and remove XYZ. What indication will the user have in the AP
listing that something is already removed? Will the entry be blue instead of black? How would
this kind of detection be accomplished?
Lets's say you run it and remove XYZ. What indication will the user have in the AP
listing that something is already removed? Will the entry be blue instead of black? How would
this kind of detection be accomplished?
All right... my idea is not achievable.
So... old software removal will be an user's task!
