Deploy dependent projects in workspace
Important
This content is archived and is not being updated. For the latest documentation, go to What's new and planned for Dynamics 365 Business Central. For the latest release plans, go to Dynamics 365 and Microsoft Power Platform release plans.
| Enabled for | Public preview | General availability |
|---|---|---|
| Admins, makers, marketers, or analysts, automatically | 
Apr 1, 2022 |
Apr 1, 2022 |
Business value
When working with AL workspaces and projects in Visual Studio Code, it's common to open the workspace and deploy a given project. Currently, however, if the NST server doesn't have all the extensions that the project depends on, they must be manually traversed and installed, because dependency publishing only works if there's a baseline to calculate from. To optimize the experience and remove unnecessary manual work, a new deployment command can be used to deploy required projects in the workspace.
Feature details
To optimize the experience and remove unnecessary manual work, a new command will be available to traverse a project dependency graph in the workspace and install any required projects if these aren't already deployed to the NST server. Note that this will only handle project and app references covered by the workspace. If the deployed AL project has dependencies to apps that aren't included in the workspace, these will still have to be present or manually deployed in advance.