Force.com IDE Developer Guide

Get Started with the Force.com IDE
Develop with the Force.com IDE
Test Code with the Force.com IDE
Deploy Code with the Force.com IDE
Get Started with the Apex Debugger
Get Started with the Apex Debugger
Set Up the Apex Debugger
Explore a Simple Debugging Puzzle
Manage Debugging Sessions
Apex Debugger Limits and Considerations
Apex Debugger Troubleshooting
Get Started with the ISV Customer Debugger
Set Up the Apex Debugger
Set Up a Debugging Session
Debug Your Project
Renew a Debugging Session
Delete Your Copy of Your Customer's Code
ISV Customer Debugger Limits and Considerations
Solutions to Common Force.com IDE Problems
Force.com IDE Release Notes
Useful References
PDF

Get Started with the ISV Customer Debugger

The ISV debugging capability covers a gap in what you can do with the Apex Debugger. As an ISV, you can debug your own code. As a subscriber, you can debug your own code. However, because of the protections against seeing managed code, subscribers can’t debug ISV code in their orgs.

Force.com IDE is in a maintenance-only state. We still provide support for the product through our official channels, but updates prior to October 12, 2019 will be only for critical security issues that arise. On October 12, 2019, we will no longer provide support or updates of any kind for Force.com IDE. On that date, we will also begin archiving documentation and removing download links for the product. We recommend that you start migrating to Salesforce Extensions for Visual Studio Code or one of the great tools made by our partners. For more information, see The Future of Salesforce IDEs on the Salesforce Developers Blog.

Warning

With the ISV Customer Debugger, an ISV can work with a subscriber to debug issues specific to the subscriber’s org. An ISV can reproduce issues in the specific environment, so problems can be diagnosed more quickly, facilitating faster fixes for the ISV’s software offering. You can debug only sandbox orgs.