microsoft / AL

Home of the Dynamics 365 Business Central AL Language extension for Visual Studio Code. Used to track issues regarding the latest version of the AL compiler and developer tools available in the Visual Studio Code Marketplace or as part of the AL Developer Preview builds for Dynamics 365 Business Central.
MIT License
744 stars 245 forks source link

macOS: Unable to load Analyzer assembly #4159

Closed salgiza closed 4 years ago

salgiza commented 5 years ago

The al.codeAnalyzers don't work in macOS.

If you create a settings.json file and add the following configuration:

{
    "al.enableCodeAnalysis": true,
    "al.codeAnalyzers": [
        "${PerTenantExtensionCop}",
        "${CodeCop}",
    ]
}

The code analyzer does not start, and an error is shown instead:

image

This happens using the VS Code AL Language Extension v2.0.48254.

salgiza commented 5 years ago

Any updates on this? Do you think it will be fixed before the April release?

attieretief commented 5 years ago

Any plans to support this soon?

DanielGoehler commented 5 years ago

Hi @atoader, any update on this? Version 3 and 4 still have this issue.

Are Microsoft.Dynamics.Nav.CodeCop.dll and Microsoft.Dynamics.Nav.UICop.dll compiled in DotNet Core?

atoader commented 5 years ago

@attieretief this item is in our backlog, but I cannot give an estimate on when this will be available. @DanielGoehler the VSIX contains binaries that run both on the full .NET Framework and on .NET Core.

attieretief commented 5 years ago

@atoader thanks...I'll keep an eye out for it

DanielGoehler commented 4 years ago

Hi @atoader,

the Analyzer is still not working on macOS.

Unable to load Analyzer assembly /Users/daniel/.vscode/extensions/ms-dynamics-smb.al-4.0.199169/bin/darwin/Analyzers/Microsoft.Dynamics.Nav.CodeCop.dll : File /Users/daniel/.vscode/extensions/ms-dynamics-smb.al-4.0.199169/bin/darwin/Analyzers/Microsoft.Dynamics.Nav.CodeCop.dll was not found.

yrest commented 4 years ago

Same here, everything else seem to be good except the cops.

ALGitHubBot commented 4 years ago

The fix for this issue has been checked in to the master branch. It will be available in the bcinsider.azurecr.io/bcsandbox-master Docker image starting from platform build number 38574.

If you don’t have access to these images you need to become part of the Ready2Go program: aka.ms/readytogo

For more details on code branches and docker images please read: https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/ https://blogs.msdn.microsoft.com/freddyk/2018/04/16/which-docker-image-is-the-right-for-you/