Dan Miser - Missing: Connection String Wizard

Tuesday, August 22, 2006

I have a need to allow users to build up a connection string and store it in a config file. Pretty simple need, and I would imagine rather standard. After all, I can't imagine any user I deploy to would have the same connection string I do, much less the same database. As it turns out, providing a robust piece of code to get this done will have to be all custom code. Given how common this scenario is, I'm more than a bit disappointed that MS just punted on this entire thing. Do they really expect end users to just wander around and edit config file XML syntax by hand and get it right? Do they really think not having the ability to do a "Test Connection" is a good idea?

I know about the support article from MS, but that uses interop back to plain ADO. I really can't believe they would not provide a managed code alternative that works with ADO.NET. Furthermore, the DbConnectionStringBuilder class in ADO.NET 2.0 starts to solve the problem, but stops short, like Frank Costanza on a drive through New York City. That class gives us some capability to build up the connection string, but none to visually build it up, much less edit a connection string in-place in the config file.

After way more time searching around the Internet than I care to admit, I'd like to think that I'm missing some simple link, but it looks like MS expects every single .NET developer to implement their own Connection String Wizard from scratch. Feel free to reply if you know of any pre-built solutions.

Tuesday, August 22, 2006 10:14:00 AM (Central Daylight Time, UTC-05:00)

Tuesday, August 22, 2006 11:55:00 AM (Central Daylight Time, UTC-05:00)

Generally, I use the "File Name=c:\myprogramlocation\MyUdl.udl" method of connection string and keep the settings there. Durring my install process, I generate the udl from information gained from the setup program. This gives me the ability to check/change the connection just by double clicking the udl file. I use Inno for my setup and have a few custom screens generated to handle most of the cases we have run into (installing to MSSQL).

Of course this isn't exactly what you were probably looking for...but it works. Most of the time the person doing the initial install is going to be the system admin, so our method of asking for the connection data at initial setup works for us.

Steven Kamradt

Tuesday, August 22, 2006 3:53:00 PM (Central Daylight Time, UTC-05:00)

Hi Dan,

If I understand what you mean, there's a very simple, as much as obscure and little known, way of invoking the standard MS Wizard: just programmatically create an empty .udl file and execute it, and voilà, the user can build his string, and the .udl gets filled with the connection data.

Hope this helps!

--Giulio

Giulio Palmieri

Thursday, August 24, 2006 10:39:00 AM (Central Daylight Time, UTC-05:00)

I'll check into the udl approach. I used it for vanilla ADO way back when, so that may be a real good compromise. Thanks.

Dan Miser

Thursday, August 24, 2006 2:11:00 PM (Central Daylight Time, UTC-05:00)

I just tested creating an empty .UDL file, and it works really well. Thanks Giulio!

Ken White

Comments are closed.