The real reason for the problem is...(probably)
A nice fresh web.config is the main thing as far as I can tell. I put an old copy (1.1) of my web.config in a folder for reference within my 2.0 site and the error reappeared. When I excluded the file, which 2.0 insists you do explicitly, the problem went away.
Hope this helps someone out there.