Issue ReportsTotal: 43363Active: 402Processed: 42961
SuggestionsTotal: 17801Active: 506Processed: 17295
QuestionsTotal: 98475Active: 106Processed: 98369
1851 Knowledge Base Articles
557 Code Central Examples
This website is powered by Developer Express ASP.NET technologies including the ASPxMenu, ASPxNavBar, ASPxTabControl, ASPxSiteMapControl, ASPxPopupControl and the ASPxGridView and Editors Suite. Database connectivity is via eXpressPersistent Objects.
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 when they are used in Visual Studio 2005 / 2008. 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, select its shortcut from the Start Menu\Programs\Developer Express .NET vX.Y\Tools menu, where X.Y corresponds to your DXperience version.
See Also: 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?
Do you have any comments? We are eager to hear them!