Having trouble migrating from .Net 2.0 to .Net 3.5? Clean up your configs!
It seems that 3.5 is a lot pickier over what it will accept in a config file, than 2.0 was. Particularly if you are using the configSource attribute, to include separate files for different environments.
I was having issues deploying an application using ClickOnce. I had migrated it to VS 2008, so I could convert it to work on 64 bit machines. The old configs had a lot of additional tags, and 2008 doesn’t like extra tags.
Do your cleanup like you should be, and we won’t have this problem, will we? See, your mom was right. If you clean up after yourself, life will be much easier.