Web.config best practices in ASP.NET apps?
From: Ronald S. Cook (rscook_at_westinis.com)
Date: 04/26/04
- Next message: Derrick: "Re: C# Project, in VSS, in the IDE"
- Previous message: Andreas Håkansson: "Re: BorderStyle in the CompactFramework"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 26 Apr 2004 08:50:05 -0600
It seems to make more sense to separate app settings (e.g. global variables,
constants that the development team would control) from web settings (e.g.
database connection strings) that the operations team would control... or
does it?
Our ops team doesn't like that they must comment out connection string lines
depending on wjhere deploying and would rather have their own file that they
insert as desired. But we currently require version/change control on the
Web.config file as we may update a global variable from build to build.
Is there a best practice to this issue, or is using a single Web.config just
the way it has to be?
Thanks,
Ron
- Next message: Derrick: "Re: C# Project, in VSS, in the IDE"
- Previous message: Andreas Håkansson: "Re: BorderStyle in the CompactFramework"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|