Major Exo Checkin Tonight
Jamie Thomas
All,
I am *finally* planning to check in my changes to the Exo codebase this evening that have been cooking for the past three months. At this point a number of projects, including Enrich, have been updated to reflect these changes and appear to be working correctly. However, in order to effectively introduce these changes I need to check them in and work with each of you to ensure existing projects and code is not adversely affected.
If you have any projects with extensive ExoWeb client code pending deployment in the next day or so, please let me know by 9:00 this evening. Having said this, the goal was to simplify client development without introducing significant breaking changes. If you client code is simple and correctly written it should just work. If the code has flaws, does not load data correctly, or uses some complex Exo code (including use of _variables), it will not. However, in working with the Enrich team on this, almost all changes made to the codebase to address breaks resulted in fixing underlying problems and simplifying complex code.
Once I have worked with all of you to absorb the initial impact of this check-in, I will be communicating via the Exo Google group the changes and how you should begin to take advantage of them in your future development work. In the meantime, if you are in the process of writing any Exo server or client rules, please check with me first so I can give you a quick primer.
Thanks,
Jamie
Jamie Thomas
All,
These changes are now checked in (hopefully everything). This includes both Exo for VC3 and Exo for EF implementations and all unit test projects. Please get with me in the morning if you are encountering any issues relating to this checkin. Thanks Bryan for your support getting this completed!
Thanks,
Jamie