UniDirect .NET Frequently Asked Questions

• Bundled Devart data providers for accessing Oracle, MySQL, and PostgreSQL servers without additional software.
• Support for DBMonitor to perform per-component tracing of database events such as SQL statement execution, commit, rollback, etc.
• DataSet Wizard for greatly simplifying the process of generating datasets in your application.
• Enterprise Library support for taking advantage of Data Access Application Block functionality.
• ASP.NET 2.0 Provider Model support for using UniDirect .NET as one of the ASP.NET 2.0 providers.

This generally indicates that license information could not be found, or you try to apply it in some way that does not suit the kind of application. For example:

• File licenses.licx, required for UniDirect .NET to function properly, could not be found.
• File licenses.licx is not added as embedded resource.
• File App_Licenses.dll not found in ASP.NET applications.

To fix the problem determine type of your application and read corresponding section of "Licensing" topic.

This means that license information was found but it is incorrect. It usually happens in the following cases:

• The project was earlier compiled with old or trial version of data provider.
• File licenses.config used by a class library does not refer to launched executable.
• The App_Licenses.dll belongs to other application or needs to be recompiled.
• Something's wrong with the operating system or installation of UniDirect .NET.

If you encounter this problem delete all files from obj folder and rebuild the project. If this does not help send to our support address small compiled binary with sources so we can investigate the problem detailed.

To support server-side compilation you ought to have special assembly App_Licenses.dll in the Bin directory of your site. To create this assembly execute Build Runtime Licenses command in the licenses.licx file context menu in the Solution Explorer view. Required assembly will be created automatically.

Note that this is not necessary for precompiled ASP.NET applications (if nothing is compiled on server by user request). Precompiled applications are licensed as usual applications.

• Use appropriate shortcut in start menu, for instance, Start - Programs - Devart UniDirect .NET - UniDirect .NET documentation.
• Use command in the IDE: Tools - UniDirect - UniDirect .NET Help.
• Position cursor on some class from CoreLab.UniDirect and press F1.

• You have UniDirect provider assembly (such as CoreLab.UniDirect.MySql.dll) on your device in the application's directory.
• You have a target provider assembly (such as CoreLab.MySql.dll) on your device in the application's directory.

• You have application config file (DeviceApplication.exe.config) with <bindingRedirect> element for your target provider assembly (e.g. CoreLab.MySql). This is needed when version of target provider assembly differs from version that UniDirect was designed for.

  Here is an example of the application config file (DeviceApplication.exe.config) in the case when target provider is dotConnect for MySQL and the application name is DeviceApplication.exe:

  <configuration>
    <runtime>
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <dependentAssembly>
          <assemblyIdentity name="CoreLab.MySql"
            publicKeyToken="09af7300eec23701"
            culture="neutral" />
          <bindingRedirect oldVersion="4.25.22.1"
            newVersion="4.25.25.1"/>
        </dependentAssembly>
      </assemblyBinding>
    </runtime>
  </configuration>
  

  In this file oldVersion represents the assembly that UniDirect .NET was designed for, and newVersion is the version of CoreLab.MySql.dll you actually use.

  The example configuration files are located in the folder where you installed UniDirect .NET. You have to copy the file to your project, rename it to match the application name, and adjust the newVersion attribute of the bindingRedirect tag to match your version of the provider assembly.