April 02, 2008

LLBLGen Pro Suggested Relationship Naming Convention

LLBLGen Pro is our current data access and business logic layer of choice at emediaIT and we are now looking into using LINQ to LLBLGen Pro for future projects. It really is an awesome framework...

LLBLGen Pro generates a complete data-access tier and business objects tier for you (in C# or VB.NET), utilizing powerful O/R mapping technology and a flexible task-based code generator, allowing you to at least double your productivity!

...and I would recommend it to anyone. Their support and lead developer, Frans Bouma (Just re-awarded his MVP status), are also excellent.

We do however have issues with some of the default designer and project settings (although they do allow you to customise/set a great deal of things) in that if you have more than one relationship from one entity to another the default naming convention is...

...which leads to relationships being named .Entity_ and even .Entity__ etc if there are sufficient relationships.

I feel that the default settings should be something more like...

I am sure however that they have a good reason for have left it more customisable/open though, most likely just for greater flexibility.