You can make com components.  Inside of mts, com+, com services or whatever
they are calling it today, there are roles.  I am not sure the file system
object is going to help you unless you hide the 'secret' code from the
developers.  And that trick will probably never work.

Stacy


----- Original Message -----
From: "Ken Schaefer" <ken@a...>
To: "Security_asp" <security_asp@p...>
Sent: Wednesday, February 21, 2001 5:50 AM
Subject: Re: FileSystemObject and multiple developers


> Can you elaborate?
>
> Cheers
> Ken
>
> ----- Original Message -----
> From: "Stacy Draper" <sodapop@n...>
> To: "Security_asp" <security_asp@p...>
> Sent: Wednesday, February 21, 2001 6:11 PM
> Subject: Re: FileSystemObject and multiple developers
>
>
> > If your developing in such in an environment your doing it wrong.
> >
> > ----- Original Message -----
> > From: "Susan Harrington" <sharring@m...>
> > To: "Security_asp" <security_asp@p...>
> > Sent: Tuesday, February 20, 2001 2:09 AM
> > Subject: FileSystemObject and multiple developers
> >
> >
> > > In using The Scripting Objects (FileSystemObject), is there any way to
> > > keep developers from looking at all files anywhere on the server and
at
> > > each other's (possibly confidential) code on the website?  The
> > > FileSystemObject allows the displaying of the directory and then
listing
> > > the text files in those directories.  There seems to me to be no way
to
> > > keep one developer from accessing text files anywhere on the server or
> on
> > > the website that are not specifically password protected.  Help!
>
>