Puzzling problems after upgrading 2.6 - 5.3

Posts   
 
    
PgFunn
User
Posts: 1
Joined: 08-Dec-2017
# Posted on: 08-Dec-2017 10:16:09   

LLBLGen version: 5.3 (5.3.1) RTM Build date: 03-nov-2017

Putting this in "General", as I'm not sure where else it belongs:

I'm in the process of converting an old solution from referencing an LLBLGen project generated with v2.6, to referencing a new project generated with v5.3.

After substuting a reference to the new LLBLGen project for the old project, I've experienced some puzzling problems with the existing Visual Basic code.

(The new LLBLgen project is generated for .Net 4.5)

*** The method GetMultiManyToManyUsing...CollectionVia... is no longer available? * The method CancelEdit is no longer available for entities?**

I've not found anything specific regarding this - What am I missing, here? Is there any project config missing?

Currently, I'm forced to use clumsy rewrites instead of these methods.

Any ideas what's going on?

Walaa avatar
Walaa
Support Team
Posts: 14946
Joined: 21-Aug-2005
# Posted on: 08-Dec-2017 12:57:54   

In general, break changes can be found in the migrating your code section of the docs.

As for CancelEdit, please check this thread: http://www.llblgen.com/TinyForum/Messages.aspx?ThreadID=22006

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39588
Joined: 17-Aug-2003
# Posted on: 08-Dec-2017 17:39:50   

The GetMultiManyToMany... methods should still be there on the selfservicing collection classes. Could you check if they're generated at all? Did you pick selfservicing for code generation in v5? Also, the names are constructed using patterns, which are available in the project settings. Could you check whether these patterns are matching what you want to use? (Conventions -> General -> Entity Model -> Element Name Construction -> General). These patterns are used to construct the navigator names, which are then used to build the GetMultiManyToMany... method calls.

If you just converted from v2.6 to v5.3 however, it should just work out of the box. I think it might be you picked adapter and not selfservicing when generating code, but don't know for sure.

Frans Bouma | Lead developer LLBLGen Pro