CodeSmith Community

I have used Nettiers 2.0 and never had this problem. I downloaded the nightly build 12_20_2007, and after generating the code and building it, I got an error in the EntityRelationshipMember.cs. Here it is. The error says : myroot.Web.Data.ILinkedDataSource does not contain a definition for 'Deepload. I temporarily commented out the code where the error appears, but I am hoping that this can be fixed.

Public void Deepload()

{

if ( HasDataSource && EnableDeepLoad)

{

GetLinkedDataSource().Deepload();

}

}

I got a similar error.

I noticed that this occurs if I have the options IncludeManyToMany and IncludeRelations turned off in the CRUD section.

If I turn those on I don't get the error.

I guess without these options the DeepLoad methods aren't generated by the tempate, though the bases classes still require an implementation.

I've had the exact same problem. I looked in the ILinkedDataSource and found an if statement around the Deepload. The includeManytomany and includerelationships have to be true, otherwise the Deepload in the interface is not generated.

In the other places where the Deepload is used the same if statement is used (for example in the customdatasource.cst). In the EntityRelationshipMember.cst this if statement is not present.

Result:
When using a web project you can never turn of manytomany/relationships otherwise your webproject will alway be corrupt.

Only fix is to change the EntityRelationshipMember.cst. Just put this in the file:
<%@ Property Name="IncludeRelations" Type="System.Boolean" Default="True" Category="CRUD Options" Description="If true, the child collection relationships will be generated within your entities, if set to false, these child collections will not be generated, and Deep Load/Save will not be generated." %>
<%@ Property Name="IncludeGetListByFK" Type="System.Boolean" Default="True" Category="CRUD Options" Description="If true get statements will be generated." %>

Search for deepload and set the if statement around all the code where deepload is used:
<% if ( IncludeRelations && IncludeGetListByFK ) { %>
<% } // end if ( IncludeRelations && IncludeGetListByFK ) %>

I have version 2.2.0 by the way. Can this bug be fixed in a stable build?

The problem was solved after we migrated the SQL Server 2000 database to a 2005 database. Everything works fine then. So it's just a bug for SQL Server 2000.