1. Home
  2. Forum
  3. WPF
  4. Upgraded Syncfusion WPF to a new version for a new control - big mistake

Upgraded Syncfusion WPF to a new version for a new control - big mistake

 I have been working on an app for the past two years and have had great success using Syncfusion controls in the program. Recently, I found the new Digital Gauge control and wanted to add that to my program. Big mistake.

I added the Digital Gauge control and syncfusion required updates to the latest and greatest of the entire library. Upgraded that, and now some of my existing controls are fine, but others, while the application still "works" have lost functionality that the application depends on.

I've narrowed it down to this:

MenuAdv and ComboBoxAdv cannot be rendered in my XAML anymore, but the program still runs (again, with reduced functionality that breaks the app).

Other controls, such as SfDataGrid and SfCircularProgressBar work just fine.

When I hover over my MenuAdv or ComboBoxAdv definitions in my XAML code, I get the following:

"Cannot located resource 'controls/navigator/themes/generic.xaml"

Now, SFDataGrid and SfCircularProgressBar I do not see in my list of nuget packages, but I do see them referenced explicitly in my solutionreferences. I know that MenuAdv and ComboBoxAdv come from Syncfusion.Shared.WPF in my nuget packages. Even though I installed from there, for some reason (I think) there's an issue with an assembly somewhere(?)

I downloaded the Syncfusion WPF extension to run the troubleshooter, but unfortunately each time I run it, a black window appears on my Visual Studio and then restarts Visual Studio 2019 and reloads my app.

Just a note, running Visual Studio 2019, target framework is .Net 4.6.1.

I admit I'm somewhat of a novice programmer for Windows - but I have written this various useful program that seems dead in the water for me right now.

Some of my code as it appears rendered:

menuadv.PNG

My code in the .XAML:

menuadvcode.PNG  


7 Replies
VR Vijayalakshmi Roopkumar Syncfusion Team July 20, 2021 11:01 AM UTC


Hi Craig


Thank you for contacting Syncfusion Support.


We have checked the reported case that you got error on hovering the control like ComboBoxAdv, MenuAdv with our simple sample, but we are unable to reproduce the reported error in latest v[19.2.0.48]. Please find the screenshot for the same below:




Sample: https://www.syncfusion.com/downloads/support/directtrac/general/ze/MenuAdv_seperator-420011720


However on observing the error "Cannot located resource 'controls/navigator/themes/generic.xaml". This usually occurs if the resource not present in solution or it occurs due to case sensitive or wrong order of definition in xaml. Please find the same in following MSDN link


Link: https://social.msdn.microsoft.com/Forums/vstudio/en-US/bbd83f09-ec9f-44b6-a405-3b603472f3bb/systemwindowsstaticresourceextension-threw-an-exception?forum=wpf


So we request you ensure whether the referred resource file generic has been properly referred in your application. Also we would like to ensure all assemblies are properly referred and of same version assemblies.


Also on deploying troubleshooter using syncfusion extension, it works correctly at our end.




We are unable to track why the visual studio get restarts at your end while troubleshooting. So kindly update us your visual studio version and windows version to check on it further. For more information about troubleshooting of assemblies, you can refer the following UG link:


Link: https://help.syncfusion.com/wpf/visual-studio-integration/visual-studio-extensions/troubleshooting


If you still faces the same error, please modify our sample to issue reproducible sample. Also confirm you currently using product version details. It would be helpful for us to check and analyze this case better further.


Please let us know if you have any other concerns.


Regards,

Vijayalakshmi VR


CR Craig replied to Vijayalakshmi Roopkumar July 20, 2021 02:30 PM UTC

First, thank you so much for taking a look at this for me. I can imagine how frustrating it must be to help someone without having the full code available to them.

Let me add a little more content to hopefully help you better (and I will certainly answer your questions).

This happened a few days ago when I decided to use the new Digital Gauge control. Because of it's simplicity, I decided to use nuget to add the new control, which then informed me of additional dependencies ("Syncfusion.Shared.WPF" needed to be updated, for example). Once I installed everything, immediately my Office2010Blue skin on my MenuItemAdv stopped working. I also noticed that I now require a licensing statement in my code. Ok, downloaded the license and added the line of code - licensing works. I looked at the documentation and saw that using skins now required Syncfusion.SfSkinManager.WPF and Syncfusion.Themes.Office2010Blue.WPF. Once I downloaded those, my simple Visual Style entry included in my MenuItemAdv showed an error. Ok, no big deal, it seems you've changed the way skins worked so I followed the documentation to add the references to SkSkinManager as seen here:



    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
    xmlns:syncfusionskin ="clr-namespace:Syncfusion.SfSkinManager;assembly=Syncfusion.SfSkinManager.WPF"
    xmlns:syncfusion="http://schemas.syncfusion.com/wpf" />

