- For individual users
- Instant access to solutions
- Ask your tech questions
- Start your 30-day Free Trial
Main Topics
Browse All TopicsHello,
Working abit with Linq, and it really seems cool and i would really like to replace SQL actions with this, and generally use linq for processing data.
But im wondering if theres any catch to Linq ? is there any limitations to it, is there anything you shouldnt do with linq ?
Im considering building a 'realtime' table-feeder application that has to feed records into a table from data coming through a named-pipe, it has to be pretty fast performing - would it be stupid to do with Linq ?
So please share your thoughts...
( i dont know how to do regarding points, i guess its more a discussion)
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: naspinskiPosted on 2009-10-11 at 21:52:11ID: 25548686
LInq-to-SQL/Entities is a great option and is easy to develop with. Many real-time applications are run with it and do just fine. Look at the site at http://stackoverflow.com - it is all on the MS stack of Microsoft ASP.NET MVC with a Linq-to-SQL backend - it takes huge traffic and never has any problems. Keep in mind that it is just writing good 'ol SQL queries and running them, just giving the programmer a friendly, strongly-type, OO interface to it instead of SQL strings. It also protects against injection automatically, and you can Unit Test it. You can also used stored procedures if that is your thing. I really see no downsides to using L2S.
Keep in mind that Linq is *not* the same as Linq-to-SQL/Entities. Linq can be used on basically any objects in the .Net framework such as xml, Lists, IEnumerables, etc.