Hi --

I'm wondering how you all have or are handling this.

Basically, for new web projects we are going to be using ASP.Net 2.0 and LLBLGen Pro 2. For existing projects, we'll migrate them to LLBL Gen Pro 2 but target the .Net 1.1 run time. (We use self servicing for our projects.)

We've got a smallish library where we have some common llblgen utility routines as well as non-llblgen specific routines.

Do you all know of a way that I can keep 1 LLBLGen library that will run on both .Net 1.1 and 2.0? The first problem I ran into was with the EntityCollectionBase since it uses generics. Also, since the DLLs for the ORMSupportClasses are named differently between .Net 1 and 2, I'm not sure that it is even possible.

I was thinking about doing the following:

1. Create a new project for LLBLGen 2, using .Net 2.0 and migrate the code to .Net 2.0. .Net1 projects would reference a version 1.0 library while .Net2 projects would reference the new 2.0 library.

What naming convention do you all prefer? Just using a suffix as LLBLGen Pro does?

Thanks, -Ryan Casey

Hi,

The dll targetting .Net 1.1 should be accessible from .Net 2.0. To my knowledge there is no backward compatibility issue. So if you need to keep some projects referencing the generated code in .Net 1.1, and don't want to maintain two sets of generated code, having your new ASP.Net 2.0 projects reference common .Net 1.1 libs should be possible.

Jessynoo wrote:

So if you need to keep some projects referencing the generated code in .Net 1.1, and don't want to maintain two sets of generated code, having your new ASP.Net 2.0 projects reference common .Net 1.1 libs should be possible.

The problem that I think I would run into is that the LLBLGen Pro 2 .Net 2.0 ORMSupport library is not "compatible" with the .Net 1.1 ORMSupport library. (At least I don't think it would be since EntityCollectionBase is a generic collection now in .Net 2 code.) Or am I missing something?

Thanks.

.NET 2.0 wouldn't be compatible, but there is a .NET 1.1 library that is referenced when generating using the Target Platform .NET 1.1.

bclubb wrote:

.NET 2.0 wouldn't be compatible, but there is a .NET 1.1 library that is referenced when generating using the Target Platform .NET 1.1.

Ok, thanks!