On a side note... It is critically important that you separate client's webs from each other, either by making them different virtual hosts (or assignimng them different IPs) or by making the web a virtual directory.
If they are not separate, from the viewpoint of IIS it's all one large application. The webs of different hosting clients will basically share the same runtime environment. Even if you restrict your client's file-level access to aspx files, these aspx-s can still easily read and write in Application and State objects and do evil things to other people's webs. -----Original Message----- From: Unmoderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Mike Andrews Sent: Wednesday, June 23, 2004 4:38 PM To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] Viewing error message remotely... PLEASE HELP.... Thank You. That worked!!!!! WAHOOO! Later, Mike -----Original Message----- From: Unmoderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Zecharya, Bar (FIRM) Sent: Wednesday, June 23, 2004 7:44 AM To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] Viewing error message remotely... PLEASE HELP.... [del] =================================== This list is hosted by DevelopMentor� http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
