Applies to DotNetBar 5.9 or older only.

Scenario: InstallShield or some other install tool is used to create custom file type association for your executable. This is for example used to provide your users ability to double click the files that are saved by your application in windows explorer and open them.

When you start your application this way the “Not Registered” dialog box shows up if your executable file name is longer than 8 characters. If application is started normally by double clicking the EXE file it works as expected.

The problem is that file association that is created using the short file name instead of the full file name. This throws off the .NET licensing in the same way that renaming the file does and embedded resource file that contains licensing information is not found by .NET framework.

If you create the file associations using windows explorer though everything works as expected.

Related posts:

  1. How to Embed definition file in VC++
  2. Command line compilation and licensing
  3. How to perform clean install of DotNetBar
  4. Deploying, Distributing DotNetBar for Windows Forms
  5. GDI+ Exceptions