Dynamics4.NET FAQ: How do I maintain my objects, do I still use the OE Studio AppBuilder?

Back to FAQ index

Objects are maintained using the existing Progress Dynamics maintenance tools. Our number one development goal for Dynamics4.NET was to maintain compatibility with Progress Dynamics. In fact all visual repository classes (DynView.NET, DynBrow.NET, DynObjc.NET, DynFold.NET, DynTreeView.NET, ...) are defined as subclasses of the original ones in the repository and objects can be opened in the Container Builder or the AppBuilder for Viewers and Browsers. We ship template records so that a developer can simply create new .NET rendering objects from the AppBuilder. Migration can be done using the object type change utility of Dynamics or using copy-utilities that create a copy of a whole container in the repository and does the sub classing of all instances.

We have plans (without committing to a release date at all) to create migrated versions of the container builder and the viewer builder to please the developer with an up to date UI in his tools as well. For viewers this will enhance the WYSIWYG effect of the design. The container builder should simply be much more developer friendly by using a modern UI with dockable panes instead of the current multi window interface.