I'm using the latest version of LLBLGenPro - 2.5, built Aug 28. Doing an UpdateMulti like this
LPTEventEntity e = new LPTEventEntity ();
e.Volume = 0;
IRelationCollection relations = new RelationCollection ();
relations.Add (LPTEventEntity.Relations.LPTAreaEntityUsingAreaId);
new LPTEventCollection ().UpdateMulti (e, (LPTEventFields.Date == date) & (LPTAreaFields.HotelID == hotelId), relations);
Throws a NullReference exception from DaoBase.UpdateMulti(IEntity entityWithNewValues, ITransaction containingTransaction, IPredicate updateFilter, IRelationCollection relations). We build LLBLGen from source, so I've already found the bug:
IRelationCollection relationsToUse = null;
if(typeOfHierarchy == InheritanceHierarchyType.TargetPerEntity)
{
IInheritanceInfo info = ((EntityBase)entityWithNewValues).GetInheritanceInfo();
relationsToUse = new RelationCollection();
relationsToUse.AddRange(info.RelationsToHierarchyRoot);
}
if(relations != null)
{
relationsToUse.AddRange((RelationCollection)relations);
}
'relationsToUse' is never set.
I've fixed it for us; this is an FYI.