Impact on Content Delivery custom code
Whether you are performing a minimal upgrade to SDL Web 8.5 Content Delivery or doing an actual migration to the new RESTful, service-based setup, changes to your Content Delivery custom code may be necessary.
- Impact on custom code that interacts directly with the Storage Layer
If you perform a minimal upgrade only, any custom client code that interacts directly with the Storage Layer continues to work normally. But in the new RESTful, service-based setup, your clients can no longer interact directly with the Storage Layer. They instead need to interact with the microservices, who in turn talk to the Storage Layer. Consult the API references for the new Content Delivery APIs to find out more. - 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. - Making custom code work with new Content Delivery .NET assemblies
If you created custom code that interacts with (parts of) Content Delivery running as a .NET Web application, then in order to work with Content Delivery v8.5, your custom code requires policy files that resolve DLL versioning conflicts. Copy these policy files (and the new Content Delivery DLLs) to your Windows assembly on the machine that runs your custom code. - Making custom code work with the new Content Service
As of SDL Tridion 2013, theComponentPresentationentity returned by the Content Delivery Web service (now the Content Service) contains a new property calledEncoding. Only if you are upgrading from 2011 SP1 HR2, make changes to your custom code.