Separating configuration from data lowers total cost of ownership

Posted by: Jeffrey Palermo, on 09 Jan 2009 | View original | Bookmarked: 0 time(s)

All software systems require configuration.  Some require much more configuration that others.  Configuration can be an overloaded term, but I'm speaking about the information necessary for the software to function correctly.  Without this information, the software is unstable and will not work.  For most business systems, a common configuration item is the database connection string.  Without this configuration item, the system cannot function.  Other common configurations...

Advertisement
Free Agile Project Management Tool from Telerik
TeamPulse Community Edition helps your team effectively capture requirements, manage project plans, assign and track work, and most importantly, be continually connected with each other.
Category: ASP.NET | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 900 | Hits: 25

Similar Posts

  • WPF / Silverlight: RadChart and BindableLinq more
  • Using NHibernate with multiple databases more
  • Convert Web.UI Grid into a data entry spreadsheet more
  • App Configuration and Databases more
  • Running the Same Query Against Multiple Databases more
  • RadTreeView for ASP.NET Ajax - Binding to LinqDataSource more
  • Why there is still a limitation in LINQ to SQL? more
  • LINQ To SQL more
  • Error: Both DataSource and DataSourceID are defined on 'controlname'. Remove one definition. more
  • How to simulate RowTest with MS Test more

News Categories

.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Data | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD