Compatibility of Microsoft .NET Framework applications with different versions of the CICS® Transaction Gateway .NET API.
Client applications built using an earlier version of the CICS Transaction Gateway .NET API can connect to a V9.0 Gateway daemon by using the CICS Transaction Gateway .NET API assembly that they were compiled against.
To use the new CICS Transaction Gateway V9.0 .NET API assembly, client applications that were built using the CICS Transaction Gateway V8.0 .NET API and target Microsoft .NET Framework V4.0 must be recompiled. Client applications that target Microsoft .NET Framework V3.5 or were built using the CICS Transaction Gateway V8.1 .NET API can use the new CICS Transaction Gateway V9.0 .NET API by using assembly redirection; these applications do not require recompiling.
<configuration>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="IBM.CTG.Client"
publicKeyToken="4f7d883847d47abe"
culture="neutral" />
<bindingRedirect oldVersion="x.x.0.0-x.x.0.9" newVersion="9.0.0.0" />
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>
Replace "x.x" with the version
of the CICS Transaction Gateway
.NET API that the application was compiled against.If the CICS Transaction Gateway .NET API assembly is installed in the Global Assembly Cache (GAC), assembly redirection can be configured by installing the appropriate publisher policy file into the GAC. Policy files are provided in install_path/Windows/lib/policy in the ctgredist package or in install_path/lib/policy on a Windows machine with CICS Transaction Gateway installed. For more information on publisher policy and assembly redirection, see the Microsoft .NET Framework documentation.
For information on upgrading .NET applications from CICS Transaction Gateway V8.0, see CICS Transaction Gateway .NET applications.