I recently opened a issue in the AL repo (https://github.com/microsoft/AL/issues/7611) because multiple unnecessary vsc tabs are opened for the same *.dal files. So you can end up with 4 different tabs with identical content:
That's most likely because of the path behind the dal files. e.g.
vs
The first three tabs are the responsibility of the AL vsix, but the last one comes from opening objects from the AZ AL object browser.
The AL vsix is also not encoding file names (or paths) anymore, so Prod. Order Line should be Prod. Order Line and not Prod.+Order+Line
AZ AL Devtools is also using the workspace name as the first segment of the path and not the real folder name:
This can also potentially make a difference to the path. But maybe Microsoft will change this path, so we shouldn't change this immediately. The workaround is to remove the "name" of the folder from the workspace file, so VSC uses the folder name.
In the end that's pretty annoying with a lot of break points that are set one after another while debugging and navigating code in different ways:
(Screenshot is a made-up example)
I recently opened a issue in the AL repo (https://github.com/microsoft/AL/issues/7611) because multiple unnecessary vsc tabs are opened for the same *.dal files. So you can end up with 4 different tabs with identical content:
That's most likely because of the path behind the dal files. e.g.
vs
The first three tabs are the responsibility of the AL vsix, but the last one comes from opening objects from the AZ AL object browser. The AL vsix is also not encoding file names (or paths) anymore, so
Prod. Order Lineshould beProd. Order Lineand notProd.+Order+LineAZ AL Devtools is also using the workspace name as the first segment of the path and not the real folder name:
This can also potentially make a difference to the path. But maybe Microsoft will change this path, so we shouldn't change this immediately. The workaround is to remove the "name" of the folder from the workspace file, so VSC uses the folder name.
In the end that's pretty annoying with a lot of break points that are set one after another while debugging and navigating code in different ways:
(Screenshot is a made-up example)