Hi Frans,

I would like to know why I should upgrade to 3.1 from 2.6? Here is what I am doing. I am creating a Winforms standalone desktop application with Visual Studio 2008 Enterprise, LLBLGen 2.6, DevExpress, SQL Server Compact Edition 3.5, .NET 3.5. I do not use NHibernate, Linq to SQL, or Entity Framework. I am 80% done!

Does 3.1 help you to automatically do CRUD? If so, I would definitely upgrade. I find that doing simple one-to-many CRUD tasks using 2.6 takes an incredible amount of code. If I was starting on a new project I would definitely upgrade. But I am not planning on doing any more .NET applications after this one. However, I will be maintaining this application (and adding new functionality) for years to come.

So, based on what I am saying, give me a good reason to upgrade.

Rene

What does 'automatically do CRUD' mean? generate winforms dialogs etc.? then.. no. The designer is rewritten and build from the ground up, with model first now inside the designer, so you can alter your db from your model. This might sound something you dont want at first, but it's easier this way.

Why not give the new designer a spin and see for yourself? To see what's new in v3.0 and v3.1's runtime framework (so you get these benefits in your project) see the 'what's new in the runtime framework docs here: http://www.llblgen.com/documentation/

e.g. mapping typed views onto stored proc resultsets, native enum support, much faster entity creation / prefetch path node merging, WCF ria services support...