services-extension-consumption

To consume the salesforcedx-vscode-services API, install and reference the package in your VS Code extension, load the ExtensionProviderService, and build a services layer to register commands and access core services like Channel, Workspace, and Connection.

When building a Salesforce DX extension with salesforcedx-vscode-services, you can access ChannelService, MediaService, WorkspaceService, ConnectionService, ProjectService, SettingsService, FsService, and EditorService to manage org connections, project resolution, and file watchers.

You register commands in a VS Code extension by loading the ExtensionProviderService, building a pre-loaded services layer, and then using that layer for command activation and observability within your Salesforce DX development workflow.

Yes, salesforcedx-vscode-services supports file and configuration watchers. You can leverage the services layer to monitor changes and manage dev workflows, project resolution, and org connections within your VS Code extension.

You need to load the ExtensionProviderService when building a new VS Code extension that depends on salesforcedx-vscode-services to manage org connections, project resolution, and file watchers for development workflows.

The best way to manage org connections and project resolution is by consuming the salesforcedx-vscode-services API, loading the ExtensionProviderService, and utilizing the ConnectionService and ProjectService within your extension's services layer.