Best practise: using _Changed methods

Home » Lightswitch » Best practise: using _Changed methods

Best practise: using _Changed methods

| Lightswitch | February 11, 2013


Whenever a property in a related entity is read in code, Light Switch fires a change event on the parent, but doesn’t actually change any properties on the parent.


Just put this code at the start of all _Changed methods and you are save. The code after that will only run when the entity has really changed.




About the author

This author has yet to write their bio.

3 Responses to "Best practise: using _Changed methods"

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">

Current day month ye@r *

 Vraag het ons LIVE
Powered by PureChat.com