Open topic with navigation
References enable a traditional Synergy project in Visual Studio to use libraries (ELBs and OLBs). Referencing a library is equivalent to linking to a library—i.e., equivalent to adding a library to a dblink command—when developing outside of Visual Studio. (References also enable you to use repository projects. See Using Synergy/DE repositories in Visual Studio.)
To add a library reference to a traditional Synergy project, right-click the References node for the project in Solution Explorer, and then select Add Reference from the context menu. Note the following:
An OLB project should be referenced by only one project in the solution. Referencing an OLB project from multiple projects causes the OLB code to be compiled into multiple files for the application. (When creating a library for shared code, use an ELB rather than an OLB.)
We recommend using environment variables when referencing ELBs. Paths to ELBs are hard-coded in applications and libraries that reference them, and they are limited to 31 characters. To use an environment variable when referencing an ELB, do one of the following:
If you use a tab other than the Synergy or Project tab, or if you use the Project tab without specifying an environment variable in “Output path”, the full path to the ELB on the development machine will be hard-coded in the executable or library that references the project (if the path does not exceed 31-characters). The hard-coded path will then be used to locate the ELB on deployment machines.
Keep in mind that if you use environment variables when referencing ELBs, those environment variables must be set on deployment machines. If an environment variable for a referenced ELB is not set on a deployment machine, the Synergy runtime will look for that ELB in the current directory for the running DBR.