CSLA .NET

Greetings:

Strange issue when trying to save a BusinessBase object after editing.  When I change something in the object and click 'Ok' (go through the save process), I get this error:

Csla.Validation.ValidationException: Object is still being edited and can not be saved

The only thing I have done is migrate to 3.6.0 from 3.0.1.  Is there some upgrade process that I need to go through?  Or a list of breaking changes that I need to consider or something else?

Thanks,

Kelly.

Did you unbind the object from your binding source per the standard pattern before saving it? (It may be that a fix to CSLA is exposing a problem with the way you are doing this than a breaking change per se)

Not sure I follow you.  I have coded the application to operate similar to the ProjectTracker demo app and everything has been working for a year or more.  I do not need the WPF or WCF stuff; so I may just switch back to the 3.0.1 version unless there is something that I am missing in this new version that I can change rather quickly.  I just don't want to go through 30 or 40 WinForms to make changes to a process that has been working with previous editions.

But, if that is the issue, and I need to utilize some of the new stuff, I guess I will have no other alternative.

Thanks for input,

Kelly.

The issue has to do with the warning Rocky posted over a year ago and then implemented in the latest version. The old incorrect behavior is now switched to the new behavior and is exposing bugs in your code. Your code "used to work" because you didn't realize there were bugs in it and Csla didn't point them out for you. Now it does.

The book mentions it on page 214 and this forum has discussed it many times.

Here is one thread that discusses CslaAutoCloneOnUpdate.
http://forums.lhotka.net/forums/thread/20938.aspx

Joe