We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy. (Last updated on: June 24, 2019).
Unfortunately, activation email could not send to your email. Please try again.
Syncfusion Feedback

Demo: System.NullReferenceException if started in Visual Studio, not if .exe started from folder

Thread ID:

Created:

Updated:

Platform:

Replies:

146908 Aug 25,2019 09:23 AM UTC Aug 26,2019 06:39 AM UTC WPF 1
loading
Tags: Ribbon
Alexander
Asked On August 25, 2019 10:07 AM UTC

Hello,

I have a problem with the Ribbon control. 

I've installed Essential Studio WPF 17.2.0.46 in 'C:\Program Files (x86)\Syncfusion\Essential Studio\WPF\17.2.0.46' on Windows 10.

If i start the demo project  of the ribbon control  in C:\Users\Public\Documents\Syncfusion\WPF\17.2.0.46\Tools.WPF\Samples\Ribbon\Office2016\CS\RibbonSample_2017.sln, i can compile the project in debug/release without any error. The program starts, but when i click on the "minimize/collapse ribbon" icon the program crashes.

Error:  System.NullReferenceException: "The object reference was not set to an object instance."

This does not happen if i start the same .exe in the debug folder directly without visual studio (C:\Users\Public\Documents\Syncfusion\WPF\17.2.0.46\Tools.WPF\Samples\Ribbon\Office2016\CS\bin\Debug\RibbonSample.exe

What am i doing wrong? I couldnt find any additional information on the help page.
I get the same behaviour if i set up a new project with the ribbon control and fallow the "getting started" in the help section

Thanks!



Attachment: ribbon_null_error_2f306d3c.zip

Jagadeesan Pichaimuthu [Syncfusion]
Replied On August 26, 2019 06:39 AM UTC

Hi Alexander, 
 
Thank you for contacting Syncfusion Support. 
    
It is a known issue related to VS 2017 debugger. The Visual Tree is refreshed at runtime after the Windows 10 fall creator update. Due to this we could not get the children of UIElement (RibbonTab) which causes problem with collection.  

Please refer the following link for the same,
  
    
   
    
Therefore, we suggest you to disable the “Enable UI Debugging Tools for Xaml” in the options of Debug tab of VS 2017 project (Debug (Tab) > Options > Debugging > General > (Uncheck) Enable UI Debugging Tools for Xaml).  
 
Please let us know if you need any further assistance on this.    
  
Regards, 
Jagadeesan 


CONFIRMATION

This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

Please sign in to access our forum

This page will automatically be redirected to the sign-in page in 10 seconds.

Warning Icon You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.Close Icon

Live Chat Icon For mobile
Live Chat Icon