Frans Bouma's blog
The blog of Frans Bouma, creator and lead developer of LLBLGen Pro and ORM Profiler.
-
Deferred execution in Linq pitfall(s)
Say you have this query in Linq to Sql
// C# int id = 10254; var q = from o in nw.Orders where o.OrderID = id select o; // some other code id++; foreach(var o in q) { // process o. } -
Developing Linq to LLBLGen Pro, Day 5
(This is part of an on-going series of articles, started here)
-
Developing Linq to LLBLGen Pro, Day 4
(This is part of an on-going series of articles, started here)
-
Developing Linq to LLBLGen Pro, day 3
(This is part of an on-going series of articles, started here)
-
Developing Linq to LLBLGen Pro, day 2
(This is part of an on-going series of articles, started here)
-
Developing Linq to LLBLGen Pro, Day 1
(This is part of an on-going series of articles, started here)
-
Developing Linq to LLBLGen Pro, Day 0
Now v2.5 of LLBLGen Pro is out the door and the release-stress has gone away, it's time to pick up the next project, which is Linq support for LLBLGen Pro, which will be rolled into v2.6 of LLBLGen Pro, which is scheduled for Q4 2007.
-
LLBLGen Pro v2.5 has been released!
Back in January 2007 we started designing and developing LLBLGen Pro v2.5, and it's finally here!
When you develop a framework, at a given moment in time you'll wonder: "Ok, now that I have all the basics covered, which direction shall I go into now, what are the more meaningfull additions to the framework?", and we came to the conclusion that a more framework focussed approach was best, instead of adding more into UI oriented fluff like generating user interfaces (we still can do that though with a set of templates we developed, but it's not the core of the design). So, we added more entity management features, made the framework richer with a Dependency Injection mechanism and of course the usual set of new databases. -
Just in case you're using VS.NET 2008 Beta 2 with C#...
If you're using C# and VS.NET 2008 and you're typing some code like:
CustomCollection<MyType> items = new CustomCollection<MyType>() foreach(OtherType other in OtherTypeCollection) { items.Add(CreateItemFromOtherType(other)); }where CustomCollection<MyType> implements IList explicitly (void IList.method(params) {} ), you will run the risk that the IDE collapses with a crash. This is a known bug and it is fixed before RTM (yay!), but it still can cause headaches for the early-adopters of MS' next IDE. So you have been warned
.
Full report here. -
VS.NET 2008 Beta 2 / .NET 3.5: Windows Forms ComboBox contains nasty bug.
The Windows Forms combobox control contains a nasty a lot of people who will try .NET 2.0 applications on .NET 3.0 will run into: the Sorted property makes comboboxes unable to bind to data: they stay empty. This is particular bad, because any solid working application for .NET 2.0 using comboboxes in a databinding scenario (and I estimate a lot of applications fall into that category) which uses the Sorted property to get sorted results will run into this problem, and it has huge consequences: any user who has .NET 3.5 installed will run into this, no matter what you defined as supportedRuntime in the .config file of your application.