We have a folder where our app will be potentially reading, writing and creating/deleting files on, and while we can default to a safe location, we allow the user to select a different directory. How can we check if the directory they select is “safe”?
We’d like to not require admin elevation at runtime, and this path will be used for subsequent launches of the app, so it is not enough that we check whether our process is currently able to write to that location because it could be that the app is launched with admin privileges the first time (actually it does when launched by the installer because the installer runs elevated) and if they select a protected location, the next time they try to run the app, they won’t have access to the directory. Potentially GB’s of Persistent data is stored in this location so asking for a new location and moving the files isn’t an ideal solution.
Not only can any folder have any permissions, but they can change at any time, including between when you check a file and when you use it. So really, the only thing you can do is just use a file and handle the exception when it fails.