Current filter:
                                You should refresh the page.
                                  • Description:
                                    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:***
                                    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
                                • Felipe R Machado 07.05.2012

                                  This is unfortunately not a very good advice. An article depicting samples and guidelines would have been much more informative. The biggest issue is that we didn't use this converter and now with 12.1.4 it won't work anymore. I don't want to restore the old version only to use the converter, I want to KNOW how to do that manually. It don't seem a big deal, but it would have been better with documentation to back it up instead of "use this converter tool" advice :-)...

                                • Dennis (DevExpress) 07.06.2012

                                  Thank you for the feedback, Felipe. I am afraid we do not have other migration guidelines for the case when you upgrade to 12.1 first. Moreover, this is not recommended.
                                  However, if you do not want to use the converter, you can write code that will create required XML for appearance rules based on old definitions in the application model or code. We do not have ready examples for this, though, and I recommend you use the suggested approach as it seems to be easier.

                                • Konstantinos Chionas 08.26.2012

                                  Thanks Dennis
                                          steel I have problem that I cannot do step 2 because already system showing error on your example.

                                • Dennis (DevExpress) 08.26.2012

                                  @Chionas: I have updated the 2nd point accordingly. Please let me know if this helps.

                                • A.B. Data Class Action 09.10.2012

                                  How about a video tutorial? Or more detailed instructions. I'm afraid we're awfully confused on ambiguous instructions, particularly in steps 1,2 and 3.

                                • Anatol (DevExpress Support) 09.11.2012

                                  Though we do not have a video tutorial, I believe we can easily sort out this ambiguity. Would you please describe the things that are unclear to you in greater detail. I will do my best to give you additional instructions on how to achieve the required goal.

                                0 Solutions

                                Creation Date Importance Sort by