Web.config pros
- Only 1 place to add an extra bit of code
Web.config cons
- Sometimes I forget to update web.config in the production environment, since I never copy web.config from the staging area to a live site.
On each page pros
- When deploying / publishing pages and / or copying pages from dev / test / staging to a live server, you do not need to worry about updating web.config
One page minus
- On each page, therefore, if something changes, it is a pain to go through each page and fix it.
- You need to add it manually to each page.
I would recommend doing this in web.config. This works less for you since you need to remember to add it to every page. Although, if you have a ton and lots are used on only one page, you can do a little to keep your web.config a little less cluttered. I usually put my controls in web.config if I use them on multiple pages. If it is used on only one page, I usually just declare it on my asp.net page.
Jim w source share