Hi Abhishek,
It depend on the system as well as architect how he/she wants to ahead in Product. Below points i have accumulated at once based on that you can decide to which way you would like to go..
Managed:
1. A managed solution can be uninstalled after it is imported. All the components (customizations) of that solution are removed by uninstalling the solution.
2. Managed solutions are read only when imported into the target system. This mean that anyone cannot edit or change any of components from managed solution imported.
3. Managed Solution imported in Target system cannot be exported.
4. If multiple managed solutions are installed, the first one installed is below the managed solution installed later. When two managed solutions have conflicting definitions (same customized component), the general rule is “Last one wins”.
Managed solution creates layers of customizations. Managed solutions have the capability to keep track of which customizations belong to which solution. To the end user, only the top layer (latest solution installed) is visible, but under that layer there can be multiple layers of customizations so you can build a solution on top of another solution without mixing up all the changes.
Solution layering also means that you can revert-back to a previous system state. If you uninstall a solution, all its components will be removed but the customizations from other solutions in a lower layer will surface back.
Unmanaged:
1. When you import an unmanaged solution, you add all the components of that solution into your default solution. So after import components can’t be removed by uninstalling the solution.
2. Unmanaged Solution is editable when imported into target system. This mean that anyone can open solution and edit any component included solution.
3. If we delete unmanaged solution from system then changes will remain in system.
4. When you import an unmanaged solution that contains solution components that you have already customized, your customizations will be overwritten by the customizations in the unmanaged solution. You can’t undo this.
As long as solution is unmanaged, it is “open” (editable) and you can add/remove/edit components, update the publisher, the configuration and the managed properties of the solution. You will also be able to update the version of the solution and you will be able to export it. Another typical use of unmanaged solutions is to work as an integration solution to which multiple developers or teams contribute with different components.
ð However, once your solution is ready to go into UAT or production, the solution should be installed as managed because it will no longer need to be editable, this will allow a more rigorous release control because it will force all updates to be made in a development environment and then promoted to UAT/Production as opposed to making direct changes in production environments (a fundamental best practice in IT).
Unmanaged solution should be installed if you want to add all the components to your default solution, and overwrite any existing customizations.
