Do you have any idea when the next major version will be released? I am about to start a new project and one of the decisions will be what version of LLBLGen we'll use. Changing from v2.6 to a later version will be possible in the next 3 - 6 months, but this will not be an option after that time.

Thanks

absintpm wrote:

Do you have any idea when the next major version will be released? I am about to start a new project and one of the decisions will be what version of LLBLGen we'll use. Changing from v2.6 to a later version will be possible in the next 3 - 6 months, but this will not be an option after that time. Thanks

v3 isn't expected before august. Development is going well, but the scope is huge so the version needs its time to get to the quality we want to provide.

We don't add new features to v2.x but will keep on supporting that. so if you use v2.6 today and you'll find a bug after v3 has been released you'll still get it fixed.

Can I find anywhere a list of new features that you intend to have in v3.0?

I'm not sure if it can be officially made public. But I'll escalate your request.

Its not a must. If LLBLGen 3.0 is released (not beta) before our application we can upgrade just before releasing it (hopefully that will not give us too much trouble). If not... then we'll release it with v2.6.

absintpm wrote:

Its not a must. If LLBLGen 3.0 is released (not beta) before our application we can upgrade just before releasing it (hopefully that will not give us too much trouble). If not... then we'll release it with v2.6.

Of the features which are made public already: - support for (besides our own framework) NHibernate, entity framework, linq to sql (and likely others post release) - xml project file - support for model first (so define entities first, then map them to meta-data) - support for multiple database types in 1 project (so oracle and sqlserver meta-data in 1 project with 1 set of entities) - support for value types (which can contain value typed fields) so you can create a value type called 'Address' for example with fields Street, City, Country, Housenr, and in an entity you can define a field 'VisitingAddress' for example of type Address. - support for mixing of inheritance hierarchy types in 1 hierarchy - new typed list editor - model diagrams - template editor inside the designer

and some nice stuff I won't talk about now but which will blow you away

Are there any plans that LLBLGen Pro v.3.0 is integrated as a plugin in Visual studio (like entitityframework is)?

Thanks.

asa75 wrote:

Are there any plans that LLBLGen Pro v.3.0 is integrated as a plugin in Visual studio (like entitityframework is)?

Thanks.

No, not as in: you open an entity editor and it becomes a tab in VS.NET 2008. The reason is simple yet perhaps not that obvious: VS.NET is a file based IDE. This means that if you want to have a tab open for some object, it in fact has to be a File being edited. This isn't the case in our designer: it's a model which is edited partially through various editors. The alternative is to have a designer completely as 1 tab, but this isn't really useful.

Perhaps it's possible with very deep integration however from what I've read of the vs.net 2008 SDK docs, it's not really going to work.

We will look into adding an automatic open action when you double click the file in vs.net so the designer opens automatically, and also (but this might be impossible) to find out the solution target so we can generate code automatically into the solution open.

VS.NET integration makes sense when you work with files in a solution. As soon as you leave that and work with elements in a model, it's not really compatible.

Otis wrote:

• support for (besides our own framework) NHibernate, entity framework, linq to sql (and likely others post release)

Hi,

any plans to support CSLA.NET? With the support it offers for WPF and Silverlight and considering that there aren't any good domain based code generators available for it. it seems like a great fit (the available code generators are often not domain but table based, and often generate stored procs for usage).

Thanks for considering it, Patrick

pat wrote:

Otis wrote:

• support for (besides our own framework) NHibernate, entity framework, linq to sql (and likely others post release)

Hi,

any plans to support CSLA.NET? With the support it offers for WPF and Silverlight and considering that there aren't any good domain based code generators available for it. it seems like a great fit (the available code generators are often not domain but table based, and often generate stored procs for usage).

Thanks for considering it, Patrick

After the initial release we'll look at other frameworks to support and they are a candidate. Our goal is to make our designer THE designer for data-access and data model related work, as all meta-data is available and manageable. So in the end we hope to achieve that all o/r mapper frameworks on .net are supported by our designer.

V3 will offer rich support for stored procs btw, like mapping typed views on stored proc resultsets and entities as well (multi-fetch and CUD operations). We found a reliable way to obtain meta-data for resultsets of procs, even if the proc uses a temptable, and for all databases, including mysql (not MS access unfortunately). See attached screenshot . So for example iBatis as targetframework is one of the possibilities as well.

If you ever need someone to do testing let me know. I've been using the tool since the stored proc version.

Before beta starts we'll ask for beta-testers to apply, and we'll be looking for active testers with a variety of different setups (so we cover all bases/ground). I think it will be around august that we'll post this, maybe sooner .