UDL in ADO.NET

[Anders Eriksson]

Hello!

In ADO the preferred[1] way of specifying the connection string was using
an .UDL file.

What is the preferred way to do this in ADO.NET?

// Anders
--
English is not my first, or second, language
so anything strange, or insulting, is due to
the translation.
Please correct me so I may learn better English!

[1] by me and MS...

 

[Cowboy \(Gregory A. Beamer\)]

Your English is fine.

I would not say the UDL was the preferred method in ADO. It was, however, a
convenient way to package a connection. In general, in .NET apps, the config
file is the proper location for configured resources. A UDL can still be
used if you are sharing connections across multiple apps, but each
application that is installed can give the user the ability to configure for
the same database, so it does not give you a lot to configure it in this
manner.

How you configure depends upon the application(s) and the user(s) [knowledge
level, etc.].

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

*************************************************
Think outside of the box!
*************************************************

 

[Anders Eriksson]

Your English is fine.

Thank you!

I would not say the UDL was the preferred method in ADO. It was, however, a
convenient way to package a connection. In general, in .NET apps, the config
file is the proper location for configured resources.

How you configure depends upon the application(s) and the user(s) [knowledge
level, etc.].

The thing that was most convenient with UDL was that Windows had a build in
editor where the user easily could change configurations! Is there
something like this when using the config file?


// Anders

 

[Cor Ligthert [MVP]]

Anderson,

The native provider from the database by instance the SQLClient or the
OracleClient, if that does not exist OLEDB and at last ODBC.

Hoping that I understood your question right as meant.

Cor

 

[Cowboy \(Gregory A. Beamer\)]

Yes and no. There is a bit of leeway with the connection string section, but
it is not an external editor and you would have to put the bits in to allow
changing them. On install, however, it is quite easy to ask for the
connection string and even test prior to completing, so there is little need
for the end user to whack the string. You also have the ability to put
config elements in a separate file, which will not be locked down during
runtime, but there is no visual editor, per se.

I am sure there are some instances where end users need to move from one
data store to another, but it is not the most common scenario. I have yet to
have written an application where the common end user flips a connection
string after an application is installed, except for applications where a
user might work with multiple databases and that is usually configured at
runtime (although the strings might be stored at runtime for reuse).

Hope this helps!

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

*************************************************
Think outside of the box!
*************************************************

Your English is fine.

Thank you!

I would not say the UDL was the preferred method in ADO. It was, however,
a
convenient way to package a connection. In general, in .NET apps, the
config
file is the proper location for configured resources.

How you configure depends upon the application(s) and the user(s)
[knowledge
level, etc.].

The thing that was most convenient with UDL was that Windows had a build
in
editor where the user easily could change configurations! Is there
something like this when using the config file?


// Anders
--
English is not my first, or second, language
so anything strange, or insulting, is due to
the translation.
Please correct me so I may learn better English!