Erik Ernst Dynamics User Group Dynamics 365/NAV specialist

Working with extensions which have dependency on other extensions is currently not very easy. For example if we have a "main app" and a "test app", then in order to republish our main app, then we first have to unpublish the test app. Not only is there no way to do this from VSCode (except than writing a Powershell script and run it), but really slows down the test - development cycle when doing test driven development. My hope is that that the AL extension would be able to handle this automatically. With the option that it also re-publishes any unpublished extensions, so that it would be possible to quickly rerun the test that failed before.

With a requirement to have automated tests in a separate (dependent) test extension for AppSource extensions, instead of having the test codeunits inside the same extension makes it impossible to do test driven development with Business Central. The current process of first having to download symbols for the main app each time we go back to edit the tests (plus having to unpublish the test app, before republishing the main app), means that the developer must wait minutes between each red-green-refactor step. Ideally if we had two (or more) dependent extensions inside the same workspace in Visual Studio Code, then the AL compiler shouldn’t have the depend on the .App symbol files. It should be able to use the actual source files. Technically this should be possible, as all information is already present inside the VSCode workspace and the App.json files. If possible then it should also allow us to use Go to Definition to the actual file and rename references across extensions, if they are within the same workspace.