I am currently reading about Solutions in CRM 2011.
The solutions are a great enhancement to CRM 2011 but they do have quite a few quirks or things to watch out for. I’m sure these will become second nature in the future but at the moment when everything is new, you have to keep you wits about you.
The first thing I have noticed is a solution can be managed and unmanaged. An unmanaged solution is one which you can change and modify. This is basically how you will have the solution whilst you are testing and developing it.
A managed solution is a solution you don’t want anyone to change.
Another thing I was wondering about, what about plugin registration. If you supplied a solution with plugin’s do you need to register the plugins. The answer is yes, although you can include already registered plugins in the solution. This seems a bit misleading to me and I haven’t quite figured out what you do if this was an app in the CRM market place. Would he user have to register the plugin themselves or are we expected to write some code to do this programatically.
Managed solutions also cannot be exported.
Deleting a managed solution will uninstall all of the solutions components.
An interesting aspect of Managed Solutions is you can create properties to allow the user to customermize aspects of the solution.
Solutions can be layered and it matters what order you import solutions into CRM.
Solutions only include the changes which are different from the system. This means you can merge solutions together.
if two solutions both change the same area then the last solution imported will be the winner. Which is something to remember, especially if you want to layer solutions and try and modularise coding in CRM.
it’s interesting and the more I read about it the more the way it works makes sense. but it certainly helps to read the SDK and articles about solutions
Hosk's Dynamic Blog 
3 thoughts on “managed and unmanaged solutions in CRM 2011”