How does one create an installer that will guarantee that no matter where a user chooses to save file to the files do not get removed during installation of a new build?
For instance if a user chooses to save files in the app folder, then during an update the files would be removed. How can a developer prevent this from occurring? We can set a default location BUT ultimately a user can choose to save information where ever they wish to. Seems like this is a problem? At least with an app I have currently. Or so it would seem. Is it truly possible to cover every possible location that a user MAY decide to save information to?
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Users should never save to the app folder. The app should default to Documents or Data as a fallback.
Sometimes, the impossible can become possible, if you're awesome!
So it is impossible to prevent loss of data if a user choose to go against convention?
“Be who you are and say what you feel because those who mind don't matter and those who matter don't mind.” Dr. Seuss
I've only see a user do this maybe twice before. It's completely counterintuitive. It's like saving something to Program Files (which will also generally cause your data to go bye bye). And there's a file with a warning in it right in the App directory.
Sometimes, the impossible can become possible, if you're awesome!
AS I expected, just trying to make sure I cover all bases on all my apps, did not want to be doing any thing htat was incorrect
“Be who you are and say what you feel because those who mind don't matter and those who matter don't mind.” Dr. Seuss
[MainDirectories]
RemoveAppDirectory=false
There is a reason why RemoveAppDirectory is true by default.
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1