The subject is the question.
To address deployment issues, we are going to have the same connection string defined on each of our development, test and production servers, but with different connection parameters to point to our development, test and production databases respectively.
The machine.config on our developer's workstations also has the correct connection string defined.
The problem occurs when trying to get the designer to recognize this connection string when adding tables to the dataset in design view. It wants to either use a connection string based on Server Explorer entries or force you to create a new connection string on the fly.
If I allow it to "roll its own" and then go back in and directly edit the appropriate files, and then run the app, it properly picks up the connection string from machine.config, but of course this is working against the designer rather than with it.
Is there some way to get the designer to see connection strings from machine.config