Input Controls not displaying on 'some' PCs

[Richard]

Hi, I have a weird issue. I’m deploying a wpf app via clickonce and have it installed on several PCs.
On one of the PC’s the Telerik input controls don’t display. It works on all the other PC’s and it’s only controls like date/num pickers & dropdowns not working. Telerik based grid views, tabs etc all work fine on all PCs.
I have attached a screenshot from the same install on two different PC’s to demo the issue.

Have you any idea why this might be and what I can check? 

Thanks,

Richard

[Dilyan Traykov]

Hi Richard,

Thank you for the provided image.

Please have a look at the following article which lists a few common reasons and troubleshooting steps for controls being missing from the UI.

In addition to the information you provided, can you please further clarify whether you're using the implicit styles approach for theming the controls with the NoXaml binaries?

If that is the case, possible reasons for this result include the following:

• Telerik.Windows.Controls.Input.xaml dictionary is not merged in the application's MergedDictionaries collection;
• Custom styles targeting the specified controls do not include the BasedOn attribute
  

If none of these are the reason and you're not using the NoXaml binaries, I cannot be certain about the cause of this undesired appearance without being able to replicate the issue at my end. Would you find it possible to share the click once application so that I can investigate it?

In addition, please specify any details of the machine which exhibits the issue which you find relevant. Does it have an installation of the Telerik UI for WPF suite on it?

Thank you in advance for your cooperation on the matter. I will be awaiting your reply.

Regards,
Dilyan Traykov
Progress Telerik

[Richard]

Hi Dilyan,

Thank you for that detailed reply. I’m not using the NoXmal binaries in the App, but that did jog my memory that I tried them out in the past.

To test I created a new user on the broken PC and the App worked perfectly under that account. So I checked for  Telerik.Windows.Controls.Input.dll in the folder:
C:\Users\username\AppData\Local\Apps\2.0\{RandomString}
… and you were right, the NoXmal dll was in the broken User Profile while the full binaries dll was installed to the working AppData folder.

I’m guessing that I had tested the NoXmal version in the pass and even though I had uninstalled the App it had left the NoXmal dll behind. When I installed the new version of the App with the full binaries both dlls were the same version (2020.2.617.45) and the old NoXmal was not replaced.

Thanks,
Richard

[Dilyan Traykov]

Hi Richard,

I'm glad to hear that we've come across the cause of the issue.

I cannot, however, determine why the old NoXaml assembly was not removed or replaced afterward. I believe this should be handled by the ClickOnce installer. A similar issue has been discussed in this StackOverflow thread.

Nonetheless, can you please specify whether manually deleting the old file is possible and whether it solves the issue on the problematic PC?

Regards,
Dilyan Traykov
Progress Telerik

[Richard]

Hi Dilyan,

Manually deleting the file is possible, it lives in the user profile so a normal user has full access to it. Unfortunately once I fixed it I could not recreate the issue to investigate further. 

This is my dev PC so it has a lot of install / uninstalls happening all the time, it's possible the dll got left behind on one of those uninstalls. This is wild speculation but the Xmal and NoXaml dlls are the same version but the NoXaml is has a date modified of 20min 'newer' .

Maybe when the App does looking for the dll to use and finds two dlls of the same version but different sizes it picks the 'newer' date modified. Again, that's just speculation, I can't recreate to test that theory. 

 

PS. We met at Ignite in London two years ago when I gave you a demo of out Silverlight software. 

 

Thanks,

Richard

[Dilyan Traykov]

Hi Richard,

I can also only guess as to why the NoXaml version of the dll is being used in this case, but your theory about its modified date seems reasonable. If you do come across this issue again, we can further investigate the exact cause for this.

PS: I'm happy to see you've recognized me. I was really impressed by the MigrationStudio and AppTracker solutions you've built. I do hope you find the migration from Silverlight to Web and WPF easy, but as always, we're here to support you should you come across any issues along the way.

Regards,
Dilyan Traykov
Progress Telerik