On Feb 27, 6:50 am, "Keith MacDonald" <nos...@parasites.com> wrote:
> I don't know whether this is a problem with Vista, IIS 7, or my brain, but I
> cannot reproduce a setup I like working with on XP on my new Vista system.
>
> The HTML files are checked into a project in Visual SourceSafe 8, with its
> working folder set to C:\inetpub\wwwroot, or subfolders thereof. When a
> change is required, it's a simple case of checking out the file, editing it,
> immediately viewing the changes in IE, then checking it back in if all is
> correct. This is all done on the local hard drive, so the files are
> separately published to the live server.
>
> The problem on Vista is that the IIS subfolders are always read-only, even
> after I explicitly remove that attribute, and grant myself permission to do
> so. Some mysterious process follows on behind and resets the attribute.
> Can anyone suggest a solution?
>
> Thanks, Keith

> I don't know whether this is a problem with Vista, IIS 7, or my brain, but
> I cannot reproduce a setup I like working with on XP on my new Vista
> system.
>
> The HTML files are checked into a project in Visual SourceSafe 8, with its
> working folder set to C:\inetpub\wwwroot, or subfolders thereof. When a
> change is required, it's a simple case of checking out the file, editing
> it, immediately viewing the changes in IE, then checking it back in if all
> is correct. This is all done on the local hard drive, so the files are
> separately published to the live server.
>
> The problem on Vista is that the IIS subfolders are always read-only, even
> after I explicitly remove that attribute, and grant myself permission to
> do so. Some mysterious process follows on behind and resets the
> attribute. Can anyone suggest a solution?
>
> Thanks, Keith