Configuring Patch Assemblies

Patch for Essential Studio platforms

Syncfusion provides custom patches to customers to fix specific issues or defects they have encountered. These patches typically replace a few assemblies (DLLs) in the release version of Essential Studio. Make sure that the corresponding Essential Studio\Platform version installed on the machine before install the patches.

Let us consider version 11.4.0.26 as the base version for the following examples:

Patch Installation and Assemblies zip file 

Patches are available as a installer file that automatically copies the patched DLLs, and also makes the necessary changes. The changes done by the patch installer are as follows:

As an alternative, patched assemblies are also provided in a zip archive. You can use the zip archive and manually change your references to the new assemblies, if you do not want to install the patch installer on your development system. The following information will also help to apply the patched assemblies to your development system:

List of Assemblies

The list of assemblies that have been changed are listed along with the patch installer link provided by Syncfusion Support. 

For example, consider the following assembly has been changed in a patch: 

Syncfusion.Tools.Web.dll

Patch installer execution 

The following steps illustrate the Patch installer execution:

1. Back up a copy of the existing assemblies from the precompiledassemblies folder into the Backup Assemblies folder.

2. Place the patched assemblies in the Backup Assemblies folder, and then copy the patched assemblies into the precompiledassemblies folder. This folder is the master copy for all assemblies.

3. ​​Install the patched assemblies into the GAC, if the Run Assembly Manager check box is selected during installation.

4. Copy the patched assemblies into the Assemblies folder; the installation location under Essential Studio generated by the Assembly Manager.

What should I do after installing the Patch? 

If the Visual Studio projects have references to the assemblies from the GAC, no further action is needed. The patched assemblies have the same version information as the release assemblies, so your projects will pick the patched assemblies with no changes.

If the patched assemblies have the same version information, how can we ensure that the patched assemblies have been applied?

Patched assemblies have the same Product version number, but the File version number is similar to the Essential Studio release version number (except the revision part). It is higher than the release version of the revision number. The Date Modified attribute will also be different.