Apex Development Options

Salesforce provides multiple ways to write Apex.

Developer Console

Browser-based IDE inside Salesforce.

Use it for:
● Quick edits
● Small experiments
● Log inspection

Limitations:
● No Git integration
● Limited autocomplete
● Not suitable for large projects

Visual Studio Code + Salesforce CLI (Recommended)

This is the industry standard setup.

Benefits:
● Full IDE experience
● Git version control
● Extensions and linting
● Project structure
● Faster deployment
● Team collaboration

This is what we’ll use.

Prerequisites

Before starting, make sure you have:

● A Salesforce Developer Org or Sandbox
● Stable internet connection
● Admin access to your org

Step 1 – Install Required Software

Install the following tools:

● Visual Studio Code

Download and install VS Code from the official site.

● Salesforce CLI

Install Salesforce CLI to authenticate and deploy code

Verify installation

sf --version

● Salesforce Extensions Pack for VS Code

Install from VS Code Extensions marketplace.

This provides:
● Apex syntax support
● Org authentication
● Deployment commands
● Code completion

Step 2 – Authorize Salesforce Org

You can connect your Salesforce org in two ways:
● Using Terminal (CLI)

● Using VS Code Command Palette

Both methods do the same thing internally.

Method 1 – Using Terminal (CLI)

Open the VS Code terminal and run:

sf org login web

This opens a browser window for login.

After successful login:
● Org is connected
● Authentication token is stored locally

Verify connected orgs:

sf org list

Method 2 – Using VS Code Command Palette (Recommended for Beginners)

1. Open the VS Code

2. Press:

Ctrl + Shift + P   (Windows / Linux)
Cmd + Shift + P    (Mac)

3. Type:

SFDX: Authorize an Org

4. Select the command.

5. Choose Web Login when prompted.

6. Browser window opens → Login to Salesforce.

7. After successful login, return to VS Code.

You will see a success message in VS Code once the org is connected.

Verify Org Connection

1. Open Command Palette again.

2. Type:

SFDX: Display Org Details

This shows the authenticated org information.

Step 3 – Create a Salesforce Project

A Salesforce project is a local folder structure where your source code lives and syncs with your org.

You can create a project in two ways:
● Using VS Code Command Palette
● Using Terminal (CLI)

Method 1 – Using VS Code Command Palette (Recommended)

1. Open the VS Code

2. Press:

Ctrl + Shift + P   (Windows / Linux)
Cmd + Shift + P    (Mac)

3. Type:

SFDX: Create Project

4. Select:

Standard Project

5. Enter project name:

apex-demo

6. Choose the folder location.

VS Code will automatically generate the project structure.

Method 2 – Using Terminal (CLI)

If you prefer terminal:

sf project generate --name apex-demo
cd apex-demo

Project Structure Overview

After creation, your project will look like this:

apex-demo
 └─ force-app
     └─ main
         └─ default
             ├─ classes
             ├─ triggers
             ├─ lwc
             └─ objects

Important folders:

● classes → Apex classes
● triggers → Apex triggers
● lwc → Lightning Web Components
● objects → Custom object metadata

This structure keeps metadata organized and deployable.

Step 4 – Create Your First Apex Class

An Apex class is where you write server-side business logic in Salesforce.
Each class is stored as metadata and deployed to your org.

You can create an Apex class in two ways:
● Using VS Code Command Palette (Recommended)
● Using Terminal (CLI)

1. Open Command Palette.

2. Type:

SFDX: Create Apex Class

4. Select the Command.

5. Enter Class Name:

HelloApex

6. Select the default directory when prompted.

VS Code automatically creates two files

HelloApex.cls
HelloApex.cls-meta.xml

Inside:

force-app
 └─ main
     └─ default
         └─ classes
             ├─ HelloApex.cls
             └─ HelloApex.cls-meta.xml

Meaning of files:

● .cls → Your Apex source code
● .cls-meta.xml → Metadata configuration (API version, visibility)

Do not delete the meta file — Salesforce requires it.

Open HelloApex Class and Copy Paste This:

public class HelloApex {

    public static String sayHello() {
        return 'Hello from Apex!';
    }

}

Save.

Step 5 – Deploy to Salesforce Org

Deployment means sending your local source code from VS Code into your Salesforce org so it becomes active and usable.

You can deploy in two ways:
● Using VS Code Command Palette
● Using Terminal (CLI)

Method 1 – Using Command Palette

1. In the Explorer panel, right-click the file or folder you want to deploy:

force-app

2. Click

SFDX: Deploy Source to Org

VS Code will start deployment in the background.

Deployment Status

You will see:
● Progress message in VS Code status bar
● Output in the Terminal panel
● Success or error notification popup

When deployment succeeds:
● Apex class appears in Salesforce Setup
● Metadata is synchronized
● Code becomes executable

Method 2 – Using Terminal (CLI)

Open terminal in your project folder and run:

sf project deploy start

This deploys all changed metadata to the connected org.

Step 6 – Run Apex Code

Once deployed, you can execute Apex code using Execute Anonymous Window in Developer Console.

This is mainly used for:
● Testing logic
● Running quick scripts
● Debugging

Open Developer Console

1. Login to Salesforce.

2. Click ⚙️ Gear Icon → Developer Console.

3. Developer Console opens in a new window.

Execute Anonymous Apex

1. In Developer Console, click:

Debug → Open Execute Anonymous Window

2. Enter the following code:

System.debug(HelloApex.sayHello());

3. Select Open Log.

4. Click Execute.

Now you see the log entry.

Search for:

Hello from Apex!

Or Click Debug Only button.

You should see your output in the log.

This confirms:
● Code deployed correctly
● Apex method executed successfully

Common Setup Mistakes

Avoid these issues:

● Not installing Salesforce Extensions
● Using old sfdx commands instead of sf
● Forgetting to authorize org
● Editing code directly in org and locally simultaneously
● Skipping Git version control

Conclusion

A strong development environment is the foundation of productive Apex development.

You now have:
● VS Code configured
● Salesforce CLI connected
● A working project
● Your first Apex class deployed

Happy Learning!

Apex Beginner to Advance

Apex Development Environment Setup