I do agree with you on the drop zone.

If you right click the AL Extension in the Extension part of vscode there is an option to 'Install Another Version..'. I haven't tried it but I assume that this makes it easier to switch.

We are still using v.14 and it really sucks that we cannot compile with the default version. But it's not quite as bad as you make it. If you click the Unistall button, then you get the option of installing any one of older versions.

@hicamajig

Ай бұрын

The biggest annoyance seems to be the ability to develop for one cloud project that is on the latest version and one On-Prem using an older version. I haven't found a way to have separate versions of the AL Language extension on both yet so at some point I will be constantly installing different version unless I can find a way to do per workspace.

@Hougaard

Ай бұрын

Easiest way, install the insider VS Code, it's a separate VS Code instance with separate extensions installed.

@EPErnst

Ай бұрын

@@Hougaard That's also a good suggestion. Isn't there any "downsides" to using the insider build?

@Hougaard

Ай бұрын

Turn off updating when you're on a version that works :)

@Hougaard

Ай бұрын

But actually, this should work better: code.visualstudio.com/docs/editor/profiles

How to add today date on list page caption pls sir create new video pls pls🙏

Native Extensions is a real game changer. FINALLY. The introduction of namespaces really has changed the developer mindset over at MS, thank every god that ever was, finally we can have extensibility within the context of a single place! Not everything needs to know everything, even in a single app! namespace MyNamespace.Vehicles; table X Car ... (some properties/fields here) namespace MyNamespace.Vehicles.Racing; tableextension Y "Racing Car" extends MyNamespace.Vehicles.Car; ... (some racing specific properties/fields here)