I see a lot of code samples with embedded connection strings (to MS SQL databases), and connection strings using localhost. I guess that’s fine for tutorials and quick starts, but what about actually putting it in production?
I need my VB.NET Windows Forms to go somewhere and get the connection string for my rich client application. The server names will change (and that’s about all that changes) from roll-out to roll-out. The connection string can’t be in SQL because you need a connection string to get to it! So where do you put it, and in a form that system administrators can change it? .INI file? Registry? Flat file? Environment variable?