As an ISV or Salesforce partner, you can package and distribute applications and components to other Salesforce users and organizations, including those outside your company.
Publish applications and components to and install them from AppExchange.
A managed package ensures that your application and other resources are fully upgradeable. To create and work with managed packages, you must register a namespace prefix. A managed package includes your namespace prefix in the component names and prevents naming conflicts in an installer’s organization. After a managed package is released, the application or component names are locked, but the package developer can still edit these attributes.
API Version
Description
Label
Language
Markup
Apex Class Considerations for Packages
Keep these considerations in mind when you develop Apex classes for packages.
Adding Aura Components to Managed Packages
Add an Aura component to a managed package from a package detail page in Setup.
Deleting Aura Components from Managed Packages
After you’ve released a managed package, you may decide to refactor the package and delete an Aura component. It’s your responsibility to educate your customers about the potential impact from any components you delete. In the Release Notes for your upgraded package, list all custom components you’ve deleted and notify customers of any necessary actions.
See Also
j
