Using the newest 'dependencyPublishingOption (Default)' option takes into account dependencies when publishing changes from within a multi-project workspace.


Flow when e.g. publishing changes to a Base app:

This will uninstall all apps (including External and Indirect dependency) that depend on Base. Any other app that directly depend on Base and are not published in the global scope are unpublished. Base will be uninstalled, unpublished, and then published. Dependend apps will be published, installed and then compiled against the newly published Base.

If all of the above works fine, all apps are available again on the database. However, we often encounter ERRORS during Fast Publish / Publish, resulting in ALL dependend extensions being uninstalled / unpublished.

Doing a publish afterwards of the Base app will not result in all extensions from the previous app being reinstalled / republished. The developer is forced to currently manually reinstall / republish EACH extension.

Request would be to provide better INTEGRATED support from within VSCode to fix these kind of issues, without having to depend on powershell scripts. A 'Full / Force Publish' command to republish/install all workspace extensions (and other dependends) based on the dependency rules would be very usefull. (Even better would be VSCode detecting previous erring publishing attempts and correct dependend extensions during a next publish attempt)

Creating custom powershell script to work around the entire -devendpoint problem is not the advised way.