LINQ Disadvantages
-
Can Any One expain the dis advantaged of LINQ,like where i Can use and where I can not... Thanks, Srinivas Mateti
I think Linq to XML is the best one. I would never work in XML without linq. I dont think there is any such disadvantages. At least using Linq we can leave out unnecessary long for loops for data manipulation. :)
Abhishek Sur
My Latest Articles **Create CLR objects in SQL Server 2005 C# Uncommon Keywords Read/Write Excel using OleDB
**Don't forget to click "Good Answer" if you like to.
-
Can Any One expain the dis advantaged of LINQ,like where i Can use and where I can not... Thanks, Srinivas Mateti
There are no disadvantages in using LINQ. You can find them when you start using them. Well the way you program them makes the disadvantgaes. So you have to analyze your code to correct them. thanks, Thani
India is Mythical and so we are
-
Can Any One expain the dis advantaged of LINQ,like where i Can use and where I can not... Thanks, Srinivas Mateti
For maintenance better using stored procs over LINQ to SQL. Consider if you have a schema change in your table. With LINQ, you add the field in the table and make a corresponding change in your business object and UI as appropriate. If you're using stored procs, you have to remember to modify 4 stored procs and each of the methods that call those procs as well. In addition, with stored procs, you need to remember to manage your own concurrency checks along with updates to calculated fields/identity/timestamps/etc. Keeping a level of abstraction is a good thing and stored procs are one way of doing that. You can have some of that if you use an XML mapping source rather than attribute mapping because with XML mappings, you can tweak the mappings without necessarily needing to recompile the application. Naturally, if you are adding or removing columns or changing data types, a recompile may be necessary.
Thanks and Regards Sujit Kr. Mandal Software Engineer
-
For maintenance better using stored procs over LINQ to SQL. Consider if you have a schema change in your table. With LINQ, you add the field in the table and make a corresponding change in your business object and UI as appropriate. If you're using stored procs, you have to remember to modify 4 stored procs and each of the methods that call those procs as well. In addition, with stored procs, you need to remember to manage your own concurrency checks along with updates to calculated fields/identity/timestamps/etc. Keeping a level of abstraction is a good thing and stored procs are one way of doing that. You can have some of that if you use an XML mapping source rather than attribute mapping because with XML mappings, you can tweak the mappings without necessarily needing to recompile the application. Naturally, if you are adding or removing columns or changing data types, a recompile may be necessary.
Thanks and Regards Sujit Kr. Mandal Software Engineer
...but you can use stored procedures with Linq to SQL! Just drop the SPROCS onto the entity surface and in your linq code you execute the sproc like a method. So your statement about SPROCS is incorrect.