Thanks for all of your responses. @Jeff - I've used the registry for other "older" services, and it has worked fine. However, that was before XML and ,NET, so like Stephen, I've been trying to stay away from using it. Besides, to do the structure I'm looking to use for this project, the Registry would be really difficult to use for it.
@Raghupathi - I looked at your latest links, and while one of them, http://stackoverflow.com/questions/730153/custom-configuration-in-net, is definately like what I'm trying to accomplish, there wasn't really a complete answer provided to solve it. The other links really didn't match my scenario. @Stephen, I think you're right about going back to my original idea of just creating a separate XML file and parsing that. I haven't used LINQ, so I'm unfamiliar with how I could use that to walk through the structure. Could you maybe explain, or provide a link to an example, of how I could use LINQ for this, and how I would "bind the XML to the DLL [EXE actually] and keep it out of sight"? Thanks again everyone! Larry On Nov 4, 10:14 am, Stephen Russell <[email protected]> wrote: > On Tue, Nov 2, 2010 at 7:47 AM, Larry <[email protected]> wrote: > > Hi Raghupathi, > > > I've seen the 2nd MS link before, but it doesn't address the sort of > > structure that I have with a collection within a collection. I need > > to have it so that I would have one class where I can roll through > > each "Clinic", and within each clinic, roll through each "LocInfo" > > maintaining the relationship of LocInfo to Clinic. > > > In the Section Grouping example (1st link), it doesn't show what the > > actual configuration XML, just the section groupings, so I'm having a > > problem invisioning what the config XML would look like. It appears > > though that this example is only showing how to retrieve the > > ConfigSections information, not the actual configuration information. > > Unless I'm completely missing the point (possible...), I don't > > understand how this would relate to the configuration XML structure > > type that I'm looking to use. > > ----------------- > > Sounds like you really need this as meta data in XML and not part of > the .config file. In that you could Linq query the value you NEED in > one shot, and that is your point of failure in the current config > mythology right? > > You could bind the XML to the dll and keep it out of sight. > > -- > Stephen Russell > > Sr. Production Systems Programmer > CIMSgts > > 901.246-0159 cell- Hide quoted text - > > - Show quoted text -
