Fixing broken build (inferred array typing and in-line initialization are also no-nos under .NET 2.0...you'd think I'd start to be catching on to this by now, eh?) /slaps self on back of hand/
Reduced the ambition of the method designed to create the array of constructor args so that it no longer attempts any type-casting. The method takes type object and returns type object so creating typed arrays in the middle of the method isn't needed and leads to several so-called edge-conditions depending on constructor arg types such as the enum array indicated by this issue.
-updated so-called "anonymous child containers" to be assigned deterministic naming of the form "parent/nestedContainer1/nestedContainer2/nestedContainer3/etc"
-prior changes already prevent the actual error reported in this issue by throwing if two contexts are attempted to be registered with the same names
-fixing broken build (apparently .ToLowerInvariant() didn't show up on the .NET String class until .NET 2.0 so reverting to the somewhat less reliable .ToLower() method for now)
-cannot reproduce
-added unit tests around the HandlerMap class' MapPath() method so that if a subsequent example of the behavior reported in this issue is provided we can properly test against it
fixing broken build from inadvertent introduction of using statements referencing the System.Collections.Generic namespace unsupported under .NET 1.1 (bad VS2008!, bad VS2008!)
fixing broken build from inadvertent introduction of .NET 2.0 inline property initializers unsupported by the 1.1 or 2.0 csc.exe compiler used to build those targets
-added direct support for specifying a collection of IResource instances to configure the container
-introduced various ApplicationContextArgs classes to encapsulate ever-expanding constructor params for ApplicationContexts
-revise constructors chaining to fall over to ApplicationContextArgs-based constructors.
-move codifation of differnt ApplicationContext 'defaults' (caseSensitive, Refresh, etc.) from ApplicationContext constructors into ApplicationContextArgs classes
-changed all references to hard-coded folder and filenames in the relevant tests to use run-time-generated GUIDs to ensure (best as humanly possible!) no collisions with existing files or folders
-introduced IDictionary convenience constructor overload for DictionaryVariableSource
-added unit tests for DictionaryVariableSource behaviors
-introduced guard exception if unbalanced strings are passed to constructor as key-value pairs (but aren't in fact properly 'paired')
