
linq
Get flash to fully experience Pearltrees
Zip operator in Linq with .NET 4.0 - DotNetJaps
C# 4.0 in a Nutshell - LINQBridge
LINQBridge You might already have discovered that LINQ is addictive : once you're accustomed to solving problems through slick functional queries, it really hurts being forced back to the imperative style of C# 2.0! LINQ's query operators are implemented from .NET Framework 3.5. And here lies a difficulty: your clients might have only Framework 2.0 installed on their machines .SP 2010: Getting started with LINQ to SharePoint in SharePoint 2010 - Tobias Zimmergren's thoughts on development
Author: Tobias Zimmergren http://www.zimmergren.net | http://www.tozit.com | @zimmergren In SharePoint 2010 you now have the ability to use LINQ syntax to fetch items from your lists instead of using the "traditional" approach of CAML queries. (Including SPSiteDataQuery and SPQuery objects) In this article I will give you a brief introduction to how you can get started using LINQ queries in SharePoint, also known as LINQ to SharePoint .This is the last of my posts on LINQ before switching over to Beta2; I’m playing catch-up but be aware that some things will have changed. I will post any changes for Beta 2 to both this and Being Ignorant in LINQ to SQL as time permits. What are Specifications? Specification is a design pattern authored by Martin Fowler and Eric Evans. If you are not familiar with specifications then you can read more about them in Eric Evans book Domain Driven Design, or just read this comprehensive paper . If you are not sure what Specifications are, you might want to read that before you read this.
Specifications in C# 3.0 - Windows Live
Kirk Evans Blog : Calling SharePoint Lists Web Service Using WCF
LINQ provider basics
Learn how to create custom LINQ providers. Introduction LINQ (Language Integrated Query) works as a middle tier between data store and the language environment. From a developer's point of view, it is just a new pattern for querying data from multiple data structures directly in the IDE.Batch deletion in the O/R Mapping frameworks is always depressing. We need to query all the entities we want to delete from the database, pass them to the DeleteOnSubmit or DeleteAllOnSubmit methods of DataContext, and finally invoke SubmitChanges to delete the records form database. In this case, we will cost an additional query and send lots of "DELETE" commands to database. How wasteful!
LINQ to SQL Extension: Batch Deletion with Lamb...
I posted an article the other day showing you how to exploit the query capabilities of LINQ to do reflection over the attributes on a C# class. I want to show you how to exploit some of the extension methods in System.Query to make the code even cleaner. I used a method called Members that got all of the members in order of member type (i.e. fields first, properties next and so on). The code looked like this: public static IEnumerable<MemberInfo>Members( this Type t) { foreach (FieldInfo fi in t.GetFields()) yield return fi; foreach (PropertyInfo pi in t.GetProperties()) yield return pi; foreach (MethodInfo mi in t.GetMethods()) yield return mi; foreach (EventInfo ei in t.GetEvents()) yield return ei; } I needed to split the queries into each of the types we required in order to get elements ordered by type.
LINQ & Reflection in C# 3.0 « The Wandering Gli...
David Ebbo's ASP.NET blog : Dynamic Data at MIX...
Solving LINQ's N-Tier Issues - Bryan Sampica
Ok, so maybe solving is somewhat of a misnomer, but we certainly can combat them with strength and conviction. A little background on the subject first; LINQ has proven to be somewhat of a booger when attempting to work with it in a streamlined development environment when incorporating any sort of N-Tier pattern. Why you ask should it be a problem...the common answer I've heard many many times is, why should it be any different? You have at the essence of it some pretty simple logical and physical layer guidelines right? It's well known in the industry at this point to create N-Layer app's to solve things like SOC (separation of concerns) and physical or network boundaries.Parallel LINQ Running Queries On Multi-Core Processors Joe Duffy and Ed Essey THis article is based on the Parallel FX library, which is currently in development. All information herein is subject to change. Multi-core processors are here.
Parallel LINQ: Running Queries On Multi-Core Pr...
10 Tips to Improve your LINQ to SQL Application...
Hey there, back again. In my first post about LINQ I tried to provide a brief(okay, bit detailed) introduction for those who want to get involved with LINQ to SQL. In that post I promised to write about a basic integration of WCF and LINQ to SQL working together, but this is not that post. Since LINQ to SQL is a code generator and an ORM and it offers a lot of things, it is normal to be suspicious about performance of it. These are right up to a certain point as LINQ comes with its own penalties.A couple weeks ago, I read the article, LINQ to SQL Extension: Batch Deletion with Lambda Expression by Jeffrey Zhao. In case you didn't read the article, it discusses the downside of most O/R Mapping frameworks when it comes to multiple updates or deletes. He states the fact that a SQL statement for each row flagged as update/delete in the entity set is created. I went about implementing something similar to what Jeffrey envisioned and I'll explain some of the hurdles I had to overcome to achieve it.
Batch Updates and Deletes with LINQ to SQL
27th March 2009. It's now a year since I wrote this post. Thanks to some comments by Janus2007 I've realised that it needs updating.

