My ISP suddenly switched my ASP.NET from 1.1 to 2.0 without notifying me first so now my websites are currently down due to configuration issues with web.config going from ASP.Net 1.1 to 2.0.  I read that 3.x is ok to run on ASP.NET 2.0 from an run only environment.  Does anyone know what I need to modify in my web.config file to have it correctly work with ASP.NET 2.0?

Thanks,

-Scott

I plan to upgrade to 4.4.x when I get 3.3.7 back up and stable on production and developement on my hosting providers site.  So that way I can make the upgrade to 4.4 on development before doing it on production.  Last time I did an upgrade from 3.2 to 3.3.7 something got screwed up in the database and I lost all of my data on production, so now I mirror my site to do it on one before the other.

Does anyone else know what changes have to be made to the web.config file in 3.3.7 to make it work on ASP.Net 2.0?  I've read through the instruction guide that tells me to just add the requirePermission="false" to the section names, but I still recieve an error in the web config.  Is there anything else I'm missing or need to check up on?