Upgrading support softwares to Aptify 6.2

This topic contains links to the sub-topics that describe how to upgrade support software to Aptify 6.2:

Upgrading a Classic e-Business Site With 6.2 Changes

If you want to upgrade your classic e-Business site with the Aptify 6.2 updates (Telerik Upgrade and .Net 4.8 Framework upgrade), the main items to address are the site's bin directory contents and new entries in the web.config. 

Obtaining the site's bin directory contents

Aptify has made downloading the bin directory for a product easier by updating the Sync Repository Object records for the e-Business application.  This record can be referenced by the Object Repository Synchronizer tool to dump the entire contents of the sync record.  An example is shown below.

Here we are downloading the contents of the sync record to a temporary folder location. By default, the sync record will only contain stock assemblies necessary for the site. Custom assemblies may be required and missing from this record. For example, if you have a custom entity plugin on Persons and have not added it to this sync record, it will not be included in the sync output.

Best Practice

Aptify recommends adding your configured assemblies to the sync records for your applications so they can be included when using the OR Sync tool against a Sync record.  If your configured assemblies are needed by all top-level applications, you can put them in their own sync record, and then add that sync record to the Related Syncs subtype for the top-level sync record in question.  Related syncs will automatically be included during syncing provided the 'Include Related Syncs' checkbox is checked (as shown).  Include Related Syncs was a featured added to the OR Sync tool starting in version  

Once you have the sync contents you should diff those contents against the bin directory of the site you want to upgrade. This gets you familiar with what files are changing, what files are new, and what orphan files might exist in your current site that are not in the sync record today. If there are orphan files in the site and you know they are for your configurations, you could add them to the sync record at this time, so they exist going forward. If there are orphan files in the site that you do not recognize, you might want to exclude them going forward until you understand what their purpose is. They may be unnecessary for your site to function. Once you are comfortable with the sync contents merge them into the bin directory.

Typically, files with the extensions lic, xml and txt in the diff can be ignored.  

Assemblies That Can Be Deleted

The following assemblies are no longer needed for classic e-Business and can be deleted from the bin directory. They will not be present when syncing the OR sync record from classic.  

  • Telerik.Windows.Controls.dll
  • Telerik.Windows.Data.dll
  • Telerik.Windows.Documents.dll
  • Telerik.Windows.Documents.FormatProviders.Html.dll
  • Telerik.Windows.Documents.FormatProviders.OpenXml.dll
  • Telerik.Windows.Documents.FormatProviders.Rtf.dll

Assemblies That Need to be Added

The following assemblies are additional assemblies that are needed for classic e-Business Telerik Upgrade and need to be downloaded from Telerik Site and added in the bin directory. 

  • Kendo.Mvc.dll
  • Kendo.Mvc
  • Telerik.Documents.Core.dll
  • Telerik.Documents.Fixed.dll
  • Telerik.Documents.SpreadsheetStreaming.dll
  • Telerik.Documents.SpreadsheetStreaming
  • Telerik.Web.Design.dll
  • Telerik.Web.Device.Detection.dll
  • Telerik.Web.Device.Detection
  • Telerik.Web.PDF.dll
  • Telerik.Web.Spreadsheet.dll
  • Telerik.Web.Spreadsheet
  • Telerik.Web.UI.dll
  • Telerik.Web.UI.Skins.dll
  • Telerik.Web.UI
  • Telerik.Windows.Documents.Core.dll
  • Telerik.Windows.Documents.Core
  • Telerik.Windows.Documents.Fixed.dll
  • Telerik.Windows.Documents.Fixed
  • Telerik.Windows.Documents.Flow.dll
  • Telerik.Windows.Documents.Flow.FormatProviders.Pdf.dll
  • Telerik.Windows.Documents.Flow.FormatProviders.Pdf
  • Telerik.Windows.Documents.Flow
  • Telerik.Windows.Documents.Spreadsheet.dll
  • Telerik.Windows.Documents.Spreadsheet.FormatProviders.OpenXml.dll
  • Telerik.Windows.Documents.Spreadsheet.FormatProviders.OpenXml
  • Telerik.Windows.Documents.Spreadsheet.FormatProviders.Pdf.dll
  • Telerik.Windows.Documents.Spreadsheet.FormatProviders.Pdf
  • Telerik.Windows.Documents.Spreadsheet
  • Telerik.Windows.Zip.dll
  • Telerik.Windows.Zip.Extensions.dll
  • Telerik.Windows.Zip.Extensions
  • Telerik.Windows.Zip
  • Telerik.Zip.dll

