Nathan Totten edited this page Jan 14, 2019 · 57 revisions

Salesforce Extensions for VS Code Roadmap

Our aim with the Salesforce Extensions for Visual Studio Code is to quickly respond to feedback and release new features often. We want to be as transparent as possible with our priorities and our roadmap. This document will constantly evolve to reflect a best effort one year roadmap.

NOTICE: The information presented here is subject to change. Forward Looking Statement


  • Developer Happiness - Our top priority is to make Salesforce Developers happy. This means building tools they want to use, not just something they have to use. This means we release quickly, respond to feedback, and keep the quality of our releases high. It also means focusing on the details.
  • Premier Salesforce Developer Experience - The Salesforce Extensions for VS Code will deliver a powerful and productive developer experience. We will include the best features developers have come to love from previous tools such as the IDE while building new experiences that modern developers have come to expect.
  • Ecosystem - Being a Salesforce developer doesn't mean you have to use a single toolset. We realize that our developers are diverse and have different preferences on tooling. As such, our team aims to support a rich third-party ecosystem. We do this primarily by building tools that use open standards such as the Language Server Protocol and the Debug Adapter Protocol which allow developers to leverage the same code and investments we have made to VS Code in their own tools. We believe that if our partners are no longer required to write the fundamentals they will be free to write more value-add features.

How We Do Planning

At Salesforce, our planning revolves around the three release per year cycle of the core Salesforce service. As such this is how we do planning for the Salesforce Extensions for Visual Studio Code. However, as we release every week we do maintain flexibility as we want to be agile and leave room to respond to opportunities or customer feedback quickly. So this page will describe our release planning in terms of our three yearly releases, but the exact delivery dates of each individual feature would be in one of the weekly releases in that time period. The exception to this is for features in VS Code that depend on changes in the Salesforce Org - i.e. they depend on a specific API version. When this is the case we will typically release the feature behind a flag for use against preview orgs, but wait to make the feature available by default until the date at which the API version is publically available in all orgs.

Release Schedule

In the roadmap below some of the features will be marked with the release to indicate the approximate timeframe they will be delivered.

Release Name API Version Release Date
Spring '19 45.0 2019-02-08
Summer '19 46.0 2019-06-14
Winter '20 47.0 2019-10-12

Legend of annotations:

Mark Description
open box work not started - scheduled
check mark work completed
:rocket: on-going work
:muscle: stretch goal - unclear timeline
:octocat: community contributed





Test & Debug


You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.