Force.com IDE Developer Guide
jWinter '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)
Notable Lightning Components Features in the Force.com IDE
Set Up the Force.com IDE with Lightning Components Support
Roll Out My Domain to Your Org
Create an Apex Controller Class in the Force.com IDE
Create a Lightning Component Bundle in the Force.com IDE
Add an Event Handler in the Force.com IDE
Create a Lightning Application in the Force.com IDE
Customize Your Style Sheet in the Force.com IDE
Wrap Up Your Exploration of Lightning Components in the Force.com IDE
Solutions to Common Force.com IDE Problems
Force.com IDE Release Notes
Explore Lightning Components in the Force.com IDE
Learn how to create a simple Lightning component that renders a list
of contacts from your org. Start by creating an Apex controller class, and then create a
Lightning component and an event handler. Finally, render the list of contacts in the
component.
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
-
Enable My Domain in Your Development Org
For security purposes, Lightning components require you to define a custom Salesforce domain name for your org. Setting up a new domain is simple, but it takes a few minutes before it’s available for use. When you enable My Domain, references and links to Lightning resources are in the format https://yourDomain.lightning.force.com. Use a Developer Edition org for this exercise. -
Roll Out My Domain to Your Org
Did you get your activation email? From the email, click the link to get back to the My Domain wizard. It takes you to Step 3, where you test the links to your subdomain URLs before rolling out the subdomain to your org. Even though you don’t have users to deploy it to in your DE org, you must still roll out My Domain to make your custom Lightning components available in Lightning pages, in the Lightning App Builder, and for standalone apps. -
Create an Apex Controller Class in the Force.com IDE
Create a class to access data from contacts. -
Create a Lightning Component Bundle in the Force.com IDE
A Lightning component is a combination of markup, JavaScript, and CSS. Create a Lightning component bundle that contains these files. -
Add an Event Handler in the Force.com IDE
The event handler calls your myAction function when the handler is initialized and retrieves a list of contacts. -
Create a Lightning Application in the Force.com IDE
Render and preview your contact list in a Lightning application. -
Customize Your Style Sheet in the Force.com IDE
A Lightning component can specify its own cascading style sheet (CSS). The .css file is included when you create a component bundle in the Force.com IDE. -
Wrap Up Your Exploration of Lightning Components in the Force.com IDE
You’ve now learned how to create a Lightning component that renders a list of contacts from your org. You created an Apex controller class, and then added a Lightning component and an event handler. You rendered the list of contacts in the component, both with and without pizazz. What’s next?