Indeed, the IEntityFieldCore overload eats the IEntityField2 ones. It's a leftover from a looooong lasting design flaw since the first release of adapter (well, not really a flaw, it's just a matter how you look at it
) : instead of making an overload with IEntityField2, I decided to make an overload with IEntityFieldCore, and because IEntityField also implements IEntityFieldCore, I needed persistenceinfo there as well, which was designed in to be able to specify the two at once, however, it was never really needed.
So lessons learned for me: first write testcode to consume what you think is ok, then write the real code
.