deployiment, security, aspnet

[=?Utf-8?B?cm9kY2hhcg==?=]

hey all,
i just deployed a simple web app that writes temp files to the application
root. i'm getting the following error:
ASP.NET is not authorized to access the requested resource. Consider
granting access rights to the resource to the ASP.NET request identity.

i can do what is says and it works but are there better ways to do this?
Best practices kind of stuff?

thanks,
rodchar

[Rad [Visual C# MVP]]

On Wed, 11 Apr 2007 07:30:04 -0700, rodchar wrote:

hey all,
i just deployed a simple web app that writes temp files to the application
root. i'm getting the following error:
ASP.NET is not authorized to access the requested resource. Consider
granting access rights to the resource to the ASP.NET request identity.

i can do what is says and it works but are there better ways to do this?
Best practices kind of stuff?

thanks,
rodchar

It is best to create a separate folder outside the root and grant access to
the asp.net process user to that. In this way if the application is somehow
compromised the damage that can be done would be limited.
--
Bits.Bytes
http://bytes.thinkersroom.com

[=?Utf-8?B?cm9kY2hhcg==?=]

does code access security allow you to write to a folder outside the
application root without having to grant ASPNET profile any rights?

"Rad [Visual C# MVP]" wrote:

On Wed, 11 Apr 2007 07:30:04 -0700, rodchar wrote:

hey all,
i just deployed a simple web app that writes temp files to the application
root. i'm getting the following error:
ASP.NET is not authorized to access the requested resource. Consider
granting access rights to the resource to the ASP.NET request identity.

i can do what is says and it works but are there better ways to do this?
Best practices kind of stuff?

thanks,
rodchar

It is best to create a separate folder outside the root and grant access to
the asp.net process user to that. In this way if the application is somehow
compromised the damage that can be done would be limited.
--
Bits.Bytes
http://bytes.thinkersroom.com