With this fix, I was able to get the skin to work on the entire window, but my MenuAdv and ComboBoxAdv were no longer rendered in my XAML. Panic starts to set in. I decide to abandon all skinning - let's get back to basics. I uninstall the packages for skinning entirely, SkinManager and the actual Office2010Blue.WPF skin. I then remove all references to the skin in my window XAML. Still, those two controls no longer render. I run my program and all seems ok, but I noticed some of my bindings no longer work because they update when my ComboBoxAdv updates and while the control is still there when the app runs, somehow it's behavior changed since I began this process.

Regarding your statement:

" However on observing the error "Cannot located resource 'controls/navigator/themes/generic.xaml". This usually occurs if the resource not present in solution or it occurs due to case sensitive or wrong order of definition in xaml. Please find the same in following MSDN link"

I looked at the link. But, my question is, how can the resource not be present in the solution when I've only installed the nuget packages from Syncfusion that are meant to support them? Shouldn't MenuAdv and ComboBoxAdv be included with the Syncfusion.Shared.WPF (19.2.0.48) nuget package? Do I need to do anything else to make them available in my app?

I have attached my entire MainWindow XAML.


Attachment: MainWindow.zip_d7260558.zip

I am using the following on my PC:

Microsoft Visual Studio Community 2019

Version 16.10.3

Microsoft .NET Framework

Version 4.8.04084


Syncfusion Reference Manager 17.1.0.30

A useful add-in for adding and migrating Syncfusion Assembly References for Windows Forms, WPF, and Silverlight projects.


Syncfusion WPF Project Templates 19.2.0.44

Provides Project Templates to add Syncfusion WPF Project along with corresponding configurations.


Syncfusion.VSExtension.Troubleshooter 19.2.0.44

Add-in for Troubleshooting the Syncfusion projects.


SyncfusionMenu Extension 1.0

SyncfusionMenu Visual Studio Extension Detailed Info




CR Craig July 20, 2021 03:52 PM UTC

Just an update.  I shutdown Visual Studio, relaunched, loaded my solution and re-ran the Syncfusion troubleshooter (and it worked this time).  It said my solution was missing a dependency - Syncfusion.SfDiagram.WPF.  I told it to backup before fixing (which I guess it did, though I saw no confirmation).

However, even after doing so I still see "Cannot create an instance of "MenuAdv" on my XAML rendering and the definition in my code itself is underlined with the "Cannot locate resource "controls/navigator/themes/generic.xaml." issue.

If I run the extension again, it says there are no configuration changes required for Syncfusion controls.


EM Elakkiya Muthukumarasamy Syncfusion Team July 21, 2021 12:07 PM UTC

Hi Craig, 
  
Thanks for your update. 
  
We are working on your reported query, and we will update you the further details on 22nd July 2021.We appreciate your patience until then. 
  
Regards, 
Elakkiya 


EM Elakkiya Muthukumarasamy Syncfusion Team July 22, 2021 03:37 PM UTC

Hi Craig, 

Thanks for your patience. 

On the further analysis we could found that the reported error “Shows an error on hovering the control like ComboBoxAdv, MenuAdv” not reproduced our end. If the reported error occurred only your project we suspect that this error occurred due to the namespace. So we request you to check the simple sample in your machine and update us the reported error occurred in your machine or not. Based on your update  we would like to arrange a web meeting with you to check the reported issue at your environment and analyze the exact cause of this error. So kindly share your availability to arrange web meeting with you . We will check the same and update it accordingly.   

Note: 
We need to create a incident to schedule a web meeting to check this issue. Based on your update we will create a incident for this. 

Please let us know if you have any other concerns. 

Regards, 
Elakkiya 


CR Craig July 22, 2021 03:44 PM UTC

Thank you.  I just tried your sample solution and it works fine for me.  Obviously then, it's something in my project.


I am on the east coast of the US.  I am available any time from 9am to 11pm.  Please let me know.


VR Vijayalakshmi Roopkumar Syncfusion Team July 23, 2021 10:20 AM UTC

 Hi Craig, 
 
We have created a new support incident under your direct-trac account for "To check why the controls are not rendcered properly in your environment". Please follow the created incident for further updates. 
 
Please let us know if you need any further assistance on this. 
 
Regards, 
Vijayalakshmi VR 
 


Loader.
Up arrow icon