search

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
748 stars 245 forks source link

In-client designer crashes when designing on custom database #1853

Closed r4luk closed 6 years ago

r4luk commented 6 years ago

Hello everybody, We encounter the following error when trying to design a page in our localized version of NAV 2018 CU2 installed on a local VM: img_26032018_112912_0

We are using AL Language 0.12.16641.

We didn't publish any extension from VS Code. We just tried to design a page (e.g. Sales Order List - to add/remove a field).

On the W1 version the in-client designer works fine.

On our localized version, after the adding/removing the field, the designer crashes:

img_26032018_113345_0 img_26032018_113443_0

We downloaded the symbols in VS Code. We published succesfully the symbols with cmdlet -SymbolsOnly. We changed NetFx40_LegacySecurityPolicy setting in Microsoft.Dynamics.Nav.Server.exe.config file to "false" and restarted NAV Server Instance.

We searched for similar issues, and we found #296.

Does anyone else still has the same problem? How can we solve it?

Thanks a lot, Raluca

kalberes commented 6 years ago

The event viewer entry claims that you do not have the application symbols in your database. How did you add the application symbols ? I think you have just added the system symbols?

https://blogs.msdn.microsoft.com/nav/2018/01/16/generate-symbols-in-a-modern-development-environment-with-microsoft-dynamics-nav-2018/ https://blogs.msdn.microsoft.com/nav/2018/02/02/import-symbols-in-new-or-upgrade-databases-with-microsoft-dynamics-nav-2018/ https://docs.microsoft.com/en-us/dynamics-nav/developer/devenv-running-cside-and-al-side-by-side

r4luk commented 6 years ago

Thank you very much. We thought about that, but also in the links that you mentioned (last one) it says: "If you are upgrading to Microsoft Dynamics NAV 2018 CU1, or higher, please use the symbols that you find in the ModernDev folder on the cumulative update DVD." We are using NAV 2018 CU2 and on the DVD we have: kit

We generated the symbols as it is stated in the other link: image

And we have the following result: image

All this didn't solve the problem. What are we doing wrong?

kalberes commented 6 years ago

That means that you have the test and system symbols in place. The designer on the other hand still does not "see" your app symbols. Does the "Hello World" VsCode sample work for you. Can you publish it from within VsCode?

r4luk commented 6 years ago

Yes, we can publish the Hello World sample. image

kalberes commented 6 years ago

What happens if you publish the symbol file named Microsoft_Application* (as symbols) that you have downloaded in VSCode. This is the symbol reference file generated from C/SIDE?

r4luk commented 6 years ago

We manage to download the Microsoft_Application* symbols and we published them. image

So now we have: image

And the in-client designer works. Yey!

Maybe it would be helpful to update the info in the link: https://docs.microsoft.com/en-us/dynamics-nav/upgrading-the-data#AddExtensions because it says: image

We were using NAV 2018 CU2, so we published only the symbols we found on the DVD: image

Thank you very much. Raluca

StanislawStempin commented 6 years ago

The documentation has been updated to reflect the additional step of application symbol generation. Closing this issue.