ISVforce Guide

Welcome to the ISVforce Guide
ISVforce Quick Start
Grow Your AppExchange Business
Design and Build Your Solution
Package and Test Your Solution
About Managed Packages
Configure Your Developer Settings
Register a Namespace Prefix
Specifying a License Management Organization
What are Beta Versions of Managed Packages?
Creating and Uploading a Beta Package
Create and Upload a Managed Package
View Package Details
Installing a Package
Uninstalling a Package
Installing Managed Packages Using the API
Resolving Apex Test Failures
Running Apex on Package Install/Upgrade
Running Apex on Package Uninstall
Publishing Extensions to Managed Packages
Pass the AppExchange Security Review
Publish Your Solution on AppExchange
Sell on AppExchange with Checkout
Monitor Performance with Analytics for AppExchange Partners
Manage Orders
Manage Licenses
Manage Features
Provide a Free Trial of Your Solution
Support Your AppExchange Customers
Update Your Solution
Appendices
Glossary
PDF

Newer Version Available

This content describes an older version of this product. View Latest

About Managed Packages

Available in: Salesforce Classic (not available in all orgs) and Lightning Experience
Available in: Developer Edition

Package uploads and installs are available in Group, Professional, Enterprise, Performance, Unlimited, and Developer Editions

Salesforce has two ways that you can build managed packages, first-generation packaging (1GP) and second-generation packaging (2GP). This guide describes 1GP. For new solutions, use 2GP as described in the Second-Generation Managed Packages section of the Salesforce DX Developer Guide.

Note

A managed package is a collection of application components that are posted as a unit on AppExchange, and are associated with a namespace and a License Management Organization.

  • You must use a Developer Edition organization to create and work with a managed package.
  • Managed packages are depicted by the following icons:
    • Beta Managed - Beta
    • Managed - Released Managed - Released
    • Managed - Installed Managed - Installed

To prevent naming conflicts, Salesforce recommends using managed packages for all packages that contain Apex to ensure that all Apex objects contain your namespace prefix. For example, if an Apex class is called MyHelloWorld and your org’s namespace is OneTruCode, the class is referenced as OneTruCode.MyHelloWorld.

Tip