Telerik OpenAccess Classic

Telerik OpenAccess ORM Send comments on this topic.
Updating OpenAccess Assemblies
See Also
Programmer's Guide > OpenAccess ORM Classic (Old API) > Deploying Telerik OpenAccess ORM > Updating OpenAccess Assemblies

Glossary Item Box

This documentation article is a legacy resource describing the functionality of the deprecated OpenAccess Classic only. The contemporary documentation of Telerik OpenAccess ORM is available here.

If an upgraded version of Telerik OpenAccess ORM becomes available, you can install the new version and have all applications use the updated assembly. Please consider that the new version might introduce compatibility problems for certain applications when installing in the global assembly cache.

Updating Private Assemblies (Using XCopy)

If Telerik OpenAccess ORM assemblies are being deployed as a private assemblies, you can deploy the upgrade by just replacing the earlier version of the DLL in the application folder hierarchy with the new one. If the upgrade is done this way, the application needs to be instructed to load the new version of Telerik.OpenAccess.dll and Telerik.OpenAccess.Runtime.dll. To do so, include the content of OpenAccess ORM_PublisherPolicy.cfg and OpenAccess.Runtime_PublisherPolicy.cfg in the application configuration file. This redirects the assembly resolution to the current version of the respective assemblies. This has to be used if the application cannot or should not be recompiled.

Also you can recompile the application against the new Telerik OpenAccess ORM version and redeploy the whole application including Telerik OpenAccess ORM libraries as private assemblies.

You should keep a copy of the earlier version so that if you experience any compatibility issues with the new assembly, you can revert to the earlier version.

Updating Shared Assemblies (Using the Global Assembly Cache)

The easiest way to upgrade a Telerik OpenAccess ORM assembly in a shared configuration is to install the updated DLL in the global assembly cache. By default, the common language runtime tries to load the assembly that has the latest build and revision numbers, but the same major and minor version numbers, as the assembly the application was built with. Therefore, if the major and minor version numbers have not changed, adding the later version to the global assembly cache automatically updates all applications that refer to the Telerik OpenAccess ORM assemblies.

If you have installed Telerik OpenAccess ORM in the GAC, you can also update the application configuration file or alternatively use the provided policy assemblies and install these into the GAC. Telerik OpenAccess ORM comes pre-packed with publisher policy files to redirect assembly requests to the new version. You can find more details on using publisher policy files in MSDN.

Installing an Assembly in the Global Assembly Cache

You can use one of the following tools to install an assembly in the global assembly cache:

  • An installer program, such as the Microsoft Windows Installer version 2.0
  • The Global Assembly Cache tool command line utility (Gacutil.exe)
  • The .NET Framework Configuration tool (Mscorcfg.msc)

For more information about deploying .NET applications, see Deploying .NET Framework-based Applications on MSDN.

It is recommended that you include all of these assemblies—except the policy assemblies—directly with your application and not use the global assembly cache (GAC).

See Also