Open topic with navigation
The following are the basic Synergy .NET development steps for desktop and server applications for .NET Framework on Windows x86 or x64. Most of these steps outline Visual Studio procedures, so see Visual Studio documentation for more information.
|1.||Start by reviewing Synergy .NET Requirements and the SDI requirements page (www.synergex.com/synergy-dbl-integration). Then set options for your Visual Studio environment as necessary. For example, you can control the behavior of the Visual Studio code editor and the way IntelliSense works for Synergy DBL files. See Options for Synergy/DE projects for more information.|
|2.||In Visual Studio, create a project for each assembly in your application, and put all the projects for your application in one solution. The following project templates are supported for .NET Framework development:|
For example, to create a console application (an application that runs from the command line), open Visual Studio without opening a solution and select File > New Project. Then select Synergy/DE from the Installed Templates area of the Project Dialog, and select Console App (.NET Framework) from the list of Synergy project types. You’ll need to set a few options for the project (name, location, and so forth) in the New Project Dialog; then click OK to create the project.
If you create a project when no solution is open in Visual Studio, a solution is automatically created to contain the project. Then, if this solution is open when you create other projects (e.g., class library projects), those projects will be added to the solution. See Synergy projects, solutions, and files for more information, and note the following:
|3.||Add DBL code, references to any needed assemblies, and other items to the projects for your application. See Synergy/DE item templates for information on new items you can add to a project, and note the following:|
|4.||Set project properties, which include settings for licensing, deployment, and building/compiling. See Synergy/DE project properties. For information on setting environment variables for a project, see Environment variables and Visual Studio development. For information on setting project properties for ClickOnce Deployment, see ClickOnce Deployment for Synergy .NET below.|
|5.||Build and debug the solution in Visual Studio using Visual Studio build and debug commands. See Visual Studio documentation for information on build features and the debugger. See Debugging Synergy .NET Code for debugging information specific to Synergy .NET. And see the Project Only information in SDI features for information on commands that enable you to build or rebuild (or clean) an individual project without affecting other projects in the solution, even referenced projects.|
|6.||Deploy your application to machines that meet deployment requirements listed in Synergy .NET Requirements.|
Use ClickOnce only for very simple deployments for Synergy .NET Windows desktop applications. ClickOnce deployment is not supported for traditional Synergy application or .NET Core applications.
ClickOnce is a Microsoft deployment technology that enables you to deploy self-updating, self-contained Windows desktop applications that don’t require administrative access to user systems. Setting up ClickOnce deployment can be as easy as setting properties on the Publish page of Project Designer and then clicking a publish button, but you may need to do more. For example, you may need to specify a Synergy license server.
Synergy .NET supports ClickOnce deployment through the following:
See Microsoft documentation for more information on ClickOnce deployment.
All ClickOnce deployments of Synergy applications should be to systems with Synergy/DE. The development system and target systems must have the same version of synrnt.dll and the same hotfixes, if any have been applied. And if you use the Synergy HTTP document transport API or OpenSSL libraries for Synergy data encryption, the system must have OpenSSL DLLs and either httpslib.dll or synssllib.dll. (See OpenSSL requirements for more information.)
Processor-independent application assemblies are not supported. Synergy applications deployed with ClickOnce must be built for either x86 or x64.
Although it is not supported, you may be able to deploy to a system that does not have Synergy/DE if your application doesn’t use HTTPS (with the Synergy HTTP document transport API), SQL Connection, or encryption (including xfServer). If you attempt this, note the following: