Using LINQ To SQL (Part 1) - ScottGu's Blog
Using LINQ To SQL (Part 1) - ScottGu's Blog
The above language features help make querying data a first class programming concept. We call this overall querying programming model "LINQ" - which stands for .NET Language Integrated Query.
Developers can use LINQ with any data source. They can express efficient query behavior in their programming language of choice, optionally transform/shape data query results into whatever format they want, and then
easily manipulate the results. LINQ-enabled languages can provide full type-safety and compile-time checking of query expressions, and development tools can provide full intellisense, debugging, and rich refactoring support when
writing LINQ code.
LINQ supports a very rich extensibility model that facilitates the creation of very efficient domain-specific operators for data sources. The "Orcas" version of the .NET Framework ships with built-in libraries that enable LINQ support
against Objects, XML, and Databases.
LINQ to SQL is an O/RM (object relational mapping) implementation that ships in the .NET Framework "Orcas" release, and which allows you to model a relational database using .NET classes. You can then query the database using
LINQ, as well as update/insert/delete data from it.
LINQ to SQL fully supports transactions, views, and stored procedures. It also provides an easy way to integrate data validation and business logic rules into your data model.
Visual Studio "Orcas" ships with a LINQ to SQL designer that provides an easy way to model and visualize a database as a LINQ to SQL object model. My next blog post will cover in more depth how to use this designer (you can
also watch this video I made in January to see me build a LINQ to SQL model from scratch using it).
Using the LINQ to SQL designer I can easily create a representation of the sample "Northwind" database like below:
My LINQ to SQL design-surface above defines four entity classes: Product, Category, Order and OrderDetail. The properties of each class map to the columns of a corresponding table in the database. Each instance of a class entity
represents a row within the database table.
The arrows between the four entity classes above represent associations/relationships between the different entities. These are typically modeled using primary-key/foreign-key relationships in the database. The direction of the arrows
on the design-surface indicate whether the association is a one-to-one or one-to-many relationship. Strongly-typed properties will be added to the entity classes based on this. For example, the Category class above has a one-to-many
relationship with the Product class. This means it will have a "Categories" property which is a collection of Product objects within that category. The Product class then has a "Category" property that points to a Category class instance
that represents the Category to which the Product belongs.
The right-hand method pane within the LINQ to SQL design surface above contains a list of stored procedures that interact with our database model. In the sample above I added a single "GetProductsByCategory" SPROC. It takes a
categoryID as an input argument, and returns a sequence of Product entities as a result. We'll look at how to call this SPROC in a code sample below.
Understanding the DataContext Class
When you press the "save" button within the LINQ to SQL designer surface, Visual Studio will persist out .NET classes that represent the entities and database relationships that we modeled. For each LINQ to SQL designer file added
to our solution, a custom DataContext class will also be generated. This DataContext class is the main conduit by which we'll query entities from the database as well as apply changes. The DataContext class created will have
properties that represent each Table we modeled within the database, as well as methods for each Stored Procedure we added.
For example, below is the NorthwindDataContext class that is persisted based on the model we designed above:
Once we've modeled our database using the LINQ to SQL designer, we can then easily write code to work against it. Below are a few code examples that show off common data tasks:
1 of 17 04/04/2011 4:07 PM
Using LINQ to SQL (Part 1) - ScottGu's Blog http://weblogs.asp.net/scottgu/archive/2007/05/19/using-linq-to-sql-par...
The code below uses LINQ query syntax to retrieve an IEnumerable sequence of Product objects. Note how the code is querying across the Product/Category relationship to only retrieve those products in the "Beverages" category:
C#:
VB:
The code below demonstrates how to retrieve a single product from the database, update its price, and then save the changes back to the database:
C#:
VB:
Note: VB in "Orcas" Beta1 doesn't support Lambdas yet. It will, though, in Beta2 - at which point the above query can be rewritten to be more concise.
3) Insert a New Category and Two New Products into the Database
The code below demonstrates how to create a new category, and then create two new products and associate them with the category. All three are then saved into the database.
Note below how I don't need to manually manage the primary key/foreign key relationships. Instead, just by adding the Product objects into the category's "Products" collection, and then by adding the Category object into the
DataContext's "Categories" collection, LINQ to SQL will know to automatically persist the appropriate PK/FK relationships for me.
C#
VB:
The code below demonstrates how to delete all Toy products from the database:
C#:
VB:
2 of 17 04/04/2011 4:07 PM
Using LINQ to SQL (Part 1) - ScottGu's Blog http://weblogs.asp.net/scottgu/archive/2007/05/19/using-linq-to-sql-par...
The code below demonstrates how to retrieve Product entities not using LINQ query syntax, but rather by calling the "GetProductsByCategory" stored procedure we added to our data model above. Note that once I retrieve the Product
results, I can update/delete them and then call db.SubmitChanges() to persist the modifications back to the database.
C#:
VB:
The code below demonstrates how to implement efficient server-side database paging as part of a LINQ query. By using the Skip() and Take() operators below, we'll only return 10 rows from the database - starting with row 200.
C#:
VB:
Summary
LINQ to SQL provides a nice, clean way to model the data layer of your application. Once you've defined your data model you can easily and efficiently perform queries, inserts, updates and deletes against it.
Hopefully the above introduction and code samples have helped whet your appetite to learn more. Over the next few weeks I'll be continuing this series to explore LINQ to SQL in more detail.
Hope this helps,
Scott
Comments
# Using LINQ to SQL (Part 1) - ScottGu's Blog
Saturday, May 19, 2007 3:50 AM by Using LINQ to SQL (Part 1) - ScottGu's Blog
As always, very nice! It would be great if you could continue this series with a discussion of how to handle m:m relationships, given that they are not natively supported by LINQ to SQL. Just some examples how one would work around that limitation in the DAL,
if one happens to have a DB with m:m relations.
If my database have more then 2,000 store procdures ,how can i use DLinq?
I have a little suggestion here. Is it possible to allow VB statements to span multiple lines without the use of underscores such as
A.foo(bar) A = B
some simple (but smart) regex should be able to separate the lines into
3 of 17 04/04/2011 4:07 PM
Using LINQ to SQL (Part 1) - ScottGu's Blog http://weblogs.asp.net/scottgu/archive/2007/05/19/using-linq-to-sql-par...
A.foo(bar)
A= B
the underscore character are 2 characters away from your little finger on home row and if in the future I'm going to be implementing a lot of LINQ then that would surely slow down my typing speed to some degree
I would love to know more about in which context the DataContext is used/shared as it doesn't seem thread safe or that it should be around too long because of the caching/stale data problems.
[)amien
Wow, I was really wiating for a post on LINQ to SQl from you and today is my day.
Thanks
Vikram
www.vikramlakhotia.com
ie.
Customers
CustomerProducts
Products
On a delete and add of products to customers, does it handle the CustomerProducts association table?
Thanks again
Scott,
The thing I'm still not quite getting after these tutorials, and even after playing with it some in the beta is the best way to use this along with ASP.NET Data Controls. Unless I'm missing something, the generated Update(item) method requires the same
DataContext instance that created the item, meaning it doesn't work across postbacks when used in an ObjectDataSource.
I know you've hinted at a LinqDataSource- is there anywhere we can see that yet?
--rj
Hi Davidacoder/Steve,
I'll put m:m relationships on the list to blog about in one of my future Linq to SQL posts (it deserves a post in and of itself).
LINQ to SQL doesn't natively support m:m - instead you typically create an intermediate table to handle the m:m relationss.
LINQ to Entities, which will ship shortly after "Orcas", does support m:m relationships directly. So that is another alternative to consider.
Scott
Hi Daniel,
I'll post more about integrating LINQ to SQL with ASP.NET data controls shortly.
Beta2 will have the <asp:linqdatasource> control built-in, which will provide the easiest way to use LINQ with ASP.NET controls (basically just point the ASP.NET controls at the LINQDataSource, and then point the LINQDataSource at the LINQ to SQL entities
with a filter and you are done - selection, paging, editing, deleting, insertion all handled for you).
Alternatively, if you don't want to use the LINQDataSource control then you can use the Attach() method on Tables to re-attach a disconnected entity to a DataContext. This enables you to perform changes and updates across post-backs, web-services, and/or
any scenario where you don't have the same DataContext. It works well with the <asp:objectdatasource> control today.
Scott
Hi Kain,
You can have any number of stored procedures that you want on your DataContext - so you should be able to use all 2000 of them in your database.
Scott
"LINQ to SQL doesn't natively support m:m - instead you typically create an intermediate table to handle the m:m relations.
LINQ to Entities, which will ship shortly after "Orcas", does support m:m relationships directly. So that is another alternative to consider."
I'd be disappointed to find out that I would need another tool to handle M:M
Could you have an option to handle the DataContext via a 'Open Session in View' model (ie. www.hibernate.org/43.html or here www.codeproject.com/.../NHibernateBestPractices.asp) rather than call attach or need to relate entities (not EDM, but a Poco
object) directly to controls?
Saturday, May 19, 2007 4:24 PM by robinzhong’s blog - links for 2007-05-19
Scott,
Will anything ship with Orcas to generate LINQ to SQL from and existing SQL2005 database?
4 of 17 04/04/2011 4:07 PM
Using LINQ to SQL (Part 1) - ScottGu's Blog http://weblogs.asp.net/scottgu/archive/2007/05/19/using-linq-to-sql-par...
# System.Data.Linq.dll
System.Data.Linq.dll
Hi Scott,
Thanks for the excellent write-up, as usual. Does Linq to SQL replace SQL metal (which was part of the June CTP)?
Thanks,
Burton
# robinz’s tech life » Blog Archive » links for 2007-05-20 » Enjoying Open Source!
Saturday, May 19, 2007 8:23 PM by robinz’s tech life » Blog Archive » links for 2007-05-20 » Enjoying Open Source!
Pingback from robinz’s tech life » Blog Archive » links for 2007-05-20 » Enjoying Open Source!
Hi Kyle,
The LINQ to SQL designer makes it really easy to model an existing SQL 2005 database. I'll cover this in my next blog post in the series. Basically you can add all of the tables in the database onto the designer and it will automatically infer/create the
appropriate associations between the entities.
In terms of performance, LINQ to SQL is really, really fast. In general I'd expect it to be faster than using a DataSet approach.
Scott
Hi Burton,
SQLMetal was a command-line tool that creates LINQ to SQL entity models (at the time LINQ to SQL was called "DLINQ").
In addition to the command-line option, LINQ to SQL now supports the WYSIWYG designer surface I showed in my screen-shot above. I find this more convenient to model data entities, which was why I used that approach.
Scott
Hi Scott,
I am just confused between LINQ tools and Dynamic Data Controls for ASP.NET as explained in AspNet Futures.
Are they talking about the LINQ tools with a new name comming up with Orcas or its totally different and have no connection with Orcas Tools.
Thanks
SoftMind
int count;
select p).Skeep(20).Take(10).
GetTotalRowsCount(out count);
What type of SQL do the Skip() and Take() operators generate? Would it be efficient enough for paging large amounts of data or would you still want to write your own stored procedure?
Using LINQ to SQL (Part 1) [Via: ScottGu ] Easier Winform UI Thread Safe Methods with DynamicProxy2...
Hi Scott,
Using the LINQ to SQL Designer, can I assign stored procedures for the CRUD operations of my entities, (like in named datasets) or do I have to rely on the generated SQL code?
Hi Steve,
Unfortunately LINQ to SQL won't support M:M except via an intermediate table in the "Orcas" V1 timeframe.
In terms of the "Open Session in View" pattern, I'd probably recommend against doing this. If I understand the second link correctly, this stores things web requests - which ultimately makes scaling out across multiple web servers harder, and can lead to scaling
challenges as more users hit the application.
While you could use this approach with the LINQ to SQL DataContext, a better approach would be to release the context at the end of each request, and use the Attach() feature when a user later posts back and you want to rehydate the entity from the view.
This doesn't require anything to be stored on the server, and is really easy to-do (1 line of code). This will work regardless of whether you are in single server or web farm mode, and will scale incredibly well.
Scott
Hi SoftMind,
The new Dynamic Data Controls in the ASP.NET Futures release are a set of UI control helpers that make it much easier to quickly get data-driven UI up and running.
The current release of the data controls work directly against the database - but the next release will allow you to work against LINQ to SQL entities. This will make it really easy to define your data entities, and then quickly generate UI based on them.
Scott
Hi Koistya `Navin,
You can write this code to calculate the total number of rows in the query:
select p;
5 of 17 04/04/2011 4:07 PM
Using LINQ to SQL (Part 1) - ScottGu's Blog http://weblogs.asp.net/scottgu/archive/2007/05/19/using-linq-to-sql-par...
This will execute two database requests - the first will return the total number of rows in the query. The second returns the subset of rows you want.
At now point does the entire set of products get fetched to the web-server.
Scott
Hi Matt,
LINQ to SQL uses the new ROW_NUMBER() function with SQL 2005 to implement efficient paging support within the database.
I posted two blog posts last year that talk a little more about this capability:
weblogs.asp.net/.../434314.aspx
and:
weblogs.asp.net/.../434787.aspx
The benefit of using LINQ to SQL is that you don't need to write a SPROC to achieve this, and it is much easier to write.
Scott
Hi Manuel,
>>>> Using the LINQ to SQL Designer, can I assign stored procedures for the CRUD operations of my entities, (like in named datasets) or do I have to rely on the generated SQL code?
Yes - you can assign stored procedures for the update, insert and delete operations of your entities. So if you don't want to rely on the SQL code that LINQ to SQL infers for you you can use these to override it.
Scott
Hi folks,
thinkingindotnet.wordpress.com/.../usando-linq-to-sql-1%c2%aa-parte
Scott,
Great article. A really useful primer on LINQ to SQL. A question for you: Do you have an error in the text? Please check these sentences early in the article:
"For example, the Category class above has a one-to-many relationship with the Product class. This means it will have a "Categories" property which is a collection of Product objects within that category."
-Krip
>> LINQ to SQL will know to automatically persist the appropriate PK/FK relationships for me
AMAZING!!
When will Linq to SQL support other databases (specifically DB2)? Last I read there's only support for MS SQL - doesn't that strike you as rather limiting? Hopefully I'm way off base here, I'm sure you wouldn't plan on shipping a product as cool as this with
support only for SQL Server.
"you can use the Attach() method on Tables to re-attach a disconnected entity to a DataContext. "
How does Linq-to-SQL know if the re-attached object has been modified or which fields have been modified?
Do you recommend exposing these generated classes directly in a data contract for a service? I prefer not to expose database layer implementation to the clients. So how can these generated classes be mapped to business objects for the client callers - is it
possible to map to and from external classes and still successful re-attach and use the objects across service calls?
Thanks
Could you talk a little about the underlying classes that are generated? Are the generated classes partial classes that we could "extend"? Basically, can we add new code to the Products class? Something like a IsNameOk() function inside the Products class
that would not map to a field in the database (obviously since it's a function not a property) that would return true or false based on other properties (building business rules is what I'm trying to get to)
Thanks.
Typo:
This means it will have a "Categories" property which is a collection of Product objects within that category.
1. Can you do many to many relationships without a class for the (in RDB necessary) many-to-many table?
2. Can you also call Save on a single object, and maybe even control the cascaded saving of related objects?
3. In the future articles, can you please also explain scenario's where the database tables and the classes are not so conveniently similar? Some examples: many-to-many relationships and inheritance.
Thanks!
PS. This gives .NET the definitive edge over the rest of the field. It's nice to see MS compete based on some pretty innovative ideas.
Will there be support for any other db besides SQL Server in the RTM? (spec. Oracle)
6 of 17 04/04/2011 4:07 PM
Using LINQ to SQL (Part 1) - ScottGu's Blog http://weblogs.asp.net/scottgu/archive/2007/05/19/using-linq-to-sql-par...
The problem with this model is that it allows new developers coming into the field to learn bad practices rather easily. Allowing direct coupling from the presentation tier to the DB. In turn creating my "disposable" apps.
Hi El Guapo,
When doing an Attach for disconnected scenarios, you can either use a timestamp column with the database to determine if there have been changes, or do a comparison of the values to see if there are any deltas.
Scott
Hi Peter,
All of the classes generated by the LINQ to SQL designer are generated as partial classes - which means you can definitely add custom validation logic and additional methods/properties to them. This should make adding business rules much, much easier.
Scott
Hi Mike,
1) For many to many relationships you need to go through an intermediate class (I'll cover this in a future blog post).
2) When you Save on the DataContext, it will persist all changes you make (and update everything within a single transaction by default).
3) I'll cover some of the more advanced modeling/shaping scenarios in a future post. Stay tuned! :-)
Thanks,
Scott
Hi Will,
There is no need to couple your presentation tier to the database with LINQ. LINQ to SQL generated entity classes that abstract your database and provide a clean way to add validation logic.
You can also optionally add an intermediate business layer class between your UI and entity layer to add additional separation if you'd like.
Thanks,
Scott
Hi Scott
Will there be a zoom feature on the Linq to Sql Deisgner for large databases? This would be brilliant.
Thanks
Rob Mathieson
Hi, Scott
One question, is it possible to use Extension Methods for operators, like: ==,+,-?
Thanks!
Orlando Agostinho
Scott, please check this discussion on the namespace naming for LINQ. Some of the biggest advocates of LINQ really can't understand Microsoft's decision here. We could really do with some feedback,
Thanks, Pete.
forums.microsoft.com/.../ShowPost.aspx
> All of the classes generated by the LINQ to SQL designer are generated
> as partial classes - which means you can definitely add custom validation
If people want a bit more on LINQ to SQL, I made a few videos that you can find links to here;
mtaulty.com/.../9322.aspx
Or, alternatively, you will also find them up here where they might stream/download a bit better :-)
www.microsoft.com/.../nuggets.aspx
Thanks,
Mike.
Great article,
Is there any chance of you showing a simple best practice ASP.NET example of a presentation tier, business logic tier and data acess logic tier solution using LINQ and the asp:linqdatasource. I'd be interested to hear more about scalability, how Attach works
and where the DataContext objects would be etc...
Peter
Hi Peter,
Thanks,
Scott
7 of 17 04/04/2011 4:07 PM
Using LINQ to SQL (Part 1) - ScottGu's Blog http://weblogs.asp.net/scottgu/archive/2007/05/19/using-linq-to-sql-par...
Could you give an example of a computed column? Does it have the same limitations as ADO.Net's DataColumn.Expression property or can it get it's results from a normal DotNet function with full access to all libraries?
This means it will have a "Categories" property which is a collection of Product objects within that category.
Shouldn't it be:
This means it will have a "Products" property which is a collection of Product objects within that category.
??
hi Dynamic .
if not :
---------------------------------
var query :
if(nameTextBox.Text.length>0)
where p.Name=nameTextBox.Text
select p;
if(ageTextBox.Text.length>0)
where p.Age=ageTextBox.Text
select p;
if...........
return query ;
Hi, hawk
How about this, I don't really sure, but maybe will work;
|| p=> p.Age==""+ageTextBox.Text
select p;
See Ya!
Orlando Agostinho
Lisbon/Portugal
Hi Scott
Will the Linq to Sql designer support some sort of zoom feature for large databases?
Thanks
Rob
In the SP example you put the results of the SP into an anonymous type, but then you use a concrete type to iterate over the collection of anonymous types. How much support can the compiler provide to ensure that the shapes of the objects in the
anonymous collection match the shape of the iteration variable?
Hi Rob,
Yep - the good news is that the LINQ to SQL designer fully supports a "zoom" feature. So you can put as many tables/entities as you want on it. :-)
Scott
Hi Shane,
In the SP example above the SP actually returned an explicit type (specifically a sequence of Product objects). This means that the compiler will provide explicit compile-time checking of the result.
Scott
Hi Thomas,
Yep - you can work with computed columns using LINQ to SQL. For some good examples check out my "anonymous types" post here: weblogs.asp.net/.../new-orcas-language-feature-anonymous-types.aspx
Scott
It's been said multiple times before, but I'll just reiterate; We need Oracle support i LINQ (LING for Oracle?). It kills me to see all this goodness and know that there is just no way we can ever use this... :(
8 of 17 04/04/2011 4:07 PM
Using LINQ to SQL (Part 1) - ScottGu's Blog http://weblogs.asp.net/scottgu/archive/2007/05/19/using-linq-to-sql-par...
1) Add ParentID to Categories making categories a tree, and show how we can load from the root categories and walk the tree where root categories have a ParentID of zero.
2) Change the Product Category Relation to a many-to-many and show how Linq to SQL can hide the existance of the relationship table [ProductCategoryRelation] so we just do product.Categories and get the actual Category and not a representation of the
relation.
Thanks...
Hi, Scott
I would like to ask how about LINQ Asynchronous? Imagine, I would want running one query but i know that query will be running not so fast, and i want to use any asynchronous mechanism that LINQ can give me!
Thanks a lot!
Orlando Agostinho
Lisbon/Portugal
Hi Mike,
I'll add a tree sample on my list of posts to blog. The good news is that it works well with LINQ to SQL.
Regarding M:M relationships, LINQ to SQL unfortunately only supports them via an intermediate table/class today. I'll blog how to manage that in a future blog post as well.
Scott
Hi Orlando,
LINQ itself lends itself very well to asynchronous programming. Because queries with LINQ are executed in a deffered way, you can use a nice programming model to manage this. I'll put it on my list of topics to discuss.
Thanks,
Scott
Your "anonymous types" post only seems to deal with "calculated columns" that derive from database functions.
Here's an example I found from an old DLinq document that illustrates what I think is very powerful; however, it does not seem to work in Beta 1. What happened to the ToSequence() method (has it been renamed)?
var q =
from c in db.Customers
var q2 =
from c in q.ToSequence()
Name = DoNameProcessing(c.ContactName),
Phone = DoPhoneProcessing(c.Phone)
};
Here's a quote from the doumentation that explains what I want to do:
"Still elaborate projections (transformations) may require local procedural logic to implement. For you to use your own local methods in a final projection you will need to project twice. The first projection extracts all the data values you’ll need to reference and
the second projection performs the transformation. In between these two projections is a call to the ToSequence() operator that shifts processing at that point from a DLinq query into a locally executed one."
"Note that the ToSequence() operator, unlike ToList() and ToArray(), does not cause execution of the query. It is still deferred. The ToSequence() operator merely changes the static typing of the query, turning a Query<T> into an IEnumerable<T>, tricking the
compiler into treating the rest of the query as locally executed."
Thanks
# LINQ
In Part 1 of my LINQ to SQL blog post series I discussed "What is LINQ to SQL" and provided a basic overview
In Part 1 of my LINQ to SQL blog post series I discussed "What is LINQ to SQL" and provided a basic overview
In Part 1 of my LINQ to SQL blog post series I discussed "What is LINQ to SQL" and provided a basic overview
Also,I want to know how to fix the complex relation of two or more entities.
Thanks a lot...
I actually got a shiver down my spine. A good one though! I can't explain how exciting this new release is!!! :-D
I would also be very interested in seeing how this would be used in an ASP.NET environment. For example, I don't follow this comment at all:
"When doing an Attach for disconnected scenarios, you can either use a timestamp column with the database to determine if there have been changes, or do a comparison of the values to see if there are any deltas."
Compare *what* values? Are you saying to load another instance of the object (current DB values) then compare to the re-connected object? IMO, this is hinting at a pretty serious design issue. Is it the DataContext that's tracking changes instead of the object
itself? If so, all of your change tracking and undo functionality goes bye-bye if the DataContext is "lost".
9 of 17 04/04/2011 4:07 PM
Using LINQ to SQL (Part 1) - ScottGu's Blog http://weblogs.asp.net/scottgu/archive/2007/05/19/using-linq-to-sql-par...
Wednesday, June 13, 2007 12:22 AM by Kaizenlog » Blog Archive » Java 13/06/2007
How can we return the result of Linq query? Which data type should I use?
I saw an example that was creating a class representing the database table, so the function that queries the data was returning a generic List to this class type. Are there any different and maybe better way to achieve this?
I'll second the calls for Oracle support! As an ISV, I have to write apps that run on SQL Server and Oracle (because that's what clients demand). If LINQ to SQL is really LINQ to SQL Server, then it's a technology I can never use.
Hi Juliano,
In my language feature posts (especially the query syntax one) I cover the return types of LINQ query expressions. In general, you can treat them as IEnumerable<T> sequences - where the type <T> is based on the select clause of the query expression.
Scott
Hi Scott,
I'll cover that topic in an upcoming post later this month hopefully.
Thanks!
Scott
Hi all,
I've just read that many people were wondering how to implement many-to-many relationships with Linq to Sql. Here is one simple possible solution exposed on my blog (source code attached): blogs.msdn.com/.../how-to-implement-a-many-to-many-
relationship-using-linq-to-sql.aspx
Mitsu
Thursday, June 28, 2007 9:35 AM by What Everyone is Excited About - LINQ « Wilfred Mworia’s Blog
Pingback from What Everyone is Excited About - LINQ « Wilfred Mworia’s Blog
Last month I started a blog post series covering LINQ to SQL. LINQ to SQL is a built-in O/RM (object
Hi Soctt,
You have mentioned that when we use Skip().Take(), it uses the ROW_NUMBER() function in SQL 2005 but when i looked at the query generated i do not see this being used. It's using Sub-query to get the correct set of records.I am using Orcas Beta1.
# LINQ to SQL
ScottGu has a 3 part post on his blog about LINQ to SQL . This is a very cool technology, which I hope
Wednesday, July 04, 2007 2:27 AM by Hecgo.com » M??s sobre LINQ y Visual Studio 2008
Pingback from Hecgo.com » M??s sobre LINQ y Visual Studio 2008
Some quick links about LINQ: Articles about extension methods by the Visual Basic team Third-party LINQ
Some quick links about LINQ: Articles about extension methods by the Visual Basic team Third-party LINQ
I finally got around to installing VS2008 Beta 1 on Vista and ran across a few issues. When running web
1. Unless I'm mistaken, Linq to SQL implores an Active Record pattern that, unlike most current ORMs (e.g. NHibernate, WilsonOrMapper), precludes one from going with the Data Mapper (www.martinfowler.com/.../dataMapper.html) approach. Is this correct?
Personally, I have found that an Active Record approach is fine 80% of the time EXCEPT when it comes to remoting your business objects or passing them back-and-forth between web services. As such, I've moved more or less away from the less flexible
Active Record approach ... so I'm wondering, can Linq to SQL be used in a Data Mapper type approach and if so, how?
2. Can the Linq to SQL designer be instructed to generate a single .cs file per class (table)? From a manageability and multi-developer team perspective, having all the partial classes loaded into a single .cs file sucks!
Thanks - greg
Hi Greg,
1) LINQ to SQL actually doesn't use the Active Record pattern. It supports populating entities using a Data Mapper approach, and also doesn't require the entities to subclass from a specific base class (by default the entities don't inherit from anything).
2) I think the LINQ to SQL designer generates all of its classes into a single file - but you can define your own partial classes in separate files if you want.
Scott
10 of 17 04/04/2011 4:07 PM
Using LINQ to SQL (Part 1) - ScottGu's Blog http://weblogs.asp.net/scottgu/archive/2007/05/19/using-linq-to-sql-par...
1. Is there example of using Linq to SQL within the Data Mapper pattern? I'm new to it so maybe I'm missing something.
2. Also, how big of a problem is the fact that Linq to SQL does not natively support Many-To-Many relationships? And why doesn't it given that most every ORM I know of does so??? Personally, as one who currently has this out-of-the-box with my choice
ORM (WilsonORMapper) ... I find this to be a blaring deficiency! I mean, in the database I'm looking at right now I have so many intermediary tables (e.g. Users-UserRoles-Roles) I find it hard to believe it aint supported. Am I missing something???
3. Are there any other types of relationships not supported in Linq to Sql?
- greg
Over the last few weeks I've been writing a series of blog posts that cover LINQ to SQL. LINQ to SQL
Over the last few weeks I've been writing a series of blog posts that cover LINQ to SQL. LINQ to SQL
Hi Greg,
My latest LINQ to SQL Part 4 post shows the data mapper pattern in use a little more. You can see how you can use the DataContext class provides the logic for the insert/update/delete operations - while the data model classes stay ignorant of the underlying
data logic. Ian Cooper has a good post on LINQ to SQL's "persistance ignorance" here that you might find useful: iancooper.spaces.live.com/.../cns!844BD2811F9ABE9C!397.entry
You can handle M:M relationships using an intermediary table with LINQ to SQL (my example in the latest Part 4 of this series shows updates with this). What you can't do it model M:M relationships without an intermediary table. Here is a good blog post that
talks about how you can change the object model to simulate direct relationships without the intermediary table in the object model: blogs.msdn.com/.../how-to-implement-a-many-to-many-relationship-using-linq-to-sql.aspx
Scott
Thursday, July 12, 2007 6:27 AM by LINQ overview and new features in beta 2 | Chris Does Dev
Pingback from LINQ overview and new features in beta 2 | Chris Does Dev
Over the last few weeks Scott Guthrie has been writing a series of blog posts that cover LINQ to SQL.
# LINQ to SQL ( 1)
LINQ to SQL ( 1)
Mijn vriend ScottGu heeft mij deze keer weten te interreseren in: "LINQ To SQL". Gigantisch hoe hij een...
# Valer BOCAN’s Web Log » Blog Archive » Visual Studio 2008 Beta 2 is here!
Thursday, July 26, 2007 5:02 PM by Valer BOCAN’s Web Log » Blog Archive » Visual Studio 2008 Beta 2 is here!
Pingback from Valer BOCAN’s Web Log » Blog Archive » Visual Studio 2008 Beta 2 is here!
So as it turns out, it's been a while since I last posted. Things have been a little nutty around here.
So as it turns out, it's been a while since I last posted. Things have been a little nutty around
Tuesday, July 31, 2007 8:52 PM by All you can LINQ » Quick LINQ link list
Pingback from All you can LINQ » Quick LINQ link list
Probably the biggest programming model improvement being made in .NET 3.5 is the work being done to make
Probably the biggest programming model improvement being made in .NET 3.5 is the work being done to make
Thursday, August 02, 2007 7:23 AM by Getting to know LINQ to SQL » Mark Monster
# The asp:ListView control (Part 1 - Building a Product Listing Page with Clean CSS UI)
One of the new controls in ASP.NET 3.5 that I think will be very popular is the <asp:ListView>
Over the last few weeks I've been writing a series of blog posts that cover LINQ to SQL. LINQ to SQL
11 of 17 04/04/2011 4:07 PM
Using LINQ to SQL (Part 1) - ScottGu's Blog http://weblogs.asp.net/scottgu/archive/2007/05/19/using-linq-to-sql-par...
Over the last few weeks I've been writing a series of blog posts that cover LINQ to SQL. LINQ to SQL
# Linq to SQL
LINQ to SQL is a built-in O/RM (object relational mapper) that ships in the .NET Framework 3.5 release,
# LINQ with SQL Server Compact (a.k.a. DLINQ with SQL CE)
Tuesday, August 21, 2007 4:33 AM by SQL Server Compact - Compact yet capable
Querying data from SSC database gets easier! “ LINQ ” stands for .net L anguage IN tegrated Q uery. LINQ-enabled
Over the last few weeks I've been writing a series of blog posts that cover LINQ to SQL. LINQ to SQL
Over the last few weeks I've been writing a series of blog posts that cover LINQ to SQL. LINQ to SQL
Wer das Blog von Scott Guthrie (1) kennt, kennt sicher auch seine Tutorials über LINQ to SQL (2). Auf
I've never been a fan of ORM tools. I have used several in the past because the client required it,
# LINQ to SQL
Well, as Mabster has already posted , last night I gave a fairly rushed presentation of what is coming
# willcodeforcoffee.com » Blog Archive » LINQ to SQL: The Most Powerful .NET Feature Since C# Attributes
Thursday, September 13, 2007 2:47 PM by willcodeforcoffee.com » Blog Archive » LINQ to SQL: The Most Powerful .NET Feature Since C# Attributes
Pingback from willcodeforcoffee.com » Blog Archive » LINQ to SQL: The Most Powerful .NET Feature Since C# Attributes
# 10 Things I Learned From the September MSDN Event in Atlanta at Die, AJAX!
Wednesday, September 19, 2007 3:00 AM by 10 Things I Learned From the September MSDN Event in Atlanta at Die, AJAX!
Pingback from 10 Things I Learned From the September MSDN Event in Atlanta at Die, AJAX!
It seems to me that the development world is experiencing another period of rapid evolution again, much
InPart1
ofmyLINQtoSQLblogpostseriesIdiscussed
Welcome to the thirty-first edition of Community Convergence. This issue features links to seven very
Tuesday, September 25, 2007 11:22 PM by MSDN Blog Postings » Community Convergence XXXI
Version : VS 2008 Beta 2 In this post, I am going to show you how to build a RSS feed of the employees
Thursday, September 27, 2007 8:33 AM by MSDN Blog Postings » Nachtrag zum BASTA!-Vortrag "LINQ Framework"
Pingback from MSDN Blog Postings » Nachtrag zum BASTA!-Vortrag "LINQ Framework"
Most LINQ to SQL examples you find on the net tend to be written in a way that assumes a connected environment
OverthelastfewweeksI'vebeen
writingaseriesofblogpoststhatcoverLINQtoSQL.
Tom Hollander just posted a note Code Generators: Can't live with them, can't live without them . His
12 of 17 04/04/2011 4:07 PM
Using LINQ to SQL (Part 1) - ScottGu's Blog http://weblogs.asp.net/scottgu/archive/2007/05/19/using-linq-to-sql-par...
Με την έλευση του .NET Framework 3.5 έχουµε και την καινούργια έκδοση της ASP.NET µε αριθµό 3.5. Τι καινούργια
Nachdem Microsoft gestern das neue Visual Studio 2008 ver�ffentlicht hat (siehe auch die News auf Golem.de), habe ich mir heute die Zeit genommen und die Neuigkeiten erforscht. Meiner Ansicht nach ist LINQ (Language Integrated Query) eines der
hei�esten
Με την έλευση του .NET Framework 3.5 έχουµε και την καινούργια έκδοση της ASP.NET µε αριθµό 3.5. Τι καινούργια
Tuesday, November 27, 2007 12:43 AM by ASP.Net 3.5 ??? What???s New « Servitium technology
Pingback from ASP.Net 3.5 ??? What???s New « Servitium technology
OverthelastfewweeksI'vebeenwritingaseriesofblogpoststhatcoverLINQtoSQL.
The ASP.NET 3.5 Extensions CTP we shipped this past weekend contains a bunch of great new features. One
# Rob Conery » ASP.NET MVC: Choosing Your Data Access Method
Friday, December 14, 2007 4:18 PM by Rob Conery » ASP.NET MVC: Choosing Your Data Access Method
Pingback from Rob Conery » ASP.NET MVC: Choosing Your Data Access Method
The ASP.NET 3.5 Extensions CTP we shipped this past weekend contains a bunch of great new features. One
Wednesday, December 19, 2007 12:18 PM by the rasx() context » Blog Archive » Haskell Links
Pingback from the rasx() context » Blog Archive » Haskell Links
The ASP.NET 3.5 Extensions CTP we shipped this past weekend contains a bunch of great new features. One
# LINQ to SQL Add and Delete methods renamed in .NET 3.5 RTM | Steve Glendinning
Sunday, January 06, 2008 11:42 AM by LINQ to SQL Add and Delete methods renamed in .NET 3.5 RTM | Steve Glendinning
Pingback from LINQ to SQL Add and Delete methods renamed in .NET 3.5 RTM | Steve Glendinning
Monday, January 07, 2008 2:33 PM by Programmation : python versus C#3 « Le blog de Patrick Vergain
Pingback from Programmation : python versus C#3 « Le blog de Patrick Vergain
# HowTo: O/R Mapper LINQ to SQL - Einführung & einfaches manuelles Mapping | Code-Inside Blog
Tuesday, January 15, 2008 5:43 PM by HowTo: O/R Mapper LINQ to SQL - Einführung & einfaches manuelles Mapping | Code-Inside Blog
Pingback from HowTo: O/R Mapper LINQ to SQL - Einführung & einfaches manuelles Mapping | Code-Inside Blog
Friday, January 18, 2008 3:19 PM by More Linq to SQL « Jaspers’ Weblog
Med Visual Studio 2008 introduceras flera riktigt stora nyheter för webbútvecklare: Split-vy mellan designläge
Wednesday, January 23, 2008 7:58 PM by Corey's .NET Tip of the Day
Microsoft is finally working on an OR/M tool that looks pretty compelling called LINQ to SQL (previously
# jmcd.nu » Blog Archive » New Project –> Choosing Tools
Sunday, February 10, 2008 7:56 PM by jmcd.nu » Blog Archive » New Project –> Choosing Tools
Pingback from jmcd.nu » Blog Archive » New Project –> Choosing Tools
Sunday, February 10, 2008 11:11 PM by Lightweight Database Abstraction « The Sustainable Software Workshop
Pingback from Lightweight Database Abstraction « The Sustainable Software Workshop
Monday, February 11, 2008 9:51 PM by Andrew L. Van Slaars » LINQ with LINQPad
At last, I found some spare time to start playing with that Linq2SQL thing. Installed VS2008 RTM. fired
Tuesday, February 26, 2008 1:07 PM by CodeMash 2008 « The Sideways Traffic Light
# Detailed Look: Key components in LINQ to SQL and their Key Roles
As part of this blog, I plan to have an on-going set of articles that takes a detailed look into some
# Detailed Look: Key components in LINQ to SQL and their Key Roles
As part of this blog, I plan to have an on-going set of articles that takes a detailed look into some
13 of 17 04/04/2011 4:07 PM
Using LINQ to SQL (Part 1) - ScottGu's Blog http://weblogs.asp.net/scottgu/archive/2007/05/19/using-linq-to-sql-par...
Friday, February 29, 2008 6:58 PM by Jon Kruger’s Blog » LINQ to SQL talk stuff
Pingback from Jon Kruger’s Blog » LINQ to SQL talk stuff
# The Chicken Coop » Blog Archive » Visual Studio 2008 (beta) + .NET 3.5
Thursday, March 06, 2008 9:28 AM by The Chicken Coop » Blog Archive » Visual Studio 2008 (beta) + .NET 3.5
Pingback from The Chicken Coop » Blog Archive » Visual Studio 2008 (beta) + .NET 3.5
Friday, March 07, 2008 1:49 PM by Will’s Blog - LINQ to SQL, WCF, JSON and Flex. Oh My.
Pingback from Will’s Blog - LINQ to SQL, WCF, JSON and Flex. Oh My.
# Tigraine » Blog Archive » LinQ, LinQ to SQL etc explained
Friday, March 07, 2008 3:05 PM by Tigraine » Blog Archive » LinQ, LinQ to SQL etc explained
Pingback from Tigraine » Blog Archive » LinQ, LinQ to SQL etc explained
# madhavrao…
Wednesday, March 12, 2008 6:01 PM by Pointers for starting with LINQ to SQL « Freekshow
Pingback from Pointers for starting with LINQ to SQL « Freekshow
# crimsson.com » Blog Archive » Some very useful articles about LINQ
Friday, March 14, 2008 2:48 PM by crimsson.com » Blog Archive » Some very useful articles about LINQ
Pingback from crimsson.com » Blog Archive » Some very useful articles about LINQ
Monday, March 17, 2008 8:11 AM by Greg Hochard’s Blog » LINQ and ScottGu
# LINQ Resources
Watch Scott`s blog:Part 1 - Einführung in LINQPart 2 - Data Entity Klassen erzeugenPart 3 - Querying databasePart 4 - Updating databasePart 5 - Binding LINQ-Datasource controlsPart 6 - Using Stored Procedures in LINQPart 7 - Updating with Stored
Procedu
Friday, March 28, 2008 12:16 PM by .net tricky. » Blog Archiv » LINQ
Thursday, April 03, 2008 9:51 AM by When WYSIWYG isn’t an option « Consulting in Austin
Thursday, May 15, 2008 12:21 AM by ScottGu - Da LINQ Man! | two geeks~
Tuesday, May 20, 2008 8:31 AM by Joaquim Espinhara » LINQ to SQL - Links
I regret that at my first almost two years of software development, I still coded (sometimes copy and
# Linq to SQL: Pay attention to the two ways of adding objects « delegate () { solve(everything); }
Friday, May 23, 2008 5:53 AM by Linq to SQL: Pay attention to the two ways of adding objects « delegate () { solve(everything); }
Pingback from Linq to SQL: Pay attention to the two ways of adding objects « delegate () { solve(everything); }
Saturday, May 24, 2008 6:52 AM by Linq To Sql or Entity Framework? : The Orbifold
Monday, June 02, 2008 1:02 AM by Just Say No to Manual CRUD | Caffeinated Coder
# Cutting Corners with Visual Studio 2008 and ASP.NET 3.5 « Not Just Another IT Guy
Wednesday, June 11, 2008 5:40 PM by Cutting Corners with Visual Studio 2008 and ASP.NET 3.5 « Not Just Another IT Guy
Pingback from Cutting Corners with Visual Studio 2008 and ASP.NET 3.5 « Not Just Another IT Guy
Wednesday, June 18, 2008 6:08 AM by Broc’s Uni Blog » Blog Archive » Review Questions
Pingback from Broc’s Uni Blog » Blog Archive » Review Questions
In search of a solution to how LINQ to SQL should be used in an N-tier application architecture with...
# Brad Abrams Visits South Africa « liamb.com | software development secret weapons
Monday, June 23, 2008 6:22 PM by Brad Abrams Visits South Africa « liamb.com | software development secret weapons
Pingback from Brad Abrams Visits South Africa « liamb.com | software development secret weapons
# linq where in
14 of 17 04/04/2011 4:07 PM
Using LINQ to SQL (Part 1) - ScottGu's Blog http://weblogs.asp.net/scottgu/archive/2007/05/19/using-linq-to-sql-par...
Friday, July 04, 2008 9:35 AM by Abu Ismail Loves .NET, Jr. Ismail
# Ultracet.
Sunday, July 27, 2008 2:51 PM by Check if a service is installed with ServiceController using LINQ : tryexcept.com
Pingback from Check if a service is installed with ServiceController using LINQ : tryexcept.com
Wednesday, July 30, 2008 10:01 PM by A string of links - LINQ & VB.NET « Technical Aspects in IT
Pingback from A string of links - LINQ & VB.NET « Technical Aspects in IT
LINQ is Language Integrated query. It is a integral part of visual studio 2008 and Microsoft .NET Framework
Saturday, August 02, 2008 9:24 AM by Links for the Weekend, 8-2-2008
Friday, August 08, 2008 1:08 PM by Ardekantur » My Adventures with Entity Framework and Oracle
Pingback from Ardekantur » My Adventures with Entity Framework and Oracle
Saturday, August 30, 2008 10:44 AM by Links for the Weekend, 8-30-2008
# Updating Data Using LINQ To SQL [ C#, ASP.NET Programming] | Tech Dreams
Friday, September 12, 2008 3:50 PM by Updating Data Using LINQ To SQL [ C#, ASP.NET Programming] | Tech Dreams
Pingback from Updating Data Using LINQ To SQL [ C#, ASP.NET Programming] | Tech Dreams
Thursday, September 18, 2008 9:32 AM by Data Management for Clinical Trials
# Flex, .NET 3.5 with LINQ to SQL « Justin J. Moses : Blog
Tuesday, September 23, 2008 1:05 AM by Flex, .NET 3.5 with LINQ to SQL « Justin J. Moses : Blog
Pingback from Flex, .NET 3.5 with LINQ to SQL « Justin J. Moses : Blog
# From the Desk of Brandon Haynes » Using the Linq to Sql Adapter in a DotNetNuke Module
Tuesday, October 14, 2008 5:24 PM by From the Desk of Brandon Haynes » Using the Linq to Sql Adapter in a DotNetNuke Module
Pingback from From the Desk of Brandon Haynes » Using the Linq to Sql Adapter in a DotNetNuke Module
Monday, October 20, 2008 2:19 PM by NVISIA - .NET for Coffee Drinkers
In less than an hour, I've made a COMPLETE web application, from the UI, to the Database including
Saturday, November 22, 2008 4:20 PM by ScottGu’s Using LINQ to SQL (Part 1)
# Bir Yazılımcının Güncesi » Blog Archive » Yazılım Aylığı Mı Olsak Ne?
Saturday, December 06, 2008 1:00 PM by Bir Yazılımcının Güncesi » Blog Archive » Yazılım Aylığı Mı Olsak Ne?
Pingback from Bir Yazılımcının Güncesi » Blog Archive » Yazılım Aylığı Mı Olsak Ne?
Tuesday, December 16, 2008 6:55 AM by Don’t get spoiled by LinQ To SQL | Tigraine
Saturday, December 20, 2008 6:31 PM by How to Create a TagCloud Using LINQ and ASP.NET - kosta.apostolou.ca
Pingback from How to Create a TagCloud Using LINQ and ASP.NET - kosta.apostolou.ca
15 of 17 04/04/2011 4:07 PM
Using LINQ to SQL (Part 1) - ScottGu's Blog http://weblogs.asp.net/scottgu/archive/2007/05/19/using-linq-to-sql-par...
Thursday, January 08, 2009 10:51 AM by Common tips and tricks from a SQL Developer Support perspective
Ok, today I will show how to create a super simple application that uses some of the new stuff you find
Friday, January 16, 2009 4:34 AM by Uploading Binary files or Images using LINQ to SQL | Aneef.Net
Saturday, January 17, 2009 10:17 PM by LINQ Resources « Vakul Kumar More
Monday, January 19, 2009 9:02 AM by [Linq To SQL] Apprendre (et comprendre) Linq To SQL | How To ...
Pingback from [Linq To SQL] Apprendre (et comprendre) Linq To SQL | How To ...
# .NET 4.0 - Things to come and go… « _DotNetStuff and more…
Wednesday, January 21, 2009 1:35 PM by .NET 4.0 - Things to come and go~ « _DotNetStuff and more~
Pingback from .NET 4.0 - Things to come and go… « _DotNetStuff and more…
# Building a Data Layer Using LINQ to SQL and Stored Procedures (Part 1) « DevExpertise
Friday, January 30, 2009 11:15 AM by Building a Data Layer Using LINQ to SQL and Stored Procedures (Part 1) « DevExpertise
Pingback from Building a Data Layer Using LINQ to SQL and Stored Procedures (Part 1) « DevExpertise
# Ajax search using Jquery, client side templates and ASP.NT MVC
Wednesday, February 18, 2009 6:26 AM by Dean Nolan Freelance Software Development Blog
I wrote in a previous post about “live search” using ASP.NET and Javascript. This was the term that I had seen around that described search that when you type your query, results are filtered “live” on the page without a postback to the server. ...
LINQ to SQL (Part 5 - Binding UI using the ASP:LinqDataSource Control) Over the last few weeks I've
Wednesday, February 25, 2009 1:36 AM by Toronto Coffee and Code #2 at Le Gourmand
Wednesday, February 25, 2009 1:44 AM by Toronto Coffee and Code #2 at Le Gourmand ??? Global Nerdy
Pingback from Toronto Coffee and Code #2 at Le Gourmand ??? Global Nerdy
# LINQ to SQL
LINQtoSQL
UsingLINQtoSQL(Part1)
Saturday,May19,200712:41AM
...
# LINQTOSQL - Tuturials
LINQTOSQL - Tuturials
# ASP.NET Dynamic Data and Displaying Images with a Custom Field Template
Awhile back, I posted about creating an image handler to render images stored in a database .  Someone
# ASP.NET MVC: Choosing Your Data Access Method « Ngocthanhit Homepage
Friday, March 27, 2009 11:01 PM by ASP.NET MVC: Choosing Your Data Access Method « Ngocthanhit Homepage
Pingback from ASP.NET MVC: Choosing Your Data Access Method « Ngocthanhit Homepage
Saturday, March 28, 2009 4:19 AM by ASP.NET MVC Archived Blog Posts, Page 1
Saturday, April 11, 2009 11:13 PM by LINQ to SQL « Code Gelamen « database schema
Pingback from LINQ to SQL « Code Gelamen « database schema
Sunday, April 12, 2009 2:25 AM by LINQ to SQL « Code Gelamen « database schema
Pingback from LINQ to SQL « Code Gelamen « database schema
16 of 17 04/04/2011 4:07 PM
Using LINQ to SQL (Part 1) - ScottGu's Blog http://weblogs.asp.net/scottgu/archive/2007/05/19/using-linq-to-sql-par...
Wednesday, May 06, 2009 1:23 PM by LINQ To SQL Very Slow Performance Without Compile (CompileQuery) | PeterKellner.net
Pingback from LINQ To SQL Very Slow Performance Without Compile (CompileQuery) | PeterKellner.net
Thursday, May 07, 2009 3:26 PM by seiti.eti.br » Boas pr??ticas em Linq To Sql
# Creating parameterized Solver Foundation models using LINQ to SQL | Coded Style
Monday, May 11, 2009 11:41 PM by Creating parameterized Solver Foundation models using LINQ to SQL | Coded Style
Pingback from Creating parameterized Solver Foundation models using LINQ to SQL | Coded Style
Monday, May 18, 2009 3:25 PM by LINQ 101: Getting Started with LINQ | Adventures In Development
Pingback from LINQ 101: Getting Started with LINQ | Adventures In Development
# Ajax search using Jquery, client side templates and ASP.NT MVC
Ajax search using Jquery, client side templates and ASP.NT MVC
# 780 Requests Per Second Verses 110, You Really Need to Compile your LINQ to SQL (LINQ2SQL) Queries | PeterKellner.net
Tuesday, June 09, 2009 1:21 AM by 780 Requests Per Second Verses 110, You Really Need to Compile your LINQ to SQL (LINQ2SQL) Queries | PeterKellner.net
Pingback from 780 Requests Per Second Verses 110, You Really Need to Compile your LINQ to SQL (LINQ2SQL) Queries | PeterKellner.net
Thursday, June 18, 2009 11:59 AM by Adventures in IDisposable » NerdDinner, and initial thoughts on MVC
Pingback from Adventures in IDisposable » NerdDinner, and initial thoughts on MVC
Entity Framework 4.0 will provide us with POCO support. That’s good because Entity Framework supports
Entity Framework 4.0 will provide us with POCO support. That’s good because Entity Framework supports
Saturday, July 18, 2009 5:34 AM by L??r ?? bruke Linq « PingIT – Tanker til en IT mann
Pingback from L??r ?? bruke Linq « PingIT – Tanker til en IT mann
LLBLGenPro is an object relational mapper which generates code for the data access layer using the database
LLBLGenPro is an object relational mapper which generates code for the data access layer from the database
Wednesday, August 12, 2009 7:30 AM by Carsonified » More Screenshots, Code Snippets and Wireframes
Pingback from Carsonified » More Screenshots, Code Snippets and Wireframes
# LINQ to SQL (Part 2 – Defining our Data Model Classes) | Vietnam Developer Club
Saturday, October 10, 2009 11:45 AM by LINQ to SQL (Part 2 – Defining our Data Model Classes) | Vietnam Developer Club
Pingback from LINQ to SQL (Part 2 – Defining our Data Model Classes) | Vietnam Developer Club
# LINQ to SQL (Part 6 – Retrieving Data Using Stored Procedures) | Vietnam Developer Club
Saturday, October 10, 2009 12:19 PM by LINQ to SQL (Part 6 – Retrieving Data Using Stored Procedures) | Vietnam Developer Club
Pingback from LINQ to SQL (Part 6 – Retrieving Data Using Stored Procedures) | Vietnam Developer Club
# LINQ to SQL (Part 8 – Executing Custom SQL Expressions) | Vietnam Developer Club
Saturday, October 10, 2009 12:26 PM by LINQ to SQL (Part 8 – Executing Custom SQL Expressions) | Vietnam Developer Club
Pingback from LINQ to SQL (Part 8 – Executing Custom SQL Expressions) | Vietnam Developer Club
# LINQ to SQL (Part 9 – Using a Custom LINQ Expression with the control) | Vietnam Developer Club
Saturday, October 10, 2009 12:27 PM by LINQ to SQL (Part 9 – Using a Custom LINQ Expression with the control) | Vietnam Developer Club
Pingback from LINQ to SQL (Part 9 – Using a Custom LINQ Expression with the control) | Vietnam Developer Club
Terms of Use
17 of 17 04/04/2011 4:07 PM