Opening a form with a RibbonPanelMergeContainer causes an exception

[Jhonathan Aristizabal]

Good Afternoon.

From several time no I've been dealing with a poblem with VisualStudio and the Debugging of applications containing a RibbonPanelMergeContainer, the problem is that when I open a form containing a RibbonPanelMergeContainer on VisualStudio while debugging, it crashes the IDE. After some debugging of the problem, I've stablished that the problem ocurrs when trying to open a form on visual studio wich contains a RibbonPanelMergeContainer. The error is shown in the screenshot below. 

The steps to reproduce it are this

- Create a Winforms project on Visual Studiio 2019 (Happens on 2017 too).

- Create a Form

- Add the package Syncfusion.Tools.Windows v 17.1.0.38

- Add a RibbonPanelMergeContainer to the form, close the form designer and debug the program with F5

- Switch to VisualStudio and open the form designer

- An exception should be shown

[Sabaridass Ramamoorthy]

Hi Jhonathan, 

 

Thank you for contacting Syncfusion Support. 

 

We have checked the reported scenario- “Invalid operation exception in the designer of the Form with RibbonPanelMergeContainer in debugging mode” in our side. The reported problem is occurred only when we are trying to modify the designer page in compilation mode. We have confirmed the same is related to Visual Studio designer errors and it could not be handled in our RibbonPanelMergeContainer. In order to avoid these exceptions, you need to stop the debugging process before opening the designer page as per the suggestion available in MSDN. Kindly refer to the following link. 

 

https://docs.microsoft.com/en-us/visualstudio/data-tools/the-designer-cannot-be-modified-while-debugging?view=vs-2017  

 

Regards, 

Sabaridass R 

[Jhonathan Aristizabal]

Thank you for your response.

I think you misunderstood the problem, what I am trying to say is that the error also occurs while debugging an already open form with a RibbonPanelMergeContainer (Not while trying to modify a designer form), causing VisualStudio to crash and reopen, this issue is happening on a constant basis and causes we have to close all the form designer pages before debugging, which is not a normal scenario on the developing experience of VS.

After debugging the VS sesión it seems like the control triggers a modification on the designer while opening, so you can see the Asterisk on the file but no real modification was made to the file thus triggering this error while debugging.

Regards.

[Sabaridass Ramamoorthy]

Hi Jhonathan, 

Thanks for your detailed information. 

Now we are able to reproduce the reported issue – “Exception was thrown when opening a form with RibbonPanelMergeContainer” and have logged a defect report for the same. Here we are facing some issue with our feedback portal and so we will share the feedback link to track this issue on tomorrow.

The fix will be available in our upcoming Volume 1 SP1 release which is scheduled to be rolled out by mid of May 2019. Would waiting for the official release OK for you? Otherwise, we can provide a patch on April 25, 2019. 

Please let us know if you need any further details on this. 

 

Regards, 

Sabaridass R 

[Jhonathan Aristizabal]

I would gladly install a patch, thanks for your fast support Sabaridass.

Regards.

[Sabaridass Ramamoorthy]

Hi Jhonathan, 

 

Thanks for the confirmation. 

 

We will provide the patch for the reported issue – “Exception was thrown when opening a form with RibbonPanelMergeContainer” and it will be available on 25^th April, 2019. 

 

Regards, 

Sabaridass R 

[Jhonathan Aristizabal]

Hello, is there an ETA for the patch solving this problem?, I just checked the latest patch info and could not find reference to the solution of this bug.

Regards.

[Subburaj Pandian Veluchamy]

Hi Jhonathan 

  

We regret for the inconvenience caused. 

  

We are still working on this to resolve your reported issue, “Exception was thrown when opening a form with RibbonPanelMergeContainer”. We will fix the issue and update you the issue fix patch by May 13, 2019. We appreciate your patience until then.   

     

Regards,
Subburaj Pandian V  

[Sabaridass Ramamoorthy]

Hi Jhonathan,

We have fixed the reported issue “Opening a form with a RibbonPanelMergeContainer causes an exception”, and it can be downloaded from below location.

v17.1.0.38

Recommended approach – exe will perform automatic configuration

Please find the patch setup here:

http://syncfusion.com/Installs/support/patch/17.1.0.38/162277/I143829/SyncfusionPatch_17.1.0.38_162277_5132019075448262_I143829.exe

Advanced approach – use only if you have specific needs and can directly replace existing assemblies for your build environment

Please find the patch assemblies alone from:

http://syncfusion.com/Installs/support/patch/17.1.0.38/162277/I143829/SyncfusionPatch_17.1.0.38_162277_5132019075448262_I143829.zip

Assembly Version: 17.1.0.38
Installation Directions :
This patch should replace the files “Syncfusion.Calculate.Base” under the following folder.
$system drive:\ Files\Syncfusion\Essential Studio\$Version # \precompiledassemblies\$Version#\4.0
Eg : $system drive:\Program Files\Syncfusion\Essential Studio\17.1.0.38\precompiledassemblies\17.1.0.38\4.0

To automatically run the Assembly Manager, please check theRun assembly manager checkbox option while installing the patch. If this option is unchecked, the patch will replace the assemblies in precompiled assemblies’ folder only. Then, you will have to manually copy and paste them to the preferred location or you will have to run the Syncfusion Assembly Manager application (available from the Syncfusion Dashboard, installed as a shortcut in the Application menu) to re-install assemblies.

Note:
To change how you receive bug fixes, ask your license management portal admin to change your project’s patch delivery mode.

https://www.syncfusion.com/support/directtrac/patches

Disclaimer:
Please note that we have created this patch for version 17.1.0.38 specifically to resolve the following issue reported in the incident 143829. This fix will be included in our main release 2019 Volume2 which is expected on end of June 2019.

If you have received other patches for the same version for other products, please apply all patches in the order received.

Regards,

Sabaridass R