RightHand's community place

Here is an example where an extension method is useful. Take this LLBLGen Pro code for example: public EntityCollection<CustomersEntity> GetCustomers() { using (DataAccessAdapter da = new DataAccessAdapter("Data Source=[SERVER];Initial Catalog=Northwind;Integrated Security=True")) { LinqMetaData context = new ...

I posted both slides and demo code from my "Making ORM applications more secure/Naredimo ORM aplikacije varnejše" presentation held at Bleeding Edge conference in Portorož on 1.10.2008.The material is in Slovene language. Enjoy.

I am proud to announce that today, after years of experience with LLBLGenPro development, I've become an official LLBLGenPro partner. As such I am offering consultancy and development with LLBLGenPro, the #1 ORM product for .net. Do you want to speed up your database application development, reduce the number of errors in code, develop a ...

LLBLGen Pro v2.6 is released and a free upgrade to v2.x customers. The major feature of this release is Linq to LLBLGen Pro, as Frans said, ''one of the most feature-rich Linq providers available on .net today''. Having tested beta versions I can only say the this version is a step in right direction. Great work, Frans.

My favorite ORM tool just got better - Frans implemented Linq to LLBLGen Pro. He really implemented it to the last detail as he writes in a series of blog post (a must read for everybody doing LINQ to an ORM product). If you are a customer go grab the beta bits. If you are not, well, it is a reason more to become one.

I have to say that I like LINQ to SQL, heck, I even do presentations about it. So, it is a cute ORM. What is that good about it features LINQ. However, there are some serious showstoppers in there. One are more serious than the others. I won't deal with what's good about LINQ to SQL, rather I'll dive into showstoppers as I see them. So, let's ...