13 iunie 2011 16:16
Has anyone done any work on defining best practices for Solution management from a change management perspective? I get the concepts and limitations of managed/unmanaged solutions, but am struggling with coming up with some reusable best practices for how to manage web resources (like html/js/etc), ribbon changes, etc both in source control and for deployment - particularly with a large organization that could have multiple concurrent CRM development teams working with different deployment dates over a long period of time. Obviously compiled code-based artifacts like plugins, silverlight, etc have their source code managed the same as now, outside the 'solution' model...Some of the areas I am going back and forth on include:
1. Versioning individual web resource files, xml files, etc (instead of just a version of a Solution zip file) - this allows better insight into what is changing between versions and better supports the ability to 'roll back' single files.
2. Promoting code between environments - DEV/QA/Integration/Staging/Prod - Managed/Unmanaged? single large solution or many small solutions? Complexity over time with many many 'mini-solutions' vs. risk of accidentally promoting development done on shared objects by other teams.
I have read a ton of information about solutions, but /I/ have not seen any clear best practices regarding the points above. I'm sure I can come up with something that will 'work' but don't want to re-invent the wheel if someone has already made this effort.
Thanks in advance for any guidance
26 iunie 2011 13:40
I have started a discussion to try to get people to add their experiences / best paractices around solution management here http://social.microsoft.com/Forums/en-US/crm/thread/b878da13-c70b-4c9b-86f3-fe4ce52cb038
I've added a few tips of my own but so far no one has responded. Feel free to comment on this so we can 'bump' it from time to time to keep it near the top of the list.
Microsoft Certified Technology Specialist (CRM) GAP Consulting Ltd. Microsoft Community Contributor Award 2011
5 mai 2012 18:01Moderator
Here is an article on best practices around promoting solutions from different environments:
Gonzalo | gonzaloruizcrm.blogspot.com
8 august 2012 23:22
Today we had some interesting discussion on managing the CRM solution when there is multiple developers involved. We have gone through the options mentioned in -http://msdn.microsoft.com/en-us/library/gg328392 and some solution merging videos - http://channel9.msdn.com/posts/Merging-CRM-2011-Solutions . BUT nothing was an ultimate solution for our scenario where multiple devs will be touching same entities and other components.
What we used in our 2011 upgrade was :
> Use VSTF for managing web resources (.js,.html etc) - Worked
> Use VSTF for plugins and any dlls or external components - Worked
> Created UnManaged solutions for seperate features like below - Wated to Improve
- Core Solution - Entities
- Report Solution - All reports
- Ribbon Solution - Main page Ribbon cistomizations (not entity level)
- SiteMap Solution - Sitemap changes
- Workflow Solution - All workflows
Main challenge was devolopers wanted to use core solution same time as it has all the entities.
If you guys are fidning any better process then please post here.
Any feedback on the process we followed also welcome.
7 martie 2013 08:30Please note that some of the best practices do not involve crm 4 migrations. There still will be some errors when using managed solutions and upgrading managed solutions by using the "holding solution" method.