In Visual Studio 2005, the Developer Express controls appear as read-only on inherited forms. Is there a way to make them editable and use visual inheritance as in the previous versions of Visual Studio?
We have found a way to enable visual inheritance in our controls. We have tested this solution in all the typical visual inheritance scenarios and haven't noticed any failures yet. But we cannot be completely sure that we have chosen the correct approach and thus we don't enable visual inheritance by default. What causes this doubt is that Microsoft disabled visual inheritance for its controls.
There is a DXDesignKeys tool shipped with the DXperience suite. It adds a new key to the registry and is capable of changing its state. When this key is present and enabled, Developer Express controls allow visual inheritance. If it is not present or disabled, visual inheritance is prohibited just as with standard controls (this is the default behavior). To launch the program, find it here: "C:\Program Files (x86)\DevExpress X.Y\Components\Tools\Components\DXDesignKeys.exe" , where X and Y correspond to your DXperience version. Make sure to close Visual Studio prior to using the DXDesignKeys tool.
You can also invoke this tool by using the DexExpress menu in Visual Studio as shown in the attached screenshot:
There is a limitation in the Visual Inheritance mechanism: item collections must not be modified on inherited Forms/UserControls.
We recommend that you modify collection properties (for example, tab pages, bar items, grid columns) at runtime to avoid possible problems. Please refer to the following article for additional information:
Visual inheritance support for complex controls
The use of XPO and server mode data source components on visually inherited controls
Can I use the grid on an inherited form or user control?
Troubleshooting design-time problems
What is the best way to set the same Look-and-Feel style of the entire application with DXperience for Windows Forms?