How to: Determine the Public Key Token of the Windows Client Control Add-in and .NET Framework Assembly
To use a Microsoft Dynamics NAV Windows client control add-in on a Microsoft Dynamics NAV Windows client page, you must register the assembly that contains the control add-in on the Control Add-ins page of the Microsoft Dynamics NAV 2016 database. To register an assembly, you provide the assembly's public key token. The public key token is a unique 16-character key that is given to the assembly when it is built and signed in Microsoft Visual Studio. To determine the public token key, you can run the Strong Name tool (sn.exe) on the assembly. The sn.exe is available with the Microsoft .NET Framework SDK. For more information about how to sign assemblies, see Strong Name Signing (sn.exe) or How to: Create a Windows Client Control Add-in.
To determine the public key token
Locate the sn.exe file.
The default folder for the Microsoft .NET Framework SDK is C:\Program Files\Microsoft SDKs\Windows\v7.0\Bin.
At the command prompt, change to the directory that contains the sn.exe utility.
Type the following command.
sn.exe -T <assembly>
<assembly>with the add-in assembly's path and file name, such as C:\Program Files (x86)\Microsoft Dynamics NAV\90\RoleTailored Client\Add-ins\MyCompany.MyProduct.RtcAddins.dll.
Press Enter and note the public token key that is displayed.
How to: Create a Windows Client Control Add-in
How to: Install a Windows Client Control Add-in Assembly
Windows Client Control Add-in Overview
Developing Windows Client Control Add-ins
Installing and Configuring Windows Client Control Add-ins on Pages