This page lists system requirements for Synergy DBL Integration for Visual Studio (SDI). It includes the following:
This page lists required third-party products, but it does not list requirements for third-party products. For example, it lists the minimum version of Mono for Synergy applications on Linux, but it does not list Mono’s requirements (such as the minimum version of glibc needed for a given version of Mono). See third-party product documentation for information on these requirements.
For information on developing Synergy applications in Visual Studio, see Synergy in Visual Studio.
For information on developing Synergy applications for .NET, see Synergy .NET Development. For information on Synergy .NET development requirements, see Synergy .NET Requirements in the Synergy/DE documentation.
For information on Synergex.SynergyDE.synrnt, a NuGet package that contains runtime libraries required for device applications. See www.synergex.com/synrnt-nuget-package
The following are required and must be installed on a 64-bit Windows machine before SDI is installed on that machine. (SDI cannot be installed on 32-bit systems.)
You can install SDI on a machine that has MSBuild but not Visual Studio by selecting only the “MSBuild Components” option for the SDI installation. This installs only the SDI components required to build traditional Synergy and Synergy .NET applications and libraries from the command line.
Note the following:
For better performance, exclude the following programs from virus scanning: dbl.exe, dblnet.exe, dblnet64.exe, dblproto.exe, and devenv.exe. Also exclude the location used for prototype files (.dbp), and temporary Visual Studio files from virus scanning. (Alternatively you can exclude the .dbp extension and the extensions of .include files and repository files–e.g., .ism and .is1.)
To use remote debugging with a Synergy .NET application, the remote system must have Remote Tools for Visual Studio 2017 or 2019. To examine Synergy variables as you debug remotely, you must also install the Synergy .NET Remote Debugger on the remote system. See Debugging Synergy .NET Code in the Synergy/DE documentation for more information.
To deploy a Synergy .NET application for Microsoft .NET Framework, target systems must have .NET Framework and Synergy/DE Professional Series (which includes the Synergy .NET runtime libraries).
SDI supports .NET Core 2.1 or higher and .NET Standard 2.0 or higher.
The following are required for Synergy .NET Core and .NET Standard development:
NOTE: Upgrading to a new version of SDI does not upgrade compiler or runtime tools for existing .NET Core or .NET Standard projects. The following NuGet packages must be updated explicitly for these projects: Synergex.SynergyDE.synrnt and Synergex.SynergyDE.Build. To upgrade NuGet packages for existing projects, use the NuGet Package Manager. See Microsoft documentation for more information (e.g., Install and manage packages in Visual Studio using the NuGet Package Manager).
For information on deploying .NET Core applications, see Synergy .NET Requirements in the Synergy/DE documentation.
To deploy an application that runs under Mono on Linux, you must have a Linux system with Mono 3.2.8 or higher and Synergy/DE 10.3.1b or higher. (Note that the OS must natively support the Mono version. Downloading Mono sources and building them on the Linux machine will result in an unsupported configuration.)
Once you have installed Synergy/DE, use GACUTIL to add the runtime libraries (synrnt.dll) to the global assembly cache or make sure this file is in the same folder as your application binaries. The synrnt.dll file is in the dbl/bin directory for your Synergy/DE installation. Use the following command to add synrnt.dll to the global assembly cache:
For a traditional Synergy Linux application, you’ll need to run the application on a Linux machine and then use remote debugging to debug the application from Visual Studio or use standard traditional Synergy debugging on the Linux machine. In either case, the Linux machine must have the version of SDE that the application was built for (set with the “Target Synergy runtime” setting on the Build page of Visual Studio project properties).
For a traditional Synergy OpenVMS application, you may be able to do preliminary debugging with files built on Windows, but for final builds and full debugging you’ll need to build and run the application on an OpenVMS machine and then use remote debugging (to debug the application from Visual Studio) or use standard traditional Synergy debugging on the OpenVMS machine. In either case, the OpenVMS machine must have the version of SDE that the application was built for (set with the “Target Synergy runtime” setting on the Build page of project properties). Additionally, if code for OpenVMS includes DBL$ or SYS$ routines, the Visual Studio project with that code must reference the VmsCompatibility library (available for download at github.com/Synergex/VmsCompatibility) to be able to run on Windows. See Developing a traditional Synergy application in Synergy/DE documentation for more information.