Writing Your First AVEVA Historian SDK Application

The UI sample application demonstrates capabilities of the SDK in one universal GUI application. This section of the documentation walks you through the building blocks of such an application and the concepts behind the interface. The code snippets in this section can be found in the step-by-step console application solution installed in the SDK sample application folder.

The sample step-by-step console applications have the historian computer name, user name, and password hardcoded in the source files for simplicity. You may want to change them before recompiling and running those applications.

To be able to use the AVEVA Historian SDK programming interface, you need to add a reference to the aahClientManaged.dll to your project references. If you plan to build a 64-bit application, it should reference the 64-bit version installed by default in this folder:

C:\Program Files (x86)\ArchestrA\Toolkits\Bin\x64

If you plan to build a 32-bit application, you should have a reference to its 32-bit version installed by default in this folder:

C:\Program Files (x86)\ArchestrA\Toolkits\Bin\x86

IMPORTANT: AVEVA Historian SDK applications expect certain files to be available on the application path. To ensure the correct version of the SDK files are loaded, verify that C:\Program Files (x86)\ArchestrA\Toolkits\Bin\x64 is part of the application path if your application is 64-bit, or C:\Program Files (x86)\ArchestrA\Toolkits\Bin\x86 if your application is 32-bit. Applications compiled with the "Any CPU" target may not work correctly. Instead, you should choose either the 64-bit or 32-bit compile target and reference the appropriate SDK libraries.

After you have included a reference to the managed HCAL assembly, we recommend that you add the following statement to your source file to avoid repeating its namespace name everywhere in your code:

Add this statement

using ArchestrA;