Starting with v17.1, we are improving how we generate the ribbon for the WPF Rich Text Editor with regard to where we source the images used. Although we shall be maintaining the current behavior alongside the new enhancements for v17.1, this backward compatibility will be removed in v17.2, causing a possible breaking change.
Currently the ribbon generation process uses images from two different sources: the
DevExpress.RichEdit.Core.dll assembly, as well as the WinForms Rich Text Editor (no, that is not a typo!). To put it mildly, this is not optimal. In v17.1, we have copied these images to the
DevExpress.Images.dll assembly as well, and the new ribbon generation code for the Rich Text Editor will source the images from there. However, this could cause a breaking change since we are referencing an assembly that you may not be deploying as part of your app.
Please note that the images are exactly the same, they are just provided in a different assembly.
Of course, this double collection of ribbon images could be a source of future bugs: we have to ensure any new or changed images are compiled into two completely different assembly sets. Indeed you could view this as a special kind of “code duplication”. Hence, in v17.2 we shall be removing these Rich Edit ribbon images from the Core assemblies, and from then on they will only be available from the Images assembly.
To avoid future problems, when you upgrade to v17.1, please ensure that the
DevExpress.Images.dll assembly is included in your build process.