Take a look at the $system.OBJ.Load() and $system.OBJ.LoadDir() methods.  This is the most common way to take source from your source control system and load them into your namespace.  

Yes - if you New $namespace, then once the context pops off the stack it will revert automatically to the original namespace before setting the newed version of $namespace

I want to bump this post up because it is really useful (thanks Evgeny) and people definitely need to be aware of this great resource for getting the example source!

Timur - THANK YOU!  It hadn't gotten annoying enough to google a solution yet, and you just saved me the effort :)

Tim- I saw the same thing and then I realized it was an outlook thing:

 

 

It saws right the top that Outlook removed extra line breaks.  If you click that message you can reverse it and the line breaks will then get corrected.

 

HTH,

Ben

Thanks for the shout-out Paul!

I would like to clarify that subscription emails have been revamped for non-digest emails *only*.  In order to turn off Digest, you need to go to:

My Account > Subscriptions Tab > Expand "Settings" at the bottom and then uncheck "Digest mode"

 

The new email formatting isn't fully where we're like to see it yet (e.g. it is not HTML and it doesn't include full thread history) but I hope that people find that it makes consumption of updates via email significantly more useful than it was previously.  Personally - I can't wait to see this change go live!

To add one more details to what Tim wrote about how we handle internal applications - we have a partnership with our QD department where at least one during every beta release period they will request a copy of each of our apps and verify compilation, automated unit tests and manual unit tests on that beta version of Caché.  This way if there is going to be any sort of breaking change, we know it before we upgrade our dev environment and we can schedule that upgrade more wisely so as not to halt other development work.  This practice is supported by the fact that we run all of our environments on VMs so it is fairly easy for us to get a new VM cloned off for them from Test and then we are not otherwise impacted in our development workflow.  

We have been able to move to new released much more quickly as a result of this practice