Checklist for Deployment

Checklist for all .NET targets

For deployment of all .NET target types (Windows Forms, Web Forms, .NET Assembly, .NET Web Service), production servers or target computers must have:

• The Windows XP SP2, Windows Vista, Windows 2008, or Windows 7 operating system
• .NET Framework 4.0
• The Microsoft Visual C++ runtime libraries msvcr71.dll, msvcp71.dll, msvcp100.dll, msvcr100.dll, and the Microsoft .NET Active Template Library (ATL) module, atl71.dll
• PowerBuilder .NET assemblies in the global assembly cache (GAC)
• PowerBuilder runtime dynamic link libraries in the system path

  See Deploying PowerBuilder runtime files.

Checklist for .NET Web Forms and Web Service targets

For .NET Web Forms and Web Service targets, production servers must have:

• IIS 5 or later (See IIS Installation)
• ASP.NET (See Selecting the Default ASP.NET Version)
• ASP.NET permissions for all files and directories used by your applications

  For an example of how to grant ASP.NET permissions, see Setting Up a SQL Anywhere Database Connection. For command line instructions granting ASP.NET permissions to deployed application directories, see ASP .NET user permissions.

For information on different methods for deploying .NET Web Forms applications to a production server, see Deploying to a production server. These methods are also valid for deployment of .NET Web Service components.

Deploying PowerBuilder runtime files

The simplest way to deploy PowerBuilder runtime DLLs and .NET assemblies to production servers or target computers is to use the PowerBuilder Runtime Packager tool. The Runtime Packager creates an MSI file that installs the files you select, registers any self-registering DLLs, and installs the .NET assemblies into the global assembly cache (GAC).

For a list of base components deployed when you select PowerBuilder .NET Components in the Runtime Packager, see Application Techniques > Deploying Applications and Components. The Runtime Packager installs additional components depending on the options you select in its user interface.

Sybase.PowerBuilder files are strong-named .NET assemblies that can be installed into the GAC. For more information about the GAC, see Installing assemblies in the global assembly cache.

Installing assemblies in the global assembly cache

When the Common Language Runtime (CLR) is installed on a computer as part of the .NET Framework, a machine-wide code cache called the global assembly cache (GAC) is created. The GAC stores assemblies that can be shared by multiple applications. If you do not want or need to share an assembly, you can keep it private and place it in the same directory as the application.

If you do not want to use the Runtime Packager to deploy your application, you should use Windows Installer or another installation tool that is designed to work with the GAC. Windows Installer provides assembly reference counting and other features designed to maintain the cache.

On the development computer, you can use a tool provided with the .NET Framework SDK, gacutil.exe, to install assemblies into the GAC.

Some assemblies, like RadCalendar.NET2.dll, RadInput.Net2.0.dll, RadMenu.Net2.Dll, RadToolBar.Net2.dll, and RadTreeView.Net2.dll, are still installed into the .NET Framework 2.0 GAC windows\assembly directory.

Assemblies deployed in the global assembly cache must have a strong name. A strong name includes the assembly’s identity as well as a public key and a digital signature. The GAC can contain multiple copies of an assembly with the same name but different versions, and it might also contain assemblies with the same name from different vendors, so strong names are used to ensure that the correct assembly and version is called.

For more information about assemblies and strong names, see the Microsoft library at http://msdn.microsoft.com/en-us/library/wd40t7ad(VS.71).aspx.