Skip to content

Troubleshooting

This guide addresses common issues you may encounter when working with Flexible TreeView and provides solutions.

"Trial period has expired or wrong license key" error#

Symptoms#

This error occurs when running or compiling your application that uses Flexible TreeView.

For trial version#

  1. If your trial period has expired, purchase a license
  2. Verify the Properties\license.licx file exists in your .NET Framework project (not applicable to .NET projects), its build action is set to Embedded resource and it has the following content: 
    ARMSoft.FlexibleTreeView.FlexibleTreeView, ARMSoft.FlexibleTreeView, Version=X.X.X.X, Culture=neutral, PublicKeyToken=a0f39221011ef811
    Replace X.X.X.X with your Flexible TreeView version (e.g., 6.0.0.0)

For licensed version#

  1. Verify the Properties\license.licx file exists in your .NET Framework project (not applicable to .NET projects), its build action is set to Embedded resource and it has the following content: 

    ARMSoft.FlexibleTreeView.FlexibleTreeView, ARMSoft.FlexibleTreeView, Version=X.X.X.X, Culture=neutral, PublicKeyToken=a0f39221011ef811
    Replace X.X.X.X with your Flexible TreeView version (e.g., 6.0.0.0)

  2. It could be that Windows blocks access to the registry for your user, especially on Windows x64. To fix this:

    • Restart Visual Studio as administrator and reapply your license
    • Restart Visual Studio normally to continue development

Licensed version: Missing Unlock button in About window#

If the Unlock button is missing when trying to install your license key, you may still be using the trial version.

To resolve:

  1. Uninstall all versions of Flexible TreeView
  2. Remove any ARMSoft.FlexibleTreeView.* assemblies from the .NET GAC
  3. Clear the NuGet cache
  4. Install the registered version
  5. Try applying your license key again. The Unlock button should now be visible

.NET: NuGet Package Cache Issues#

When upgrading Flexible TreeView in a .NET project (not applicable to .NET Framework projects), but the old version persists, clear the NuGet cache as described in this guide.