Hi,
I have a requirement to publish a subfolder ("www") of every user's directory as a web-accessible directory (with Directory Browsing enabled). My plan is to have an IIS server host the user's directory physical paths as virtual directories. This generally works, except that to enable Directory Browsing requires a web.config... which I fully expect users to delete when they see it, and then call me up and ask why Directory Browsing stopped working. Also, intelligent users might start making changes to web.config and then making my IIS server do stuff I don't want it doing.
Is there any way I can get IIS to not store that data in web.config, and ignore any web.config files in these virtual directories?
Thanks,
- Jim