there are 3 general linq libraries
Linq for objects (IEnumerable):
this is a great replacement for the bad performing foreach. Not only is it
faster, but gives a full query language for seaching and joinging
collections. you should switch.
Linq for Xml:
coding here is probably simpler than dom and xpath coding. the performance
seem to be close to using compiled xpaths, and it uses an xmlreader under the
covers. there is less Linq code to write, and its probably (for those that
know linq) easier to read. look at switching.
Linq for SQL
this is a library that takes a compiled linq parse tree and converts to
dynamic sql at runtime. it you are doing dynamic sql, this may be a good
replacement, but should not replace stored procedures or calling prepared
statements. there are also sql features that can not be accessed from linq to
sql.
-- bruce (sqlwork.com)
"George" wrote:
I am a bit conservative type and usually give some time for technology to
mature before starting to try it.
Today my question is Linq. To start using it or not.
So here is the voting questions.
1. It speeds up development. Yes or No?
2. It makes programs easier to code and read. Yes or No?
3. Perfomance is the same (or comparable) comparing Linq with MsSql and
ADO.NET
Thanks.
George.