Code generation for property EntityFactoryToUse failed

Posts   
 
    
Posts: 1268
Joined: 10-Mar-2006
# Posted on: 02-Nov-2006 08:00:14   

I am using Developers Express XtraReports. Otis, you have helped me out with a few template modifications to make everything work with these and for the most part it seems to work nicely.

However, I am getting a weird error popup in the VS2005 designer. I click OK and go about my business, so not sure what damage it actually does.

Code generation for property 'EntityFactoryToUse' failed. Error was: ''EntityFactoryConverter' is unable to convert 'FULLNAMESPACE.MainReportEntityFactory' to 'System.ComponentModel.Design.Serialization.InstanceDescriptor'

It appears to be some sort of Visual Studio version errors. I saw some stuff in Google about having a 'copylocal' assembly on an assembly that is in the GAC. However, this is the DAL so that is not in the GAC.

It might have something to do with rebuilding the DAL with changes, then messing with the report, etc. If I rebuild - close VS, go back in, edit the report, I dont get it. Might be sort of the same problem we have when trying to use LLBLGenProDataSourcex controls after adding an entity to the DAL.

Just wanted to see if you guys have seen this or have any comments/feedback.

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39927
Joined: 17-Aug-2003
# Posted on: 02-Nov-2006 08:30:38   

I've never seen this before. It looks like an error that shows up when an EntityCollection is on a form or other designer canvas so the EntityFactoryToUse property has to be serialized into the designer code, does that describe your situation?

Frans Bouma | Lead developer LLBLGen Pro
Posts: 1268
Joined: 10-Mar-2006
# Posted on: 02-Nov-2006 16:45:52   

Yes, I have dropped the collection off the toolbar onto the report form.

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39927
Joined: 17-Aug-2003
# Posted on: 02-Nov-2006 18:06:12   

Apparently the report designer can't serialize the proper type, and indeed I think it's related to the datasourcecontrol stuff, where vs.net has different references to ormsupportclasses dlls (e.g. the generated code one, the one of the toolbox item etc.) and makes mistakes...

Frans Bouma | Lead developer LLBLGen Pro