We're getting a lot of re-use out of our .NET framework here at the port. We've got our public web site, Web Services, Windows Services, and now we're creating SharePoint Portal web parts - all using the same underlying managed framework. I've run into a problem re-using .config files across applications.
Here's the problem. We have a class VIT.Common.Configuration with a bunch of static methods that encapsulate access to in .config files. This works great, but it's starting to get hard to manage, because I need copies of the <AppSettings> blocks in each .config file. I'm having to keep at least 5 of these in sync, and it's only going to get worse. I'm going to explore creating a WebService to make this stuff available from one source, but I've got some security concerns here. Has anyone out there any thoughts about this direction? Are there better ways to manage multiple configurations?
-Brendan
Posted
12-03-2003 8:19 AM
by
Brendan Tompkins