Jan 22, 2010 at 2:53 PM
Edited Jan 22, 2010 at 3:12 PM
I will try to describe the whole situation then.
I am creating an application that has the ability to connect to many databases. So i need somewhere to keep the list of connections strings. So far it is application.config
Now this connection strings are not static, meaning that users must be able to create new connection strings, or delete through an interface i have created in the application. So far everything worked fine until the first click once update. When that happened
users lost their connection strings that they had created.
So at this point the idea came into my mind to save the connection strings into an external file and instruct Data Access Application Block to look at that file for the connection strings. So when i do a new click once update the connection strings
will not be lost.
So according to your suggestion the first option with the configSource attribute sounds great. But at a new click once update am i going to loose again the connection strings or click once will "see" this file and bring it to the new application
This is the whole story. I thought just finding a way to save connection strings in an external file would be enough but now you know what i want to accomplish and what the problem is.