I'm looking at some code that uses the asp:LinqDataSource control for
binding data to gridviews.
Does anyone know of a site Someone's blog or something like that that
compares the pros and cons of using asp:LinqDataSource
as opposed to having data access in a data layer and simply binding to it.
I never liked any of the aspdatasource controls,
but I'd like some good evidence to show either way whether the data controls
should be used or not.
I admit they seem to make development move a little quicker,
however I find that you lose a lot of control by using them.

"Ralph" <(E-Mail Removed)> wrote in
news:C2CDDA62-9863-4CE2-99C6-(E-Mail Removed):

> I'm looking at some code that uses the asp:LinqDataSource control for
> binding data to gridviews.
> Does anyone know of a site Someone's blog or something like that that
> compares the pros and cons of using asp:LinqDataSource
> as opposed to having data access in a data layer and simply binding to
> it. I never liked any of the aspdatasource controls,
> but I'd like some good evidence to show either way whether the data
> controls should be used or not.
> I admit they seem to make development move a little quicker,
> however I find that you lose a lot of control by using them.

I am not that fond of the DataSource controls overall. They constrict
you to a very tight box. In the cases where someone fits within that
box, they are nice, as you can drag and drop your entire application.
Outside of that box, you end up kludging way to much of your application
to fit the DataSource control.

If you are already tiering your applications, you will find the drag and
drop reduces the scalability of your applications and greatly reduces
the flexibility (extensibility).

I don't know of a site with the pros and cons. The major Pro I can see
is RAD (Rapid Application Development). But since I am adverse to the
idea of tightly coupled applications, the RAD will almost never outweigh
flexibility of coding an application that is properly tiered.

Peace and Grace,
Greg

--
Vote for Miranda's Christmas Story
http://tinyurl.com/mirandabelieve

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

*******************************************
| Think outside the box! |
*******************************************

"Gregory A. Beamer" <(E-Mail Removed)> wrote in message
news:Xns9CC55C60E1BC3gbworld@207.46.248.16...
> "Ralph" <(E-Mail Removed)> wrote in
> news:C2CDDA62-9863-4CE2-99C6-(E-Mail Removed):
>
>> I'm looking at some code that uses the asp:LinqDataSource control for
>> binding data to gridviews.
>> Does anyone know of a site Someone's blog or something like that that
>> compares the pros and cons of using asp:LinqDataSource
>> as opposed to having data access in a data layer and simply binding to
>> it. I never liked any of the aspdatasource controls,
>> but I'd like some good evidence to show either way whether the data
>> controls should be used or not.
>> I admit they seem to make development move a little quicker,
>> however I find that you lose a lot of control by using them.
>
> I am not that fond of the DataSource controls overall. They constrict
> you to a very tight box. In the cases where someone fits within that
> box, they are nice, as you can drag and drop your entire application.
> Outside of that box, you end up kludging way to much of your application
> to fit the DataSource control.
>
> If you are already tiering your applications, you will find the drag and
> drop reduces the scalability of your applications and greatly reduces
> the flexibility (extensibility).
>
> I don't know of a site with the pros and cons. The major Pro I can see
> is RAD (Rapid Application Development). But since I am adverse to the
> idea of tightly coupled applications, the RAD will almost never outweigh
> flexibility of coding an application that is properly tiered.
>
> Peace and Grace,
> Greg
>
> --
> Vote for Miranda's Christmas Story
> http://tinyurl.com/mirandabelieve
>
> Twitter: @gbworld
> Blog: http://gregorybeamer.spaces.live.com
>
> *******************************************
> | Think outside the box! |
> *******************************************
Thanks Gregory
I'm in agreement with everything you say.
I am interested in hearing if there are any other benefits of datasource
controls.
Microsoft documentation seems to recommend them. At least from my
observations.

"Ralph" <(E-Mail Removed)> wrote in news:79D5D48E-FC4E-400C-9A8A-
(E-Mail Removed):

> I'm in agreement with everything you say.
> I am interested in hearing if there are any other benefits of datasource
> controls.
> Microsoft documentation seems to recommend them. At least from my
> observations.

Microsoft, for some reason, has favored the lowest common denominator. And,
with many applications, this may be wise, as they can fit within a box. I
have a pretty firm standard of separating concerns, so the time savings are
not that dramatic and the flexibility I recieve is pretty phenominal.

Notice that MS is pushing heavily towards EF going forward, which does not
encapsulate all of the layers in a single drag and drop component.

Peace and Grace,
Greg

--
Vote for Miranda's Christmas Story
http://tinyurl.com/mirandabelieve

Twitter: @gbworld
Blog: http://gregorybeamer.spaces.live.com

*******************************************
| Think outside the box! |
*******************************************