However for that is as well AFAIK the best solution, don't use LINQ. This
because Linq is an expression language meant to get fast extractions from
data and submit the changes to the database in a simple way.
However for that is as well AFAIK the best solution, don't use LINQ. This
because Linq is an expression language meant to get fast extractions from
data and submit the changes to the database in a simple way.
Read what you wrote - there's no real need to mention databases at all
in my view. Your statement is biased towards databases when I'd just
say that LINQ is a set of technologies to ease data access, whatever
the data source.
I don't think so. You may not use it in all layers (although LINQ to
Objects is almost always useful, IMO) but there's nothing wrong with
using LINQ in multi-layer solutions. You still need to solve a lot of
the same problems as before in terms of concurrent updates etc, but
LINQ will help in various ways.
No, that would be the opposite of the general opinion.
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.