Upgrade from 4.1 to 5.2

Posts   
 
    
Elroy
User
Posts: 2
Joined: 01-Aug-2017
# Posted on: 01-Aug-2017 23:57:48   

I install the upgrade and the new licenses. I regenerated the entities and updated all of the references to libraries to 5.2. All went fine, but I can build. I get 2 errors from generated code. I am using VS 2017. I have the projects and the generated code targeting .NET 4.6.2. I have attached a screenshot of the errors.

Please advise, since I can not move forward. I will revert back to 4.1 for the time being.

Thanks.

Attachments
Filename File size Added on Approval
LLBGen pro error 080117.png 9,832 01-Aug-2017 23:58.02 Approved
daelmo avatar
daelmo
Support Team
Posts: 8245
Joined: 28-Nov-2005
# Posted on: 02-Aug-2017 07:59:36   

Hi Elroy,

Please confirm what LLBGen Pro Designer build version are you using. Also confirm the runtime library version that you are referencing on the generated code. Ref: http://www.llblgen.com/TinyForum/Messages.aspx?ThreadID=7717

It looks like you generated code with one version and referenced other runtime library version.

David Elizondo | LLBLGen Support Team
Otis avatar
Otis
LLBLGen Pro Team
Posts: 39614
Joined: 17-Aug-2003
# Posted on: 02-Aug-2017 09:41:55   

yes looks like it. Also make sure the files you generated on top of the old code indeed overwrote all files. This is easy to check in the generation log in the designer shown after code generation

Frans Bouma | Lead developer LLBLGen Pro
Elroy
User
Posts: 2
Joined: 01-Aug-2017
# Posted on: 02-Aug-2017 15:34:11   

Thanks for the prompt response. I had found the problem before I had a chance to read your responses.

My fault. There was an old project that was writing the new code in the wrong place.

Sorry for the trouble.

You might want to consider doing what DevX does on updates. Have a converter that changes all the references in all the projects to the new release. That saves a lot of time.

Thanks again for the help.

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39614
Joined: 17-Aug-2003
# Posted on: 03-Aug-2017 09:58:45   

True, though if you use nuget for the references, it will be easy as well simple_smile v4.1 wasn't on nuget so you had to reference the runtimes from a folder, but they're nowadays also on nuget which makes managing the runtime references much easier (in vs, right-click solution -> manage nuget packages -> update)

Frans Bouma | Lead developer LLBLGen Pro