Upgrading to 2.6 problems

Posts   
 
    
BexMed
User
Posts: 63
Joined: 18-Jul-2007
# Posted on: 10-Jun-2008 14:12:29   

Hello

We have quite a large project using llbl 2.5 (adapter) and we have recently moved it over to VS 2008 and now want to upgrade to llbl 2.6 using the 3.5 dlls.

For some reason I am finding this very difficult, and the documentation doesn't appear to help. I have updated all the dlls that are referenced in the project to the 3.5 ones and opened the lgp file with 2.6 and set the .net version drop down to 3.5 and regenerated. This caused all the referenced dlls in my project to revert back to the .net 2 ones.

I have a feeling I need to update the template, but I don't know how to do this. Obviously I am missing something, though what it is is completely eluding me.confused

Could you give me some advice?

Thanks

Bex

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39614
Joined: 17-Aug-2003
# Posted on: 10-Jun-2008 14:26:25   

You refer to .net 3.5 versions of assemblies, which assemblies exactly? Did you generate code on top of the v2.5 code base?

The code generator doesn't alter any reference to any assembly, you've to do that manually.

Frans Bouma | Lead developer LLBLGen Pro
BexMed
User
Posts: 63
Joined: 18-Jul-2007
# Posted on: 10-Jun-2008 15:14:27   

Yes I did generate the code on top.

The 3 main projects EntityLayer, SchemaImporter and SqlServerDataLayer all have a reference to sd.llblgen.pro.ormsupportclasses.net20. I deleted this reference and added the SD.LLBLGen.Pro.ORMSupportClasses.CF35.dll and SD.LLBLGen.Pro.LinqSupportClasses.NET35.dll (as I wasn't sure which I needed) but regenerating recreated these projects and put them back as they were with the sd.llblgen.pro.ormsupportclasses.net20.

I know this sounds silly.. but its completely regening the whole projects.

Bex

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39614
Joined: 17-Aug-2003
# Posted on: 10-Jun-2008 17:00:25   

BexMed wrote:

Yes I did generate the code on top.

The 3 main projects EntityLayer, SchemaImporter and SqlServerDataLayer all have a reference to sd.llblgen.pro.ormsupportclasses.net20. I deleted this reference and added the SD.LLBLGen.Pro.ORMSupportClasses.CF35.dll and SD.LLBLGen.Pro.LinqSupportClasses.NET35.dll (as I wasn't sure which I needed) but regenerating recreated these projects and put them back as they were with the sd.llblgen.pro.ormsupportclasses.net20.

I know this sounds silly.. but its completely regening the whole projects.

Bex

You should keep referring to sd.llblgen.pro.ormsupportclasses.net20, as there's no specific .NET 35 build, as that's not necessary. The CF35 build is for compact framework 3.5. See: http://www.llblgen.com/documentation/2.6/hh_goto.htm#Using%20the%20generated%20code/gencode_compiling.htm

Could you check for me please if you set the reference to the ORMSupportClasses .NET 2.0, and regenerate, that it keeps referring to that same dll ? Here we generate our unittest projects on top of existing code all the time and it works OK.

Frans Bouma | Lead developer LLBLGen Pro
BexMed
User
Posts: 63
Joined: 18-Jul-2007
# Posted on: 10-Jun-2008 17:38:47   

That did the trick! I didn't realise that I needed the new .net 2 ones as well.

Thank you