Managing DotNET Dependencies on AppSource for Business Central

When you try to convert existing C/Side objects to AL the first attempts are typically done while scoping OnPrem. This gives an overview of the errors to be fixed w.o things like DotNET.

In this phase you typically switch between C/Side and Visual Studio Code all the time fixing the errors one-by-one and reconverting.

Source : Mark Brummel Blog
Read more…

Dynamics 365 Business Central: using DotNet assemblies on a Docker container sandbox

I think that everyone of you already knows that calling custom .NET DLLs in your extension’s code is not supported in a SaaS environment, but you can still use .NET assemblies in your extensions if you explicitly target the on-premise world.

Source : Stefano Demiliani
Read more…

Six months with extensions – Goodbye to the last DotNet

During the year, I have rolled up to several of the Dynamics NAV 2018 cumulative upgrades implementing new functionalities and unfortunately also fixed multiple errors in the standard application.

Upgrading to Dynamics NAV 2018 CU 5: the sales lines started to give the error: Another user has changed the sales line. Just entering the Line Type, The Item No. and the Unit of Measure code. Therefore, entering a line you needed to leave the document window and reenter to continue.

Bron : Aphorisms about Microsoft Dynamics NAV
Lees meer…

Convert Nav Report (that used a DotNet List) into AL Extension

When developing Extensions for NAV, using the Modern Development Environment in Visual Studio Code, you cannot use .Net Interoperability. See this link if you want to read more about this subject.

So if you have NAV developments that use .Net and you want to move them into Extensions you will probably need to replace the logic implemented using .Net with something else.

Bron : Andrei Lungu
Lees meer…