Latest Microsoft Blogs

While getting started on . NETOOP , one of the first issues to address is that of “Global” settings. When you build a web application for a single purpose, you can hard-code things without much concern. Microsoft.com is probably always going to have the same name, but .NETOOP is going to be a portal application. Everyone who uses the application will need to .NETOOP to use their own web site name (and lots of other site specific configuration data.) Now ASP.NET has that clever “ Application Settings ” feature. This is a great feature that includes design time setting creating and a well factored API for reading the settings. The problem is that these settings like “Site Name” are going to be used all over the site and the actual settings are...

In designing .NETOOP we have this issue: Since .NETOOP will be an adaptable application designed to meet the needs of many users, some of the things that one might hard code in an application like “Web Site Name” will need to be set at installation time. For “system”  configuration settings we have the web.config file. For language and culture variations we have resource files. But this type of site configuration doesn’t really  fit nicely into either of these categories. We could use……. web.config .res files .xml files a table in the database. There are a number of considerations. Since these are not really the same kind of configurations issues that we normally put in the web.config file (like a connection string) it would seem that...