I just upgraded from 2.5 to 2.6. Done by uninstalling 2.5, then installing 2.6.

Next I opened a project from 2.5 and ran the generator. Unfortunately, the newly generated project won't compile (It's type adaptor targeting .NET2). The first compile error is (amongst many others):

"Error 1 'SD.LLBLGen.Pro.DQE.SqlServer.DynamicQueryEngine' does not contain a definition for 'FactoryToUse'"

This was in DatabaseSpecific\DataAccessAdapter.cs 475 76

Looking at the project files, possibly it's because the dll references aren't changed, eg the .csproj file has:

<ItemGroup> <Reference Include="SD.LLBLGen.Pro.ORMSupportClasses.NET20, Version=2.5.0.0, Culture=neutral, PublicKeyToken=ca73b74ba4e3ff27, processorArchitecture=MSIL"> <SpecificVersion>True</SpecificVersion> <HintPath> </HintPath> </Reference> <Reference Include="SD.LLBLGen.Pro.DQE.SqlServer.NET20, Version=2.5.0.0, Culture=neutral, PublicKeyToken=ca73b74ba4e3ff27, processorArchitecture=MSIL"> <SpecificVersion>True</SpecificVersion> <HintPath> </HintPath> </Reference>

Am I missing some vital step in the upgrade?

Help!

Rgds, Peter

You've to redirect the references to the new runtimes of v2.6. If you generate code on top of existing v2.5 code, the assembly references aren't migrated, you've to do that manually.

Otis wrote:

You've to redirect the references to the new runtimes of v2.6. If you generate code on top of existing v2.5 code, the assembly references aren't migrated, you've to do that manually.

I tried with a new project, based on Northwind, using adaptor. Still getting the references pointing to 2.5 libraries in the generated projects. Having thought about it the problem is obvious. Please check

vsnet2005CFPPCDBSpecificProjectFileAdapter.template

and

vsnet2005CFPPCProjectFile.template

...

Also

vsnet2005DBSpecificProjectFileAdapter.template vsnet2005ProjectFile.template

Indeed a bug in the templates. Will fix it a.s.a.p.

Our automated buildtests didn't pick this up because they're build with the references specified with the compiler, so the vs.net file is bypassed. All project templates suffer this.

Otis wrote:

Indeed a bug in the templates. Will fix it a.s.a.p.

Our automated buildtests didn't pick this up because they're build with the references specified with the compiler, so the vs.net file is bypassed. All project templates suffer this.

No problem. Could you email me when it's all done so I can update?

Rgds, Peter

PeterJ wrote:

Otis wrote:

Indeed a bug in the templates. Will fix it a.s.a.p.

Our automated buildtests didn't pick this up because they're build with the references specified with the compiler, so the vs.net file is bypassed. All project templates suffer this.

No problem. Could you email me when it's all done so I can update?

Rgds, Peter

The templates package in the customer area -> v2.6 has been updated now, so you can just download that and unpack it on top of the installed v2.6 installation. Thanks for reporting this.