If you became a customer of the Syncfusion Reporting Platform or the Report Viewer, Report Designer, or Report Writer components before October 2019 and have questions related to those products, you can request support through our forum system. However, please note that this support system is only for existing customers who are still using the Syncfusion Reporting Platform or its components and not for new customers looking for reporting products from Syncfusion.
For new customers or those with general reporting questions, we recommend contacting our support team at https://support.boldreports.com/, which is a separate brand created by Syncfusion for its reporting solutions. Our team will be happy to assist you with any questions you may have.
Thank you for choosing Syncfusion for your reporting needs.
I have obtained the license for the community of SyncFusion and I have two problems: 1) The SyncFusion controls separator disappears before starting Visual Studio 2017 Pro. 2) I can not use RibbonControlAdv because it displays an error message like the following:
Error al generar el código para la propiedad '<nombreDePropiedad>'
KJKeerthana Jegannathan Syncfusion Team July 27, 2017 10:10 AM UTC
Thank you for contacting Syncfusion support.
Query 1: The SyncFusion controls separator disappears before starting Visual Studio 2017 Pro.
We were not able to understand your problem with your previous update. Can you please share whether you are facing issue while using controls from the Toolbox? If possible, can you share the video/screenshot which replicates the issue? It will help us to resolve your problem at earliest.
Query 2: I cannot use RibbonControlAdv because it displays an error message like the following: Error al generar el código para la propiedad '<nombreDePropiedad>
We have checked the reported behavior of RibbonControlAdv by drag and drop into the form from Toolbox in 18.104.22.168 version and we were unable to reproduce the reported error from our side. So, can you please share the below details
1)Essential Studio version which you are currently using.
2)OS in which the application runs.
Also, if possible please provide simple sample which replicates the issue?