DevExpress for WPF does not work on other machines after using the skinning control

I use the cracked version of the DevExpress13.2.6. WPF's

After using the DevExpress control in the project, it didn't work on the other machines, scared me, and I found that the DLLs were copied locally. What is the reason for this?

The conjecture is that the DLL references other DLLs, or some DLLs need to be registered. But DLL so many, do not know which DLLs are bad, can not all get past it, so big. Later found some information asked the other people with this question, they all said poor Devexpress.utils.v13.2.dll. But in fact they are winfrom and WPF is not the same. It is not suitable at all.

Later I debugging, found that dxwindow out a problem. The rest is good, that is, quoting this and then using the skin will not run up.

Then this time is simple, is poor skin control, skin control altogether also about 20 about, and the skin of the basic control on one, haha.

The problem is solved: To reference Dxwindow, first refer to Devexpress.xpf.themes.dxstyle.v13.2.dll. Of course Devexpress.xpf.core.v13.2.dll this is a must. He will automatically refer to it.

You need to manually reference the Devexpress.xpf.themes.dxstyle.v13.2.dll, and then just look at what skin you need, and put which skin in the debug root directory. I'm quoting devexpress.xpf.themes.metropolislight.v13.2.dll this skin, I think this is the most beautiful. O (∩_∩) o haha ~

Show us The effect:

　　

Incidentally, how to change the skin of WPF, this Baidu a lot, but incidentally remember to avoid looking for:

Thememanager.applicationthemename = "Metropolislight";//Skin Name
This. UpdateLayout (); Re-layout

theme.themes;//Get all skin collections

Generally not necessary, after all, the skin of the DLL is so big, it is recommended to take a part of the skin good-looking DLL, remember their name is good.

There's time in the back. devexpress for WPF control usage, many online is Winfrom, WPF is too few. Want to enjoy a lot of communication with WPF.

　　

DevExpress for WPF does not work on other machines after using the skinning control