G
Guest
I have an asp.net application using a multi-page wizard control that grabs
user selected files from a database and allows the user to configure
parameters using controls on the wizard pages. The resultant files are then
submitted for simulations.
When I attempt to navigate through the wizard an exception is thrown because
I am not permitted to overwrite a file in a read-only directory. When I
uncheck the read-only on the folder (subfolders included) my application is
able to overwrite a file once and then the next attempt is hit with an
exception.
I notice that my selection never stays fixed. I can uncheck the read-only
and accept the changes then come back and it will have reset itself. Right
now I am using a folder that resides inside my applications directory. I
kind of liked the idea that all of the applications temporary files could be
found within the applications directory.
I have had some difficulty setting folder attributes to allow applications
to write access to folders. I suspect this is because I am not following
common convention. I would like to be able to deploy my application with
all the correct directory permissions via a setup project or the publishing
tool. I would like to do so in a way that does not cause changes to be made
from my development laptop to my production machine.
I suspect I should probably be using the temporary directory and not
deploying a working directory explicitly. I would like to know the best
practice.
Any advice would be appreciated,
Thanks,
Jeff
user selected files from a database and allows the user to configure
parameters using controls on the wizard pages. The resultant files are then
submitted for simulations.
When I attempt to navigate through the wizard an exception is thrown because
I am not permitted to overwrite a file in a read-only directory. When I
uncheck the read-only on the folder (subfolders included) my application is
able to overwrite a file once and then the next attempt is hit with an
exception.
I notice that my selection never stays fixed. I can uncheck the read-only
and accept the changes then come back and it will have reset itself. Right
now I am using a folder that resides inside my applications directory. I
kind of liked the idea that all of the applications temporary files could be
found within the applications directory.
I have had some difficulty setting folder attributes to allow applications
to write access to folders. I suspect this is because I am not following
common convention. I would like to be able to deploy my application with
all the correct directory permissions via a setup project or the publishing
tool. I would like to do so in a way that does not cause changes to be made
from my development laptop to my production machine.
I suspect I should probably be using the temporary directory and not
deploying a working directory explicitly. I would like to know the best
practice.
Any advice would be appreciated,
Thanks,
Jeff