Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
VS 2008 Ling vs ado.net vs daab 1
- Thread starter Badgers
- Start date
-
1
- #2
Personally, I think LINQ is over-hyped. It can be useful, but I don't think it brings something to the table that we desperately need or have been missing.
I much prefer having complete control over the queries that are running against the database rather than some objects creating dynamic sql for me (that's assuming you were referring to LINQ accessing a database). It is possible to use LINQ with stored procedures, so that goes some way to keeping a fairly good level of control but then there won't actually be that many places where this comes in useful (or not may that I can think of anyway).
Unfortunatly, LINQ will become one of the new buzzwords and people will at least what you to understand it and in some circumstances, use it.
-------------------------------------------------------
Mark,
[URL unfurl="true"]http://aspnetlibrary.com[/url]
[URL unfurl="true"]http://mdssolutions.co.uk[/url] - Delivering professional ASP.NET solutions
[URL unfurl="true"]http://weblogs.asp.net/marksmith[/url]
I much prefer having complete control over the queries that are running against the database rather than some objects creating dynamic sql for me (that's assuming you were referring to LINQ accessing a database). It is possible to use LINQ with stored procedures, so that goes some way to keeping a fairly good level of control but then there won't actually be that many places where this comes in useful (or not may that I can think of anyway).
Unfortunatly, LINQ will become one of the new buzzwords and people will at least what you to understand it and in some circumstances, use it.
-------------------------------------------------------
Mark,
[URL unfurl="true"]http://aspnetlibrary.com[/url]
[URL unfurl="true"]http://mdssolutions.co.uk[/url] - Delivering professional ASP.NET solutions
[URL unfurl="true"]http://weblogs.asp.net/marksmith[/url]
Also, I should add that as long as you have a seperated data access layer then at least you are starting in the right direction.
The DAAB will simplify the amount of code you write over traditional ADO.NET code and it will allow you to change database types easier, so in that respect it's a better option.
LINQ show go some way to doing something similar, I'm just not as convinced as to it's necessity when dealing directly with a typical database (when you are dealing with other types of data access, then it may bring some useful methods).
-------------------------------------------------------
Mark,
[URL unfurl="true"]http://aspnetlibrary.com[/url]
[URL unfurl="true"]http://mdssolutions.co.uk[/url] - Delivering professional ASP.NET solutions
[URL unfurl="true"]http://weblogs.asp.net/marksmith[/url]
The DAAB will simplify the amount of code you write over traditional ADO.NET code and it will allow you to change database types easier, so in that respect it's a better option.
LINQ show go some way to doing something similar, I'm just not as convinced as to it's necessity when dealing directly with a typical database (when you are dealing with other types of data access, then it may bring some useful methods).
-------------------------------------------------------
Mark,
[URL unfurl="true"]http://aspnetlibrary.com[/url]
[URL unfurl="true"]http://mdssolutions.co.uk[/url] - Delivering professional ASP.NET solutions
[URL unfurl="true"]http://weblogs.asp.net/marksmith[/url]
- Thread starter
- #4
- Status
Similar threads
