Skip to main content

#msdyn365bc - Clean your app.json file?

Hi Readers,

This article is about a quick change during AL Development.

This change can be implemented starting Business Central 15.3 and higher. 

With Business Central 17 the Visual Studio code automatically apply these setting when you create a new apps. 

As we all understand, that we all extension need to have at least dependent on Microsoft default apps.

Microsoft’s Application app introduced with Dynamics 365 Business Central version 15.3.

This app encapsulates all the dependencies from the System Application and Base Application apps and provides an abstraction to protect AppSource and PTE extensions.

What does that mean?

  • Remove the direct dependencies to the Base Application and System Application.
  • Add the "application" property in the app.json file and provide here the minimum Microsoft Base Application version that your app is compatible with.


Without these changes
  • You will have symbols downloaded for 
    • Microsoft_Base Application_x.x.x.x.app
    • Microsoft_System Application_x.x.x.x.app
    • Microsoft_System_x.x.x.x.app
With these changes 
  • You will get one more additional symbol for Microsoft_Application_x.x.x.x.app  

You only need to depend from Application and all other dependencies are transparently inherited.

All extensions submitted on AppSource must respect this requirement. 

Please update your app.json file as soon as possible.


Regards,
Saurav Dhyani

Labels:
Location: House No. 1, Shivlok Colony, 2, near Himalayan Academy Post Office, Shivlok Colony, Sewla Kalan, Majra, Dehradun, Uttarakhand 248171, India

Comments

Post a Comment

Popular posts from this blog

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------
10 comments
Read Complete Article »

RTC Report It is not possible to instantiate the Visual Studio bridge.

Hi all, As a Navision developers I have Multiple Versions of Navision running in single Machine. As discussed Earlier in the post how to run multiple Version of RTC in single machine. So my machine have following details for RTC Versions - NAV 2009 R2    - is installed. NAV 2009 SP1  - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 SP1 IN\ NAV 2009         - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 IN\ This approach has been working great for execution of Classic and RTC Clients. However, after installing Dynamics NAV 2009 R2, if i tried to view the Layout for an NAV 2009 SP1 Report i was getting the following error: ---------------------------  Microsoft Dynamics NAV Classic  ---------------------------  It is not possible to instantiate  the Visual Studio bridge.  ---------------------------  OK    --------------------------- After searchi...
4 comments
Read Complete Article »

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.
Post a Comment
Read Complete Article »