The web config file is loaded when the application goes online. It is loaded only once and is shared between all users. So as long as you have a decent hardware configuration for your server, you shouldn't have any problems, it should work. On the flip side having a large number of config entries can increase the seek time when accessing config items. HTH!

harold aptroot wrote: Poke it with a TCP connection Poking it might just make it angry and it could POP you. ;P only two letters away from being an asset

The web.config file is usually just read once and the info cached so unless you actually change something in your web.config file I can't see this being an issue. Here is a link to MSDN that discusses .NET application performance tuning. http://msdn.microsoft.com/en-us/library/ms998583.aspx[^] Back in the blog beatch! http://CraptasticNation.blogspot.com/[^]

It doesn't really make much difference here - the message isn't dragged back to the top of the list, unlike QA. Just don't hold your breath waiting for a response! :D "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer