Mar 08, 2010 03:35 PM|YugangW|LINK
When the shared web.config will be checked into source control, it should avoid having machine specific settings in it as this will break team development. I agree with you on this one.
Not sure the detail of your statement of "This works for us but it may not work very well for larger projects". I guess, maybe you don't like the fact that different developers might have to duplicate the web.config file so they can modify couple of config
artifacts to fit their specific dev environemnt for example, mail alias on sending errors, url for the service reference. So the ideal approach would be to have a root web.config defining any firm settings and then each developer uses web.config transformation
to add their own for the purpose of local debugging or just running the webs? Is this your concern?
Microsoft visual web development team