Browse by Tags
All Tags »
Linq (
RSS)
Last time I introduced LLBLGen Pro QuerySpec , a new fluent API for specifying queries for LLBLGen Pro . As promised I'll write a couple of blogposts about certain aspects of the new API and how it works. Today I'll kick off with the basics. Two types...
In the past two months I've been busy creating a new query specification API for LLBLGen Pro . Our native query API is modeled after SQL statement fragments (like a 'predicate', a 'relationship', a 'field'), but specifying a query with it can be a little...
Today I ran into a breaking change in .NET 4 which I couldn't find in the documentation. It's about binding a linq to objects query to a BindingSource's DataSource in winforms. The code works properly in .NET 3.5, but crashes in .NET 4: _firstRelationshipsBindingSource...
For the people who know me a little it's no surprise, but in case you didn't know: I love algorithms. I think they're the cornerstone of good software and they should be your first source of wisdom for every piece of software you're creating. This post...
If you're using Linq and Resharper, you've probably seen the warning Resharper shows when you use a foreach loop in which you use the loop variable in a Linq extension method (be it on IQueryable<T> or IEnumerable<T>). In case you don't know...
In the first part of this series I talked about the fact that Linq to LLBLGen Pro is a full implementation of Linq and why it's so important to use a full linq provider instead of a half-baked one. Today, I'll discuss a couple of native LLBLGen Pro features...
Some people asked me what the highlights are of Linq to LLBLGen Pro , which was released this week , as it seems that Linq support is apparently growing on trees these days. In this and some future posts I'll try to sum up some of the characteristic features...
After almost 11 months of design, development, beta testing and adding final polish, it's here: LLBLGen Pro v2.6 ! This version, which is a free upgrade for all our v2.x customers, has a couple of major new features, the biggest of course being the full...
UPDATE I tested this initially with EmployeeID and noticed the strange behavior. Writing this blogpost I thought the max of the employeeID was a little artificial, so I changed that in OrderDate. But... what happened (see my reply to this blogpost below...
Imagine, you're sitting at your desk and you're using the Linq to Sql designer in VS.NET 2008 and you have, say, 50 entities in your model. You're happy about how things are progressing. It took a while to get the model set up, considering the wicked...
More Posts
Next page »