'EntityCollection' could not be set on property 'DataContainerType

Posts   
 
    
like2175
User
Posts: 83
Joined: 27-Mar-2006
# Posted on: 04-Nov-2008 11:32:40   

My page still runs, but now, since restarting my project and not knowingly changing anything, when viewing the design of the page all of the LLBLGenProDataSource controls (self-serv) show:

"Error Creating Control - {control_name} 'EntityCollection could not be set on property 'DataContainerType'.

I've added a new dsOffice and this works fine: I can't bind any new controls to the "broken" LLBLGenProDataSources

You can see from this extract that the markup is identical for the "broken" dsNotificationType and the working dsOffice:

Can I do anything to "fix" the broken LLBLGenProDataSource controls?


<llblgenpro:LLBLGenProDataSource ID="dsNotificationType" runat="server" DataContainerType="EntityCollection"
      EntityCollectionTypeName="Fluor.Tlc.DAL.CollectionClasses.NotificationTypeCollection, Fluor.Tlc.DAL">
    </llblgenpro:LLBLGenProDataSource>
    <llblgenpro:LLBLGenProDataSource ID="dsOffice" runat="server" DataContainerType="EntityCollection"
      EntityCollectionTypeName="Fluor.Tlc.DAL.CollectionClasses.OfficeCollection, Fluor.Tlc.DAL">
    </llblgenpro:LLBLGenProDataSource>

Vs2008 v2.5 targetting oracle 9 ODP

Walaa avatar
Walaa
Support Team
Posts: 14950
Joined: 21-Aug-2005
# Posted on: 04-Nov-2008 11:42:36   

Which LLBLGen Pro runtime library version are you using?

like2175
User
Posts: 83
Joined: 27-Mar-2006
# Posted on: 04-Nov-2008 11:57:30   

SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll reports fileversion: 2.5.08.0328 assembly version: 2.5.0.0

Within my project the .dll reports Runtime Version v.2.0.50727

Is this what you need?

like2175
User
Posts: 83
Joined: 27-Mar-2006
# Posted on: 04-Nov-2008 12:11:07   

Just noticed... flushed

I have 2 projects in my solution.. The DAL and "the rest!" I was referencing 2 different version of the runtime library v2 and v2.5 in each of the 2 projects. Changing them to both reference v2.5 and closing and reopening my vs poject has fixed the issue.

Thanks for your help.

Graham