How to fix wrong icon in material design extension?

[VahidEra]

Hi guys,
I am using material design in xaml toolkit in my wpf project. And I also use material design extension, which is based on material design in xaml toolkit.
But there is a problem here, and this problem is that the icons in the material design extension are displayed incorrectly, like this:

the icons should be like this:

Of course, I must say that my project is based on .Net Framework 4.8, but the material design extension is compiled based on .NET Core 3.1 and .NET Framework 4.5.2. Is this the problem and if so how do I fix it?

Keep in mind that I changed the framework of my project to 4.5, but I ran into problems

[nicolaihenriksen]

@VahidEra This is a known/expected issue. See #3159 and #3125. The issue you're facing seems to be the exact problem of the latter. In short, there is a version mismatch.

[VahidEra]

Dear Nicolai, first thank you very much to helping me.
According to your guidance #3125 (comment), the only way to solve this problem is to use the Material Design version, according to which the Material Design Extension is compiled right?
In this case, how can I downgrade the material design of my project to a lower version?

[nicolaihenriksen]

@VahidEra well you could just use the Nuget Package Manager in Visual Studio to downgrade, or directly change it in your *.csproj manually.

However, beware that you will miss out on all new features and big fixes added after that version. So this is not ideal.

A better approach would be to get a new version of the Extension library which is compiled against a recent (preferably latest) version of MDIX. That, however, is up to the author of that library. This is an unfortunate side-effect when icons are directly referenced in code (not XAML). There are workarounds to this which I mentioned in the linked issue, but again that will require changes in the Extensions library.

[VahidEra]

@nicolaihenriksen Yes, I got it. You are exactly right, because after changing the material design version, my project faced many problems. So I prefer not to use material design extension at all. Do you have a suggestion for a custom open directory?

[nicolaihenriksen]

@VahidEra Well, there are a few libraries out there to pick from I guess. Alternatively roll your own.

Another option is to fork the Material Design Extension library and build your own version of it?
I have a suspicion that you only need to change the FileSysteminfoIconConverter.cs class to load the PackIconKinds by reflection (as done in my comment here). I guess you could also consider creating a PR for the library with this change. It can/will have a small performance impact, but probably nothing noticeable for most use cases.

[VahidEra]

@nicolaihenriksen Dear Nicolai, thanks a million for your advice. You are the best and the best never rest.