Note : Deleting an Unmanaged Solutions will delete the Solution but will not delete the components.
Note : Deleting an Managed Solution will delete the Solution and Components both (except the Components that are the part of another solution including Default(System) solution )
Export/Import Solutions
For Export : Only Unmanaged Solution can be Exported
For Import : You can import the solution as Managed or as Unmanaged
When an unmanaged Solution is imported, the customizations it contains
overwrite any customizations already in place. This applies only to customizations explicably present in the Solution.
EXAMPLE: Joe exports his Vacation Solution, which contains a custom entity,
as unmanaged. He then adds a field to the entity named Special to store a bit value. He adds the field to the form for the entity as a check box. The form is used so that data in the Special field is accumulated for some records. Joe then imports
his Solution from the file he exported. When he publishes the changes and looks at the form, he finds his Special field disappeared. However, the field is still available to add to the form.
In the preceding example, the customization placing the field on the form is
overwritten by the import. However the field (and the data in it) is left intact since it is not explicitly referenced.
If an import contains changes that conflict with existing data, it will fail.
EXAMPLE: Connie exports a Solution as unmanaged containing a Customer
Interest entity. The entity contains a field called Interest Time of data type Integer. After the export, Pete deletes the Interest Time field from the entity. Connie recreates the field but, although she specifies the same name, she makes
the new field Date and Time. If Connie tries to import the Solution she exported earlier, the import will fail. The Import Summary screen will show that the failure occurred in the Customer Interest component.
In the preceding example,Connie can downloaded the log file to see the error.
HHH
