G
Guest
I wrote an ASP.NET script that accesses a database on a server I don’t host
myself. I understand that IIS needs to give ASP.NET permission to access
every single file. It’s not enough to give read/write access to the folder
the file (or files) is stored in. This would mean that whenever I write a new
script, doing something with a new file, I have to call my hosing provider
and have them change the permissions (i. e. add the permission for the new
file). If I’m right with this statement, this does not seem very efficient to
me and makes me question the whole ASP.NET thing. Am I right?
myself. I understand that IIS needs to give ASP.NET permission to access
every single file. It’s not enough to give read/write access to the folder
the file (or files) is stored in. This would mean that whenever I write a new
script, doing something with a new file, I have to call my hosing provider
and have them change the permissions (i. e. add the permission for the new
file). If I’m right with this statement, this does not seem very efficient to
me and makes me question the whole ASP.NET thing. Am I right?