Deploying DLLs built from modified source code

Question

I have experimented with changing source code for a control (SfRichTextBoxAdv) and tested my changes in the test project. I find the Build Manager makes the process fairly easy, and my tests worked fine. However, I am not sure what would be the best way to deploy my changed control to our product. As I understand it, versions of DLLs that I build are not compatible with DLLs released by Syncfusion because they are built with a different strong key file. Therefore, I cannot simply replace the one DLL affected by my changes (since it depends on common Syncfusion DLLs). It seems I would have to build and replace all Syncfusion DLLs with versions I built in order deploy my changes to the single DLL. Is this correct? What are my other options for deploying my changes? I thought of renaming the set of DLLs that the control I changed depends on, but am guessing this would cause problems with the Build Manager.

Manivannan Sundararajan · Answer

Hi Peter,Thanks for contacting Syncfusion support.Yes, you are correct. Syncfusion assemblies are compiled using the Strong key. Also, you can’t deploy single assembly as there are dependent sources which needs to be compiled with same strong key. For your case you can use the Build Manager to compile all assemblies. While building the Syncfusion sources from Build Manager (with or without strong key), all the dependent sources will also be compiled and the assemblies will be placed in the below location.Location:{ProgramFilesFolder}\Syncfusion\Essential Studio\{version}\UserAssembliesExample:C:\Program Files (x86)\Syncfusion\Essential Studio\16.1.0.37\UserAssembliesFor example, if you compile the SfRichTextBoxAdv source from Build Manager, all the dependent sources will also be compiled. So, you can use the assemblies from the above UserAssemblies location and replace them in the location from where the references to your projects were placed. Regards,Manivannan S.