In yesterday’s video I chatted with a few PMs on the CRM platform team.  We talked at a high level about some of the problems they’re trying to solve as they think about CRM “5.  In today’s video we go a little deeper with Humberto Lezama Guadarrama (Program Manager),  Elliot Lewis (Developer Lead), and Scott Head (Developer) As I mentioned in yesterday’s video, don’t look for any schedule information in here.  Also features and feature names may and probably will change before we ship.  CRM “5” is still a long way away.  We’re talking about this developer-focused stuff early to help developers with design and architecture as they think about future designs. In CRM “4” you create components (entities, forms, reports, etc) and then there are various means to deploy those components into a customer’s implementation.  In this video we go deeper on a new concept in CRM “5” called solutions.  Think of solutions as providing to CRM the same sort of capabilities that Windows has with its capability to add and remove programs and features. The concept is quite powerful as it allows components to be layered on to the base system but also on top of other solutions (i.e. when there are inter-dependencies).  It also provides a way to protect the intellectual property of the components in your solution.  It also includes change management and versioning In a sense ISVs that build on the CRM platform will now have the ability to package up their applications much like you would package up windows applications into MSIs.  Elliot gives a pretty good explanation of the architecture for how this is implemented.  Like any good architect he couldn’t resist a blank white board and jumped up to diagram out the way a solution and components.  He explains in a clear way how solutions layer on top of one another and still provide for versioning, uninstall and rollback. Humberto gives us a lap around the UI for creating publishers (e.g. ISVs) and solutions.  In doing that he gives a qui...