Updating web.config

New required entries in the application config file must be manually added to web.config for existing sites. There are two common types of entries to account for with every version upgrade:  new appSettings entries and new binding redirects. These entries are documented in the general release notes for the core upgrade, as they typically apply to all products that are being upgraded. If you are upgrading your site from more than one version of Aptify, you will need to consult the documentation for those releases to understand all entries that potentially need to be added. 

  1. Whether you have done an OR sync on your e-Business bin or not, you should change the .NET framework to 4.8. Search for "targetFramework" in the web.config and update it to target .NET 4.8, like this: <compilation debug="true" targetFramework="4.8">
  2. Update the web config to update the binding redirect to the 2020 version:

    Web Config
        <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
            <assemblyIdentity name="Telerik.Web.UI" publicKeyToken="121FAE78165BA3D4" culture="neutral" />
            <bindingRedirect oldVersion="2015.2.623.40" newVersion="2020.2.617.45" />
  3. Add this key: <add key="ValidationSettings:UnobtrusiveValidationMode" value="None" />
  4. Save and close your web.config.


Now that your web.config and bin directory are updated you must test the site. 

Missing Assemblies

The most common error you will encounter during testing is a missing assembly in your bin directory. The error message will indicate what assembly is missing. If it is an Aptify assembly please let support know about this error.  Regardless of whose assembly it is, putting it in the bin directory will resolve the error. You should also update the Sync record to include it going forward.  

Missing Binding Redirects

Another common error is around required binding redirects, so make sure to Read our release notes on the topic here.


Pop-Ups not displaying correctly.:

Another common error observed is popup dialogs getting distorted and UI disturbed due to the same.  Perform the following changes for the same.

  1. Locate your eBusiness css style sheet (eBusinessStyles.css ) in the e-Business installed path. The name of the css style sheet might be different in your installed path
  2. Open the file and add below CSS changes at the end of file:

    CSS changes
    .rwWindowContent > div {
        width: inherit !important;
        height: inherit !important;
    .RadWindow .rwIcon{
        margin-top: 8px !important;
        top: 0 !important;
    .RadWindow .rwTable {
        height: 100% !important;
    height:auto !important;
  3. Locate the data_from.css file in the e-Business installed path. (Folder path for Non CMS <eBusiness installed path\App_Themes\Aptify\)
    Open the file and update Line Number  3067  and the following add width details:


    height: 589px !important;

    width: 478px !important;


  4. Save and close the file.
  5. Restart the IIS. 

Upgrading the App Server with 6.2

Steps to upgrade an application server with 6.2 are fairly minimal.  The Sync Repository Objects record for the Desktop application can be used with the Object Repository Sync tool to generate the stock list of assemblies needed.  Assemblies needed for your configurations will only be included if you have previously added them to this Sync record.  In general, it is best to diff the contents of the sync with your app server directory.  Anything in the sync download should be replaced.  Anything orphaned on the app server are likely configurations should be updated with their latest versions compiled against the 6.2 assemblies.  Finally, add the required binding redirects and new appsetting entries to the AptifyAsyncProcessor.exe.config file as appropriate for your system. 

AptifyAsyncProcessor config file and AptifyCreateProcessFlowRun config file needs to be updated to mention the new version “” for Newtonsoft.Json assembly.

Please set a new key in AptifyAsyncProcessor.exe.config  and AptifyCreateProcessFlowRun.exe.config  to set the value of ‘’EnableCaptureViewStatistics’’ Attribute to true.


Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.