I have a scenario that appears from my research to be a common issue but have yet to find a solution. The scenario is:
1. I have a VS2010 VB.NET Application
2. Within this project I have added a datasource and this has created an xsd designer object
3. The ConnectionString created is a Application Scope setting (this is I understand not optional and cannot be a user scoped setting)
4. The ConnectionString setting refers to a database on my development server
This application is not an 'internal' company application but one that will be distributed to many clients, each of which have their own networks, servers etc.
The problem comes in that the ConnectionSetting is read only so how, when I deploy the application, and it is installed on a client network can the client select the database to connect to.
This does seem to be a fundamental requirement of distributing applications but I cannot find anywwhere a solution other than to not use the datasource objects and use my own code to connect to data sources and have unbound controls.
Is there a solution to this problem or alternative strategies/methods for connecting to a datasource and using strongly typed datasets with bound controls?