I’m undecided

Business Logic implementation practices on COT??

I would like to know what is the best practice regarding writing business logic in COT. I'm recreating a LOB application that it was written initially using Entity Framework & T-SQL Stored Procedures. Actually, I want to learn how I could write business logic regarding either every field of a record or the record itself. In the entity framework things are pretty clear - for every field (Property) you have two available events (Changing , Changed) in order to write required logic..Is there an equivalent approach in COT or I should put all the logic in the before Insert/Update/Delete actions in the controller? Is there a template application that may be helpful?

1 person has
this question