Issue migrating from CSLA 2.0 to 3.5

jamorgan posted on Wednesday, December 31, 2008

Hello,

I am looking at moving my application from CSLA 2.0 to 3.5.  I have put the new version into my application and it compiles beautifully, no problems at all, but when I execute my .Save on a BO, I am running into an odd error.

On save of an object, I modify the BOs Last Update Date and Time (of SmartDate type) which is used for concurrency and to show the user when the data was last updated.  The stored procedure used to save the data also returns the new Last Update Date and Time.  In the 2.0 version, this works correctly.  With the new 3.5 in place, the date remains the same as it was before .Save is called.

I am currently walking through the CSLA code to figure out why the data changes are not being propogated back once .Save is complete.  It's like anything that changes during the Save call is not being returned.

Any thoughts on what might be occurring would be greatly appreciated.  Well, back to my debugging.