web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Answered

How to deal with DotNet or dll files while moving from onPrem to Cloud (AppSource) development in Business Cnetral

(0) ShareShare
ReportReport
Posted on by 241

Hello everyone,

How are you all? Hope you all are fine. I am looking for a way to deal with dll or DotNet files while moving from onPrem to Cloud development in Business Central.

I've been already passed through all the following technical validations for moving from onPrem to AppSource. 

https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-checklist-submission 

But when I changed "target" property in app.json from "OnPrem" to "Cloud"

"target" : "Cloud"

I got several errors regarding DotNet or dll files.

appjson.jpg dotNet.jpg

Can anyone please tell me that how can I deal with these errors or how can I move from onPrem to Cloud (AppSource) development within these dll or DotNet files. Answers will be highly appreciated. Thanks for reading.

 

I have the same question (0)
  • Verified answer
    Lars Lohndorf-Larsen Profile Picture
    on at
    RE: How to deal with DotNet or dll files while moving from onPrem to Cloud (AppSource) development in Business Cnetral

    Good point about the new .al datatypes to replace some .net uses.

  • Verified answer
    Steven Renders Profile Picture
    5,630 Moderator on at
    RE: How to deal with DotNet or dll files while moving from onPrem to Cloud (AppSource) development in Business Cnetral

    .NET interop is not allowed in BC Saas. .NET Interoperability is only available on-premise.

    FAQ for Developing in AL - Business Central | Microsoft Docs

    For cloud solutions .NET interop is not available due to safety issues in running arbitrary .NET code on cloud servers.

    With the AL Language extension, you can find AL types that replace the most typical usages of .NET like HTTP, JSON, XML, StringBuilder, Dictionaries, and Lists. Many .NET usages can be replaced directly by the AL types resulting in much cleaner code. For more information, see HTTP, JSON, TextBuilder, and XML API Overview.

    For things that are not possible to achieve in AL code, the recommendation is to use Azure Functions to host the DLL or C# code previously embedded and call that service from AL.

  • Verified answer
    Lars Lohndorf-Larsen Profile Picture
    on at
    RE: How to deal with DotNet or dll files while moving from onPrem to Cloud (AppSource) development in Business Cnetral

    Hello,

    Good question. You need to move the dll functionality to also run in the cloud. Azure functions is designed for that. A few good places to start:

    docs.microsoft.com/.../

    community.dynamics.com/.../business-central-nav-integration-with-azure-service-bus-using-azure-function

    And, I am sure that these sites can also help:

    https://demiliani.com/

    https://www.kauffmann.nl/

    https://www.hougaard.com/

    And I hope you get more replies here with more details.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Andrés Arias – Community Spotlight

We are honored to recognize Andrés Arias as our Community Spotlight honoree for…

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
Sumit Singh Profile Picture

Sumit Singh 2,710

#2
Sohail Ahmed Profile Picture

Sohail Ahmed 2,675 Super User 2025 Season 2

#3
Jeffrey Bulanadi Profile Picture

Jeffrey Bulanadi 2,203

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans