![]() | |
![]() |
| | Thread Tools | Search this Thread | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
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? |
#3
| |||
| |||
|
|
"Nedim" <Nedim (AT) discussions (DOT) microsoft.com> wrote in message news:57FE2D36-A205-43A2-805F-6739E5E5D86B (AT) microsoft (DOT) 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/...actices. aspx -- Mark Rae ASP.NET MVP http://www.markrae.net |
#4
| |||
| |||
|
|
"Nedim" <Nedim (AT) discussions (DOT) microsoft.com> wrote in message news:57FE2D36-A205-43A2-805F-6739E5E5D86B (AT) microsoft (DOT) 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/...actices. aspx -- Mark Rae ASP.NET MVP http://www.markrae.net |
#5
| |||
| |||
|
#6
| |||
| |||
|
|
"Eliyahu Goldin" <REMOVEALLCAPITALSeEgGoldDinN (AT) mMvVpPsS (DOT) org> wrote in message news:%23yaQ1VhTIHA.1208 (AT) TK2MSFTNGP03 (DOT) phx.gbl... I couldn't agree more. -- Mark Rae ASP.NET MVP http://www.markrae.net |
#7
| |||
| |||
|
|
Yup. LINQ is great, LINQ is cool. To write apps with LINQ, you gotta take time for LINQ school. (boy, that was profound, huh...) |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |