Re: linq and asp.net

by Mark Rae [MVP] on 1/3/2008 2:02:00 PM "Nedim" <Nedim@discussions.microsoft.com> wrote in message
news:57FE2D36-A205-43A2-805F-6739E5E5D86B@microsoft.com...

> so please help, should i go back to the datasets which require a lot more
> work, or is there a way to make use of the linq queries - i need to be
> able
> to make pager work (or some other way to display page numbers and them to
> be
> working links) and to be able to have more fields for filtering?

I think the debate on Linq is likely to become almost as heated as the C# vs
VB.NET debate we started back in 2002 which, thankfully, has pretty much
gone away now...

My personal opinion (so far) is that Linq is superb at allowing .NET objects
to be queried using SQL syntax *as if* they were data tables, but I haven't
really found any need to use Linq to query an actual database... That's
almost certainly because I never go anywhere near the SqlDataSource /
AccessDataSource etc objects - instead, I have a standard DAL which I use
for all database work so, once the connection string is in place, any
individual query is usually just one line of C# code...

There's an interesting take on this here:
http://blogs.msdn.com/ploeh/archive/2007/02/10/HowWillLINQImpactDatabaseDevelopmentBestPractices.aspx

--
Mark Rae
ASP.NET MVP
http://www.markrae.net

Re: linq and asp.net

by Eliyahu Goldin on 1/3/2008 6:32:00 PM One of the major challenges in asp.net is to keep your lane straight without
making unnecessary turns.

I have an impression that many asp.net innovations target novice developers
or those who switch over from some other technologies. Developers who have
already made their way and style through the years of practical development,
who already know sql, javascript and all sorts of big and little things,
don't need to rush to switch the paradigm of managing everything in
server-side code modules.

In many cases it is better to use natural database queries without
introducing an extra complexity layer and having to pass through yet another
learning curve.

--
Eliyahu Goldin,
Software Developer
Microsoft MVP [ASP.NET]
http://msmvps.com/blogs/egoldin
http://usableasp.net

"Mark Rae [MVP]" <mark@markNOSPAMrae.net> wrote in message
news:ugzMyEhTIHA.5400@TK2MSFTNGP04.phx.gbl...
> "Nedim" <Nedim@discussions.microsoft.com> wrote in message
> news:57FE2D36-A205-43A2-805F-6739E5E5D86B@microsoft.com...
>
>> so please help, should i go back to the datasets which require a lot more
>> work, or is there a way to make use of the linq queries - i need to be
>> able
>> to make pager work (or some other way to display page numbers and them to
>> be
>> working links) and to be able to have more fields for filtering?
>
> I think the debate on Linq is likely to become almost as heated as the C#
> vs VB.NET debate we started back in 2002 which, thankfully, has pretty
> much gone away now...
>
> My personal opinion (so far) is that Linq is superb at allowing .NET
> objects to be queried using SQL syntax *as if* they were data tables, but
> I haven't really found any need to use Linq to query an actual database...
> That's almost certainly because I never go anywhere near the SqlDataSource
> / AccessDataSource etc objects - instead, I have a standard DAL which I
> use for all database work so, once the connection string is in place, any
> individual query is usually just one line of C# code...
>
> There's an interesting take on this here:
> http://blogs.msdn.com/ploeh/archive/2007/02/10/HowWillLINQImpactDatabaseDevelopmentBestPractices.aspx
>
>
> --
> Mark Rae
> ASP.NET MVP
> http://www.markrae.net

Re: linq and asp.net

by Mark Rae [MVP] on 1/3/2008 2:48:00 PM "Eliyahu Goldin" <REMOVEALLCAPITALSeEgGoldDinN@mMvVpPsS.org> wrote in
message news:%23yaQ1VhTIHA.1208@TK2MSFTNGP03.phx.gbl...

I couldn't agree more.

--
Mark Rae
ASP.NET MVP
http://www.markrae.net