How does the core team manage the web.config file during an upgrade?  Do you simply back it up, perform the upgrade and then copy it back?  I've always been fearful that this would break any settings that might have been added during the core changes for the new release.  So I've always tried to track changes with comments, however this isn't a very easy thing to do either with 3 party modules making AJAX changes and whatnot that aren't so easy to track.

What is the most efficient way to handle the web.config file during an upgrade?

Thanks

Darin

Winmerge x 2.  Primarily the connection string and machine keys, or you break the upgrade.  For me, the rest of the differences between config files could be added later if needed, but those two are critical.

I also comment my web.config with changes, makes it easier in upgrades.

Jeff

Thanks to you all.  I really appreciate all of your responses and all the hard work that many folks have devoted to this great project.

I have all and more of the web.config references mentioned above commented.  I'm very pleased to hear about the winmerge tool, I'm not familiar with it but will be soon.

Thanks again

Darin