NewsArchive
08-08-2011, 04:11 AM
Just finished a chat with some folks about uninstalls. The way I have it setup
now is that anything the installer put on the system, it removes. And I do mean
everything. Per design, no issue.
The bone of contention in some minds is that I have a folder for demo data (always
in the same place) and live data (default location or user chosen during install).
After uninstall, if the program created the live data files (they are not
installed on purpose), empty or not, these files are left behind by design. The
idea is that live data belongs to a customer. Some think it should be removed,
others don't.
The reason for uninstalling live data is the assumption the user no longer wants
the package, therefore the live data is not wanted either. On the flip side, the
data belongs to the customer, there is sensitive information in these files.
Also, if a user wants to uninstall then re-install, they will have to start over
from scratch, re-entering all that data.
A possible solution to address both sides is during the uninstall, ask the user if
they wish to wipe out data they created (default to No). If they say yes, then an
are you sure message, with the default button set to No. This means in order to
blow away their data, they have to deliberately answer Yes twice.
Anyone use a modified uninstall like this?
--
Russell B. Eggen
www.radfusion.com
now is that anything the installer put on the system, it removes. And I do mean
everything. Per design, no issue.
The bone of contention in some minds is that I have a folder for demo data (always
in the same place) and live data (default location or user chosen during install).
After uninstall, if the program created the live data files (they are not
installed on purpose), empty or not, these files are left behind by design. The
idea is that live data belongs to a customer. Some think it should be removed,
others don't.
The reason for uninstalling live data is the assumption the user no longer wants
the package, therefore the live data is not wanted either. On the flip side, the
data belongs to the customer, there is sensitive information in these files.
Also, if a user wants to uninstall then re-install, they will have to start over
from scratch, re-entering all that data.
A possible solution to address both sides is during the uninstall, ask the user if
they wish to wipe out data they created (default to No). If they say yes, then an
are you sure message, with the default button set to No. This means in order to
blow away their data, they have to deliberately answer Yes twice.
Anyone use a modified uninstall like this?
--
Russell B. Eggen
www.radfusion.com