Documentation Center

Making custom .NET code work with the new RESTful APIs

If you perform a conservative upgrade, in which you continue to use the deprecated in-process .NET APIs, you will at some future point wish to migrate to .NET RESTful APIs. Your code that now talks to the in-process .NET APIs can talk to new RESTful .NET APIs without a recompile of your code, but some configuration is required to make this happen.

Procedure

  1. In your web application, open Web.config for editing.
  2. In the <assemblyBinding> section, add the following subsection:
    <dependentAssembly>
      <assemblyIdentity name="Tridion.ContentDelivery.AmbientData" publicKeyToken="ddfc895746e5ee6b" culture="neutral" />
      <bindingRedirect oldVersion="0.0.0.0-7.2.0.0" newVersion="VERSION" />
    </dependentAssembly>
    <dependentAssembly>
      <assemblyIdentity name="Tridion.ContentDelivery" publicKeyToken="ddfc895746e5ee6b" culture="neutral" />
      <bindingRedirect oldVersion="0.0.0.0-7.2.0.0" newVersion="VERSION" />
    </dependentAssembly>

    where VERSION is the version of this assembly, as found by right-clicking the file, selecting Properties, selecting the Details tab in the dialog that opens, and checking the File version property. To make sure you are looking at the right file, also click the File description property, which must mention "(CIS)", that is, Content Interaction Services or microservices.

  3. Save and close Web.config and restart your web application to apply the changes you made.