M
Marty McDonald
We'll create classes which are responsible for providing data to application
developers. Normally, the classes would use config entries for the
connection strings. ***App developers who use these classes should not have
to worry about where the data is or how the classes acquire the data.***
If an app consumes many such dlls, the app config file would contain many
connection strings in its config file. Yet the app developer should not
have to be responsible for those entries. Alternatives would be to provide
connection strings via web services and Sql Server.
Has anyone tried to solve this before? If so, what are your ideas? Thanks
for any thoughts.
developers. Normally, the classes would use config entries for the
connection strings. ***App developers who use these classes should not have
to worry about where the data is or how the classes acquire the data.***
If an app consumes many such dlls, the app config file would contain many
connection strings in its config file. Yet the app developer should not
have to be responsible for those entries. Alternatives would be to provide
connection strings via web services and Sql Server.
Has anyone tried to solve this before? If so, what are your ideas? Thanks
for any thoughts.