Hello.

I'm a veteran classic asp and ado programmer and am now learning asp.net and ado.net. I'm trying to determine the best data source control to use for my asp.net apps. It seems i have three choices: sqlDataSource, xmlDataSource and objectDataSource.

sqlDataSource seems easy to use, but has stated limitations. I'm looking for the one to use for large web applications and one that will provide the highest degree of security (to prevent injection attacks, etc.).

Which one would you recommend?

Thank you for your help.

Sal

Personally, I don't use those DataSources objects except in very specific situations. I create a Data Logic Layer(DLL) that handles my data needs and then bind controls to some sort of strong typed Data Source like a List<T>.

I find that this is the most Robust approach but also requires more coding on your part then simply dragging and dropping Data Source controls so I guess it depends on where your comfort zone lies.

My two cents anyway.

================================================== =========
Read this if you want to know how to get a correct reply for your question:
http://www.catb.org/~esr/faqs/smart-questions.html
================================================== =========
.: Wrox Technical Editor / Author :.
Wrox Books 24 x 7
================================================== =========

Hi there,

Take a look at the article series about N-Layer design that starts here:

http://imar.spaanjaars.com/QuickDocId.aspx?quickdoc=416

It discusses the SqlDataSource and ObjectDataSource controls and shows you a real-world example of the latter. You can still do what Doug suggests (create your own code layers), but use the DataSource controls in the front end for code free data binding....

Imar
---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results and Beginning Dreamweaver MX / MX 2004
Want to be my colleague? Then check out this post.