Can you have two managed packages in one Dev Org?
If not, what are my options and do I have to pay Salesforce to increase the limit? You cannot create two managed packages in one dev org, you can only have one namespace created per DE org. Your options are to create another DE org and install the first managed package in there.
Can a packaging Org own only one managed package?
We recommend that you enable Dev Hub in your Partner Business Org (PBO). A packaging org can own only one managed package. A Dev Hub can own one or more packages. The namespace of a managed package is created in a namespace org and linked to the Dev Hub. See Namespaces for more details.
What does managed package mean in Salesforce World?
In the Salesforce world, a managed package is a set of components that have been developed together in one org (called the packaging org) and can be installed together into other orgs (called subscriber orgs). Releasing this project as a managed package can take a bit more work, but has several benefits:
How to create a second generation managed package?
You can create and install a second-generation managed package directly from the command line. You include an entry in the sfdx-project.json file for each package to specify its alias, version details, dependencies, features, and org settings.
Can you delete a managed release package in apex?
Yes, if you can get it uninstalled from all subscriber orgs (including any sandboxes, etc), you can delete the package entirely. I’ve personally done this in one of my developer orgs a while ago.
Can you delete a managed release package if it is not installed in any subscriber Org?
Can you delete a managed release package if it is not installed in any subscriber org? Yes, if you can get it uninstalled from all subscriber orgs (including any sandboxes, etc), you can delete the package entirely. I’ve personally done this in one of my developer orgs a while ago.
How to delete a package in Salesforce DX?
Use the force:package:version:delete and force:package:delete commands to delete packages and package versions that you no longer need. To delete a package or package version, users need the Delete Second-Generation Packages user permission. Before you delete a package, first delete all associated package versions.