Read/Write permission on hosted ASP.NET sites

[Urs Eichmann]

We're developing a standard software application (ASP.NET) which will
run on servers of various ISP in a shared/hosted environment. With the
ISP I usually work with it is no problem to get a folder where the
ASP.NET account has read/write access. However, I'm concerned that this
might be a problem with other ISPs.

What do you think about it - is it usually a big deal to have a folder
with read/write access in a hosted environment?

Thanks for any help
Urs

[John Timney \(ASP.NET MVP\)]

Its common under a hosted application, your paying for the application
hosting after all. If they cant provide it without impacting other hosted
services then they dont know what they are doing.

--
Regards

John Timney
ASP.NET MVP
Microsoft Regional Director

"Urs Eichmann" <ur***@online.nospam> wrote in message
news:%2****************@TK2MSFTNGP15.phx.gbl...

We're developing a standard software application (ASP.NET) which will
run on servers of various ISP in a shared/hosted environment. With the
ISP I usually work with it is no problem to get a folder where the
ASP.NET account has read/write access. However, I'm concerned that this
might be a problem with other ISPs.

What do you think about it - is it usually a big deal to have a folder
with read/write access in a hosted environment?

Thanks for any help
Urs

[Steven Cheng[MSFT]]

Hi Urs,

I agree with John since most Web Host Provider will only give the users
restricted permissions so as to prevent the server from being damanged by
some unrestricted code or configuration( web.config). For example, some
host will not provide full trust level for asp.net web applications. And
folder's write/modify permission is also a common problem. If you're going
to deploy your application in a public host, I think we'd better contact
the host provider to see whether they can allow us to customize the web
space so as to ensure our web applicaiton running correclty.

Thanks,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)