Hi all,

Just want to check if this is o.k.

Creating a class that generates static versions of some of my aspx pages
(The ones that will hardly get updated).

The content is in a database (In order to keep the site maintainable as it
grows) and the aspx pages pulls this content for each section.

I didn't want to use caching as I am hosted on a shared server and memory
constraints will kick in. I am using caching for the few pages that are
updated on a regular (every few days or every week) basis.

The class has a method that takes three parameters (urlSource,
htmlPageName, htmlPageLocation). It then generates the html page and places
it where ever I specify.

o.k enough of the rambling :-)

As this class would need the ability to write to the hard drive I came
across permission issues.

I didn't want to enable write permissions on most of my folders within IIS
as this is generally not a good idea (So I was going to use my local IIS to
generate the html pages and then upload via ftp).

I've been looking at ways of generating these pages on the server without
enabling write permission within IIS (To prevent other people from using
those permissions via the IUSR_MACHINENAME account).

By giving the aspnet account write permissions to my chosen directorys it
seems to allow my class to generate the html pages even though write
permissions is unchecked within IIS.

Can someone confirm that this is how it is supposed to work (I have been
trying a few things so it may have affected the directories I am writing
to)?

And are there any security implications if I do things this way?

Sorry for the rambling :-) just wanted to explain what I was trying to do.

Thanks,

John

You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

Reply via email to