CommandBase Stopped Working When Moving From CSLA 3.7 to CSLA 4.1

grj posted on Thursday, October 13, 2011

We use a few CommandBase derived objects in our project. We create them using reflection. When we upgraded our project from csla 3.7 to csla 4.1 they quit working.

When I step through the code the data table used to store retrieved rows gets populated as expected. But when I use the datatable through a property on the command object the rows are no longer there. The columns still exist but not the rows.

Thanks,

grj

vschaak replied on Friday, October 14, 2011

Hi grj,

I don't know, whether it exactly fits your problem, but once I encountered a prob very similar:

If you use:
var cmd = new ExistsCommand(id);
DataPortal.Execute<ExistsCommand>(cmd);
return cmd.ProjectExists;

In this case you'll miss all data retrieved or generated by your execute method, although your cmd-object has all that is generated by its constructor (the id property for example).

Using this, the world is just fine ;-):
var cmd = new ExistsCommand(id);
cmd = DataPortal.Execute<ExistsCommand>(cmd);
return cmd.ProjectExists;

Does this help?

Regards

Volker