New Post: Execute other functions -- lifecycle

The magic word here is the FunctionContextContainer. Its not documented anywhere, but if you dig around in the source, you'll find some interesting things.

The basic idea is that you wrap your whole page-content inside your own function which allows you to add items to the container, which is then passed to all your child functions, which can then at any point retrieve items from the container.

Look at it as a HttpContext Items Collection, just within the context of C1 Functions.

I'm using it extensively myself, which you can see examples of here

• this is a wrapper-function around the FormBuilder which allows child-functions to evaluate which form they are being executed within
  
• this allows for functions added to a MailTemplate to access the Form-instance which was submitted and triggered the email to be sent - here is an example of a function that retrieves the instance form the container
  

Ps. If you use the Html.C1().Function(...) way to execute functions inside razor files, then make sure to always use the Html.C1().Function(..., FunctionContextContainer) overload, otherwise you'll find that your context is being cleard. I've reported it as an issue here https://github.com/Orckestra/C1-CMS/issues/191