Release Notes

For information about enhancements made in weekly releases, see the Salesforce Extensions for VS Code change log.

Winter '19

• Develop Against Any Org in Visual Studio Code (Beta)
  Connect to any org to retrieve and deploy source from Visual Studio Code. Previously, you could use Salesforce Extensions for VS Code only with scratch orgs. Salesforce Extensions for VS Code is the flagship development environment for customizing Salesforce with code. The ability to connect to and develop against any org enables you to start using Visual Studio Code, even if you don’t work exclusively with scratch orgs.
• Debug All Your Orgs for Free with Apex Replay Debugger (Generally Available)
  Apex Replay Debugger simulates a live debugging session using a debug log, which is a recording of all interactions in a transaction. You no longer need to parse through thousands of log lines manually. Instead, Apex Replay Debugger presents the logged information similarly to an interactive debugger, so you can debug your Apex code. With this release, we added checkpoints, which provide more information about your variables than debug logs do.
• Explore Your Apex Tests in Visual Studio Code
  See your test results at a glance, and jump from those results to your test code in Visual Studio Code. When Apex tests fail, you can jump from the test results straight to the line that contains the failed assert statement. When Apex tests succeed and you want to remind yourself what you were testing, you can jump to the method definitions for those tests. You can also see which test methods are in your test classes from the testing sidebar.

Summer '18

• Debug All Your Orgs for Free with Apex Replay Debugger (Beta)
  Apex Replay Debugger simulates a live debugging session using a debug log, which is a recording of all interactions in a transaction. You no longer need to parse through thousands of log lines manually. Instead, Apex Replay Debugger presents the logged information similarly to an interactive debugger, so you can debug your Apex code.
• Debug Subscriber Sandboxes in VS Code
  The ISV Customer Debugger 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. With the ISV Customer Debugger, an ISV can work with a subscriber to debug issues specific to the subscriber’s org.

Spring '18

We now offer code completion for the sObjects in your scratch orgs. We also fine-tuned the Go To Definition feature so that it works from more locations in your source code.

Some notable entries from the change log:

• New command—SFDX: Refresh SObject Definitions (enables code smartness in Apex for sObjects: Read more)
• Add Go To Definition for class and interface usage for inner classes (PR #258)
• Enable Go To Definition for usages of classes and interfaces in class and interface declarations (PR #247)

salesforcedx-vscode-visualforce Extension

A new Visualforce language server provides code completion for the standard Visualforce components in your org. The Visualforce language server understands embedded JavaScript and CSS in your .page and .component files, making it easier for you to work with these languages.

Some notable entries from the change log:

• Code completion for standard Visualforce components (PR #180)
• Support proper formatting with Cmd+/ (macOS) or Ctrl+/ (Linux and Windows) in embedded CSS and JavaScript within Visualforce files (PR #200)

salesforcedx-vscode-apex-debugger Extension

We continue to enhance your experience with the interactive Apex Debugger for scratch orgs.

Some notable entries from the change log:

• Paginate collections in variables view (PR #209)
• Configure exception breakpoints (PR #218)