August 2006 Archives
Part of an application I work on derives some of its configuration from the contents of a global.asa file, with configuration hard-coded. I've been looking at ways of separating the configuration out to make it easier to maintain and to understand. Using a simple structure of:
for the XML, and storing it in a file called "config.xml" with the appropriate permissions, obviously! I can then use the following code from ASP to parse this file and place the resultant information into the ASP Application object ready for use within any page:
' Called in Application_OnStart
Set oXmlDocument = Server.CreateObject("Microsoft.XMLDOM")
If oXmlDocument.parseError.errorcode <> 0 Then
Err.Raise oXmlDocument.parseError.errorcode, ,oXmlDocument.parseError.reason
For Each oXmlNode in oXmlDocument.documentElement.childNodes
Application(oXmlNode.NodeName) = oXmlNode.Text
I've managed to reduce the size of the global.asa, make it easier for non-developers to change configuration settings. Now all I've got to do is get the code change agreed!
A Process for Performing Security Code Reviews
Advanced Basics: Predicates and Actions
The latter is the one of most interest to me as it actually explains the purpose, and usage, of predicates in a way that is much clearer than the MSDN / Visual Studio documentation for it. A very powerful tool to have under my belt methinks!