One of the things that can be really annoying in Dynamics NAV or Business Central is the dependent apps.
What are dependent apps?
Some partners have made a base app that will contain all the basic functionality, that they use with all customers. Then they create apps that can be added to the solution but basing the solution on some data or functionality from the base app.
As you might know, there are two kinds of extensions in Business Central world: AppSource Extensions and Per-Tenant Extensions (PTE).
When you have finished developing and testing your tenant customization, you must deploy the extension (.app file) containing the customization to your customer’s production tenant. Recently I saw some discussions about whether it is possible to deploy a same PTE in the same version into different Tenants/Customers?
After my last webcast about Azure Functions, I received an interesting question: how can I quickly deploy a function to Azure? Or maybe to different Azure subscriptions or regions?
We saw in the webcast how you can deploy an Azure Function by using Visual Studio or Visual Studio Code directly. But Azure Functions have also a full range of continuous deployment and integration options provided by Azure App Service and you can deploy an Azure Function directly from a CI/CD pipeline in Azure DevOps. But there’s also a quickest way in my opinion: Zip deployment.
I’ve just got that question from a good friend, and though that I would write up my answer.
The short answer is, use Azure SQL!
How Do I: Deployment Microsoft Dynamics NAV 2016 Phone Client with Self-signed Certificate
This topic is in connection with my session “Deploying and Managing Dynamics NAV 2016 with Azure SQL Database” on NAV TechDays 15 and I want to continue my previous article.
A few days ago I have published my PowerShell script that streamlines and automates deployment of control add-ins from Visual Studio. Over the past couple of days I have improved it a little bit, and fixed a few bugs, so here’s an updated version that is more resilient to your project structure, produces resource zips that NST not only extracts, but actually understands, and does a little more.