Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.
SAP Sybase SQL Anywhere 16.0 » SQL Anywhere Server - Programming » Database and application deployment » Requirements for deploying client applications

 

.NET client deployment

The simplest way to deploy .NET assemblies is to use the Deployment Wizard. For more information, see The Deployment Wizard.

To complete the installation of the .NET assemblies on the client computer, you must do the following.

  • Ensure Visual Studio is not running.

  • Use the SetupVSPackage tool to install the .NET assemblies. SetupVSPackage requires Administrator privilege for Windows Vista and later systems. If you are running a Command Prompt, ensure it has Administrator privilege.

  • For .NET 2.0/3.x, run %SQLANY16%\Assembly\v2\SetupVSPackage.exe /install.

  • For .NET 4.x, run %SQLANY16%\Assembly\v4\SetupVSPackage.exe /install.

  • By default, SetupVSPackage will use SQL Anywhere registry settings to locate the .NET assemblies. You can specify the location of the SQL Anywhere installation by using the salocation option. 

    %SQLANY16%\Assembly\v2\SetupVSPackage.exe /install /salocation %SQLANY16%

    The short form for salocation is sal.

The SetupVSPackage application updates the Global Assembly Cache and the Windows Microsoft.NET machine.config file. If SQL Server 2008 or later is installed on the system, SetupVSPackage also installs two mapping files called MSSqlToSA.xml and SAToMSSql10.xml to the SQL Server DTS\MappingFiles folder.

The SetupVSPackage application copies SSDLToSA16.tt to the Visual Studio 2010 directory. It is used for generating database schema DDL for Entity Data Models. The user should set the DDL Generation property to this file when generating database schema DDL for Entity Data Models.

To create your own installation, this section describes the files to deploy to the end users. There are several message files each supporting a different language. To install support for different languages, you have to include the resource files for these languages. Replace [LL] with the language code (for example, en, de, jp, and so on).

Each .NET client computer must have the following:

  • A working .NET 2.0, 3.0, 3.5, 4.0, or 4.5 installation   Microsoft .NET assemblies and instructions for their redistribution are available from Microsoft Corporation. They are not described in detail here.

  • SQL Anywhere provider for .NET Framework 2.0/3.0   The SQL Anywhere installation places the Windows assemblies for the .NET Framework versions 2.0 and 3.0 in the Assembly\V2 subdirectory of your SQL Anywhere installation directory. The other files are placed in the operating-system binaries directory of your SQL Anywhere installation directory (for example, bin32 and bin64). The following files are required. 
    iAnywhere.Data.SQLAnywhere.dll
policy.16.0.iAnywhere.Data.SQLAnywhere.dll
dblg[LL]16.dll
dbicu16.dll
dbicudt16.dll

  • SQL Anywhere provider for .NET Framework 3.5   The SQL Anywhere installation places the Windows assemblies for the .NET Framework version 3.5 in the Assembly\V3.5 subdirectory of your SQL Anywhere installation directory. The other files are placed in the operating-system binaries directory of your SQL Anywhere installation directory (for example, bin32 and bin64). The following files are required. 
    iAnywhere.Data.SQLAnywhere.v3.5.dll
policy.16.0.iAnywhere.Data.SQLAnywhere.v3.5.dll
dblg[LL]16.dll
dbicu16.dll
dbicudt16.dll

  • SQL Anywhere provider for .NET Framework 4.0/4.5   The SQL Anywhere installation places the Windows assemblies for the .NET Framework versions 4.0 and 4.5 in the Assembly\V4 subdirectory of your SQL Anywhere installation directory. The other files are placed in the operating-system binaries directory of your SQL Anywhere installation directory (for example, bin32 and bin64). The following files are required. 
    iAnywhere.Data.SQLAnywhere.v4.0.dll
policy.16.0.iAnywhere.Data.SQLAnywhere.v4.0.dll
dblg[LL]16.dll
dbicu16.dll
dbicudt16.dll

  • SQL Anywhere provider for .NET Compact Framework 2.0   The SQL Anywhere installation places the Windows Mobile assemblies for the .NET Compact Framework version 2.0 in CE\Assembly\V2. The other files are placed in the Windows Mobile binaries subdirectory of your SQL Anywhere installation directory (for example, CE\Arm.50). The following files are required. 
    iAnywhere.Data.SQLAnywhere.dll
iAnywhere.Data.SQLAnywhere.gac
dblg[LL]16.dll
dbicu16.dll

  • SQL Anywhere provider for .NET Compact Framework 3.5   The SQL Anywhere installation places the Windows Mobile assemblies for the .NET Compact Framework version 3.5 in CE\Assembly\V3.5. The other files are placed in the Windows Mobile binaries subdirectory of your SQL Anywhere installation directory (for example, CE\Arm.50). The following files are required. 
    iAnywhere.Data.SQLAnywhere.v3.5.dll
dblg[LL]16.dll
dbicu16.dll

For more information about deploying the SQL Anywhere .NET Data Provider, see SQL Anywhere .NET Data Provider deployment and ClickOnce and .NET Data Provider unmanaged code DLLs.

ClickOnce and .NET Data Provider unmanaged code DLLs
SQL Anywhere .NET Data Provider removal

Copyright © 2014, SAP AG or an SAP affiliate company. - SAP Sybase SQL Anywhere 16.0