Force.com IDE Developer Guide
Winter '23 (API version 56.0)
Summer '22 (API version 55.0)
Spring '22 (API version 54.0)
Winter '22 (API version 53.0)
Summer '21 (API version 52.0)
Spring '21 (API version 51.0)
Winter '21 (API version 50.0)
Summer '20 (API version 49.0)
Spring '20 (API version 48.0)
Winter '20 (API version 47.0)
Summer '19 (API version 46.0)
Spring '19 (API version 45.0)
Winter '19 (API version 44.0)
Summer '18 (API version 43.0)
Spring '18 (API version 42.0)
Winter '18 (API version 41.0)
Summer '17 (API version 40.0)
Spring '17 (API version 39.0)
Winter '17 (API version 38.0)
Summer '16 (API version 37.0)
Spring '16 (API version 36.0)
Winter '16 (API version 35.0)
Get Started with the Apex Debugger
Create Sample Accounts in Your Org
Create an Apex Class
Create a Visualforce Page
Identify a Problem
Debug the Problem
Fix the Problem
Delete Your Sample Accounts
Manage Debugging Sessions
Solutions to Common Force.com IDE Problems
Force.com IDE Release Notes
Explore a Simple Debugging Puzzle
Once you’ve gotten the Apex Debugger up and running, work through this exercise to
explore some of the Debugger’s capabilities.
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
-
Create Sample Accounts in Your Org
To complete this exercise, add the following sample data in your org. -
Create an Apex Class
Next, let’s create an Apex class to debug. This class removes cold accounts from a list so that you can focus on more promising clients. -
Create a Visualforce Page
Now we need a Visualforce page to bring the AccountViewer controller to life. -
Identify a Problem
Because we never write buggy code, our Visualforce page should be working perfectly! Let’s make sure. -
Debug the Problem
Let’s use the Apex Debugger to see what went wrong. -
Fix the Problem
By now you’ve discovered how to fix the problem in AccountViewerController.cls. But you can’t save changes to code while a debugging session is in process. Terminate the debugging session, and then fix the code. -
Delete Your Sample Accounts
Unless you want to keep your sample accounts so that you can play with them in the future, run this code to delete them.