Closed Arthurvdv closed 1 year ago
Dear @Arthurvdv ,
Thanks for proposition, makes perfect sense. We did already have the code ready for this, just needed the parameter mapping. Since it's a small change, we'll try to hotfix this in the current version asap.
We'll keep you posted.
Kind regards,
Dear @Arthurvdv ,
Could you please v1.455.3596 ? Next to "LATEST" you can now also use "PRERELEASE" in the VSIX parameter. Current the "LATEST" will give you AL-Language v11, "PRERELEASE" will get v12.
Kind regards,
Works perfectly, thanks!
Describe the bug On retrieving the latest AL Language from the ALOpsAppCompiler@2 step, the retrieved version is different then expected. This causes an error when using the BC LinterCop, more details here https://github.com/StefanMaron/BusinessCentral.LinterCop/issues/283.
Expected: 11.0.11.58421 Actual: 12.0.779795
Looking at the AL Language extension page on the marketplace it's not wrong that the v12 is "the latest". Problem is that VS Code is working with v11. and v12 is a pre-release.
the used yaml please provide the yaml that you used. It helps you put the yaml like this:
the output Also the complete output is necessary for us to see what is going on. Also use backtics:
Expected behavior Setting the parameter alternativevsixurl with the value Latest on the ALOpsAppCompiler (v1 and v2) should grab the v11 in stead of the v12 version of AL Language.
So setting the parameter to 'Latest' wil grab the the v11 version of the AL Language A bonus (nice-2-have) could be setting the parameter to 'Prerelease' that then wil grab the v12 version.
Screenshots![image](https://user-images.githubusercontent.com/44637996/230101256-1359e02f-5579-48d9-ad4c-c7772bd5b4c9.png)
Additional context At first glance is seems possible to distinct the Prerelease version of the Current version. https://github.com/microsoft/navcontainerhelper/blob/master/ContainerHandling/Get-LatestAlLanguageExtensionUrl.ps1