What are the major changes going into version 2.0? I know about inheritance, but will there be any changes to the interfaces of either the generated code or the ORMSupportClasses?

v2.0 will be a refactored framework. There will be a lot of changes behind the scenes, one of the core changes is that there will be just 1 core: adapter, and that selfservicing will be a wrapper around adapter. This keeps the code base smaller and more maintainable. Also generics and partial classes will be used. This has for example the effect of almost making 'EntityCollection' a class which will become very small.

I'll do everything I can to make the framework look like the current framework as in: interface usage, so porting the code over to 2.0 will not be a tedious task. The usage of generics alone already requires that porting code over will take some time, but I'll try to make that as effortless as possible.

What will be kept is the predicate/relations system etc. and which will be extended by operator overloading to ease the construction of filters. (which will be added to C# in 1.0.2005.1). This will ease the porting for quite a bit.

v2.0 will furthermore have new features I'm not going to talk about here as we know our competitors read this forum as well. You can be sure it will be great

The code of 1.0.2005.1 will be kept as well in v2.0 and will be extended to have support for the new features planned. This means that if you're on .NET 1.x you still can use the features of v2.0 of LLBLGen Pro.

Thanks for your response

We will be starting the building of a new framework very soon (next couple of weeks) and are planning on using .NET 2.0 (VS 2005). Do you think it would be wise to code against 1.0.2005.x? I suppose the only alternative would be to wait for at least a beta of LLBLGEN Pro 2.0 and code against that but it doesn't sound like you release betas...is this correct?

Also, you mentioned that you will use partial classes. I'm assuming that this means all generated code will reside in partial classes and there will be "user editable" main classes for each partial class. Is this something you can discuss at this point?

mikeg22 wrote:

Thanks for your response

We will be starting the building of a new framework very soon (next couple of weeks) and are planning on using .NET 2.0 (VS 2005). Do you think it would be wise to code against 1.0.2005.x? I suppose the only alternative would be to wait for at least a beta of LLBLGEN Pro 2.0 and code against that but it doesn't sound like you release betas...is this correct?

1.0.2005.1 will bring new features you might want to use, so why wait? The thing is: because you start with .NET 2.0 when it's in beta, you will run the risk of having to port code. That's inevitable, if it's not llblgen pro code, it might be .NET 2.0 code because they changed some api call.

Betas are released to the customers when they arrive. So 1.0.2005.1 will first go into beta for customers, and after the beta cycle is complete it will be released in full. For v2.0, beta-testers will be selected, as it contains a license change as well, but beta for 2.0 isn't expected before december 2005.

All code will be runnable on .NET 2.0, you can be sure of that. the v2.0 framework will be different in some areas and the same in other areas.

Also, you mentioned that you will use partial classes. I'm assuming that this means all generated code will reside in partial classes and there will be "user editable" main classes for each partial class. Is this something you can discuss at this point?

Yes, all classes will be generated as partial classes. That means that you can add another class file yourself and add code there, so you can re-generate the code without problems.

Otis wrote:

Betas are released to the customers when they arrive. So 1.0.2005.1 will first go into beta for customers, and after the beta cycle is complete it will be released in full. For v2.0, beta-testers will be selected, as it contains a license change as well, but beta for 2.0 isn't expected before december 2005.

Whoa, lets hope that I become an expert on LLBLGen Pro by the time that happens. I would love to be a golden boy too

Beta-testers are handpicked, get a free license, but also have to test. This means doing production work with the app, not kicking the tires

Otis wrote:

Beta-testers are handpicked, get a free license, but also have to test. This means doing production work with the app, not kicking the tires

, lol