G
Guest
I need to prevent files from being manipulated (e.g., renamed or moved) by external applications (e.g., Windows Explorer) while my app is working with the files. The length of time that my app works with the files is determined by the user (i.e., the user manually opens and closes the files). A bonus would be to prevent external applications from opening the files, but that is not required. Would using a FileStream do what I need to do, assuming that I wouldn't call the FileStream.Close method until the user chooses to close the file? Is there a better technique?
Note that the files are typically between 2 - 10MB and they can be written and/or renamed multiple times while the user is working with them. Also, I use binary serialization to save the files.
Thanks,
Lance
Note that the files are typically between 2 - 10MB and they can be written and/or renamed multiple times while the user is working with them. Also, I use binary serialization to save the files.
Thanks,
Lance