Working with BinaryProjects with a VSCode Workspace only translates first extension XLIFF

[JavierFuentes]

Hi @LauraNicolas, after some tests, we think that for our scenario where we maintain internally our own Business Central customizations (hundreds or thousands of them), we think a Binary-Extensions Model of Projects could simplify our daily work and reduce the data lost risk...

It is based on this MS Official Document that says that we can work with a Multiroot Workspace with our Business Central Extensions:

https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-multiroot-workspaces

So, we split Tables, TableExtensions and Enums in a first Extension from the rest of Object Types in a second Extension, both under the same VSCode Workspace and Git repository...

You can read this issues for more info:

https://github.com/Microsoft/AL/issues/4363 , https://github.com/Microsoft/AL/issues/4364 and https://github.com/Microsoft/AL/issues/4450

We have tested in this scenario your VSCode Extension for making translations more easy to maintain, and we have noticed that ONLY the first extension XLIFF translation is generated always, without taking into account what is the active file like AL Compiler does correctly...

You can test this with this example:

WorkspaceTranslationIssue.zip

Also, if you set the .alpackages folder the first in workspace configuration file, your extension will crash:

[LauraNicolas]

Thanks Javier,

I will take a look at it and get back to you.

Salut! Laura Nicolàs