Metadata Coverage
Limitations for Salesforce DX
Previous PDF Versions
When you finish writing your code, the next step is to deploy it. We offer different deployment options based on your role and needs as a customer, system integrator, or independent software vendor (ISV) partner.
To learn about the benefits of the different development models, review these Trailhead modules:
You have several tooling options, based on how you decide to build and release yours apps.
Second-Generation Managed Packages
If you’re an ISV that develops apps and lists them on AppExchange, Salesforce recommends managed packages.
Second-generation managed packaging (managed 2GP) ushers in a new way for AppExchange partners to develop, distribute, and manage their apps and metadata. You can use managed 2GP to organize your source, build small modular packages, integrate with your version control system, and better utilize your custom Apex code. You can execute all packaging operations via Salesforce CLI, or automate them using scripts.
For more information on managed 2GP packages, see the Second-Generation Managed Packaging Developer Guide.
First-Generation Managed Packages
Similar to managed 2GP, managed 1GP packages are used by ISVs to distribute their business apps to customers via AppExchange.
If you’re familiar with first-generation managed packages and want to learn more about how 1GP differs from 2GP, see Comparison of First- and Second-Generation Managed Packages.
For more information on managed 1GP packages, see Create a First-Generation Managed Package using Salesforce DX.
Build and Release Your App with Metadata API
Develop and test your app in your sandboxes. Use Salesforce CLI or Salesforce Extensions for VS Code to retrieve and deploy your source. This development work flow is called the org development model.