
Upgrading the Data to Microsoft Dynamics NAV 2018
Applies to: Microsoft Dynamics NAV 2018. See Microsoft Dynamics NAV 2017 version.

Windows Client Control Add-ins in Microsoft Dynamics NAV are delivered as .NET Framework–based assemblies (.dll files). To use a control add-in in the NAV Windows (RoleTailored) Client, the corresponding assembly must be available on the computer where the client is running.
Windows Client Control Add-ins in Microsoft Dynamics NAV are delivered as .NET Framework–based assemblies (.dll files). To use a control add-in in the NAV Windows (RoleTailored) Client, the corresponding assembly must be available on the computer where the client is running.
In certain development scenarios—such as compiling objects that reference a control add-in—the assembly must also be installed on the machine running the NAV Development Environment.
Control add-in assemblies can be installed using two main approaches:
Each approach has different use cases, explained below.
This method is useful for:
.dll files. Default path:
C:\Program Files (x86)\Microsoft Dynamics NAV\100\RoleTailored Client\Add-insNote:
You can place assemblies inside subfolders within the Add-ins directory. This is recommended when working with multiple add-ins or dependencies.
Once copied, the control add-in becomes immediately available to the client.
NAV supports automatic deployment of control add-ins when:
With automatic deployment, assemblies are centrally managed and deployed to clients as needed.
When a NAV Windows Client requires a control add-in (for example, when opening a page that uses it), the following sequence occurs:
C:\Program Files (x86)\Microsoft Dynamics NAV\100\RoleTailored Client\Add-insC:\Program Files\Microsoft Dynamics NAV\110\Service\Add-ins%TEMP%\Microsoft Dynamics NAV\Add-InsThe deployed assembly remains available until a newer version is detected.
%TEMP%\Microsoft Dynamics NAV\Add-InsThis mechanism ensures version safety without impacting running clients.
When compiling objects that reference control add-ins:
This allows compilation and testing without manual copying.
To enable automatic deployment via the server:
C:\Program Files\Microsoft Dynamics NAV\110\Service\Add-insThis makes the add-in available to all clients connected to that server instance.
This method is useful for:
.zip file containing the control add-in assemblies in the desired folder structure. .zip file. The control add-in is now stored in the database and deployed automatically when required.
Control add-ins can also be managed using the NAV Administration Shell:
New-NAVAddinSet-NAVAddinGet-NAVAddinRemove-NAVAddinThis is especially useful for scripted deployments and automation.
Windows Client Control Add-ins in NAV can be installed manually or deployed automatically via the server or database. Automatic deployment is the preferred approach for production environments, while manual installation is often used during development and troubleshooting.
Understanding how NAV locates, deploys, caches, and updates control add-ins is essential when performing upgrades, troubleshooting client issues, or transitioning legacy solutions.

Premanath Kumarage
Author

Applies to: Microsoft Dynamics NAV 2018. See Microsoft Dynamics NAV 2017 version.

Source: https://docs.microsoft.com/en-us/dynamics-nav/Configuring-the-Windows-Client

Applies to: Microsoft Dynamics NAV 2018. See Microsoft Dynamics NAV 2017 version.
Start here
A working session, not a sales call. Bring the process your current system fights you on, and we will tell you plainly what it would take to fix it.
Newsletter
Stay ahead with Microsoft Business Applications.
Insights, implementation advice and practical ideas to help your business get more from Microsoft technology.
By subscribing, you acknowledge MicroCloud 360’s Privacy Policy.