Instead of using custom configuration files, I am using web.config to hold some values, like:

<add key="Company" value="1" />

And almost all of my aspx pages access web.config to get these values. when I was testing my app on localhost, I did not see any performance issues. But now I have uploaded my app on a live server (3rd party shared server) and it seems to me that everytime I click on a new link within my app, it takes ages for the page to come up (30 secs). I am thinkink, could it be that because I am openning web.config for every page, it may be slowing down the application. Or it may be somethig else??

web.config is normally kept in memory until the IIS process is recycled, or until you update the file.

I assume you aren't writing to web.config from your app - that would kill performance.

So your problem is probably something else.

Eric