Whether or not you use
TSQL or "inline" sql, I would suggest you create a datalayer.
The SqlDataSource is NOT a datalayer.
The base argument is really:
Rapid Code Development VS Good Code Development.
Unless I'm whipping up a demo that needs to be done by yesterday,
I would avoid tags (of which SqlDataSource is one ) 99.9% of the time.
Rapid <Good most of the time.
Good development means it is maintainable (among other things), and the
<tagsapproach is cumbersome in that regard.
See
6/5/2006
Custom Objects and Tiered Development II // 2.0
http://sholliday.spaces.live.com/blog/
for what a datalayer object is ( among many others sites out there )
"David Lozzi" <dl****@nospam.nospamwrote in message
news:08**********************************@microsof t.com...
I'm fairly new to ASP.Net 2.0 SQLDatasource objects. It defaults using
TSQL
statments for the SELECT, INSERT, UPDATE, DELETE commands, which is great
and it works. However, I've always been taught that all SQL work should be
completed by the SQL server, therefore use stored procedures even for the
simplest of select statements. Does this still hold true for
sqldatasources?
Should I use procs instead of the default tsql??
Thanks,
David Lozzi