Last post Jan 15, 2014 06:59 AM by rajemessage
Jan 12, 2014 08:25 AM|rajemessage|LINK
I Downloaded the system.linq,dynamic
and found that there is no library , it is dynamice.cs , i wanted to know , is it possible to give all funcationality using .net framwork 4.5(2012) ?
the documentaion provied for system.linq.dynamic is not so easy at the above site. is there any where else i can get some dynamic linq
documentation or book.
so that i can write dynamic linq . and understand all componenet of it.
Q3) my under standing of linq to sql and linq to entity is.
that the syntax of both the types are same and linq to sql is for sqlserver.
please correct me.
Jan 12, 2014 08:50 AM|Rion Williams|LINK
Tutorials and LINQ Basics
101 LINQ Examples is a great place to start as it has tons of examples of different LINQ queries and will cover the code to help explain what is going on within the query. It starts out
as very simple and progresses to more advanced queries.
A few other things to check out might be :
Dynamic LINQ Documentation
As far as actual documentation, I think your best bet might be to actually look at the available source for the System.Linq.Dynamic library, which is available below :
You may also want to take a look at the previously mentioned 101 LINQ Examlples section which contains an "Advanced" section that focuses more on dynamic and more "advanced" queries. I'll include a few other suggested resources that might help with dynamic
queries as well :
Regarding a Book
I'm not terribly certain of a specific book on dynamic queries, but you may want to consider taking a look at the
C# in a Nutshell book that the 2nd article above is referenced from. It is also mentioned in Scott Guthrie's blog post on dynamic LINQ. Your best resources however will likely be what you can find on the net itself.
Differences beteween LINQ-to-SQL and LINQ- to-Entities
LINQ to Entities is a version of LINQ that is specifically designed to work with and target elements that are created through Entity Framework (a popular ORM that will generate proper "Entities" based on database tables). It is highly popular especially
when the recent gains in popularity of Entity Framework and its widespread use within the .NET environment.
One of the major benefits of LINQ to Entities is that it allows developers to write strongly-typed queries to easily target the properties of the entities being queried and storing the values in strongly-typed collections (which are often easier to work
with than generic datatables and other collections might be).
Linq to SQL varies slightly from LINQ to Entities primarily due to the fact that it doesn't deal at all with Entity Framework. Since it doesn't deal with Entity Framework, LINQ to SQL allows you to perform queries on your SQL databases and will generate
all of the necessary calls for them as well as translate your queries into objects (although they may not be strongly typed as LINQ to Entities queries are).
One of the major benefits of LINQ to SQL is that since it doesn't use any kind of relation-mapping such as Entity Frameworks, it allows you to query the databases directly using LINQ.
Comparison Between LINQ-to-SQL and LINQ-to-Entities
Syntactically the two are very similar, as you can see from this white-paper article that provides a detailed comparision of the two.
Basically, you can think of things this way :
Jan 13, 2014 11:09 AM|rajemessage|LINK
Thank u very much,
Please tel me one more thing, the System.Linq.Dynamic namespace at Scott Guthrie's is from dynamic.cs file.
and the library which gets installed using nuget is same or different.
Jan 13, 2014 11:46 AM|Rion Williams|LINK
I believe that they are essentially equivalent as the Dynamic.cs file should be contained within the System.Linq.Dynamic assembly. The System.Linq.Dynamic library should be the only one that you need.
Jan 15, 2014 06:59 AM|rajemessage|LINK
gethub has 4.0,does that works with 2012 ?
Other thing is, i could not get advance section at 101 sample,
basicaly i want any resource , which can help me in making dyanmic query for gouping and summing columns ( more than one). where even tables are not known some times.
using linq to entity.