In the XAF - Eliminating the number of Conditional “Something” (coming in v2011 vol1) blog post you suggested using the ConditionalAppearance module instead of the old ConditionalFormatting and ConditonalEditorState modules.
Starting with 11.2,** these modules are marked obsolete:*** http://www.devexpress.com/Support/WhatsNew/DXperience/files/11.2.5.bc.xml#BC1377
How do I migrate* my old customization rules to Appearance** rules provided by the ConditionalAppearance module?
To migrate some of your ConditionalFormatting and ConditinalEditorState rules to Appearance rules provided by the ConditionalAppearance module, you can use the converter we implemented.
The converter processes your code and looks for ConditionalEditorState rules applied to your business classes, as well as the ConditionalEditorState and ConditionalFormatting rules declared in the application model and then creates Appearance rules in the application model based on them. Take special note that ConditionalEditorState rules applied to methods are not processed by this converter, and you will need to convert them manually.
The main purpose of this converter is to simplify the migration to Appearance rules. It covers only common scenarios of use and may not work under certain ones.
To use the converter, execute the following steps:
1. Download the How to migrate ConditionalFormatting and ConditinalEditorState rules to Appearance rules provided by the ConditionalAppearance module (Example) example (it can also be used for testing) and copy the files from its Updater folder into your platform agnostic module or any other module where the ConditionalEditorState and ConditionalFormatting rules are declared.
Note that some model extensions need to be registered in your module (see the Registration.xx source file) for the correct operation of the converter.
2. Remove the ConditionalEditorState and ConditionalFormatting module via the Module Designer.
To do this, your project should use version 11.2 or less of our products. It is also important to still keep references to these modules in your project.
3. Add the ConditionalAppearance module via the Module Designer of your module project.
4. Build the module project and then execute the Update Model command from the project's context menu in the Solution Explorer.
As a result, Appearance rules will be added to the application model of your module.
5. Manually inspect your code and application model and convert the remaining ConditionalEditorState rules applied to methods (if any).
6. Remove or comment out the unnecessary ConditionalEditorState rules (you can simply replace them by Appearance rules) from your code and remove references to the ConditionalEditorState and ConditionalFormatting modules completely from your project.
Show all comments