Configuration settings is always a thorny subject. That's because different developers have different preferences on how to do this. In the .NET world, you have the app.config and web.config depending on the project type. Then you can also use ConfigR or even static XML/JSON files. Another option is to store these settings in the database. There's is no right or wrong answer and you should use whatever works best. However, I recently started working with a new team, where things are not as straightforward when it comes to configuration settings. The application is a standard ASP.NET …[read more]
Showing all posts tagged: 'web.config'
A 3-post collection
Are you still using XML files to store your application settings? Are you still placing your website properties in the web.config? Have you developed a nifty, cool, special library to manage XML files full of configuration properties? Do you, like me, find XML extremelly annoying even with all the new APIs such as LINQToXml? Sureley there must be something better out there? Well look no more, because I have the solution! Let me introduce you to ConfigR, the excellent little tool written by Adam Ralph. What is ConfigR you may ask? As Adam elegantly pitches it: ConfigR allows you …[read more]
Spring.Net is a great IoC (Inversion of Control) framework that allows developers to implement Dependency Injection using an xml configuration. In most cases, the Spring config will end up in either your app/ web.config files. However, in some cases, it may be desirable or necessary to keep the Spring object definitions outside your app/web.config files in order to be able to share them across multiple projects, eg your website and your unit tests. The Spring.Net framework has a feature to allows us to do this easily, but there are a few caveats that I will …[read more]