You define what is accepted in a check-in when you set up the version control system. Quality checksīefore the version control system accepts a check-in, it might subject the elements to quality checks. Renaming an element deletes the element with the old name and adds an element with the new name. After you create the element, you must check it in.Īn element that is checked in can be renamed. First, give it a proper name in accordance with naming conventions, and then click Add To Version Control on the context menu. Because elements are stored for each layer in the version control system, customizing an element effectively creates a new element.Īfter you create an element, you must add it to the version control system. Customize an existing element, resulting in an overlayered version of the element.When a developer communicates with the version control server, the.
#Morphx boxart software#
In contrast, Visual SourceSafe and TFS are designed for large projects in which many developers work together on the same project for an extended period of time (for example, an independent software vendor building a vertical solution).įigure 2-32 shows a typical deployment using Visual SourceSafe or TFS, in which each developer locally hosts the AOS and the database. For example, MorphX VCS does not provide any tools for maintenance, such as making backups, archiving, or labeling. Although MorphX VCS provides many of the same capabilities as a version control server, it has some limitations. With just a few clicks, you can enable MorphX VCS to persist the changes in the business database.
In these situations, the benefits of having a change history are enormous. In such setups, each developer often works simultaneously on several projects, toggling between projects and returning to past projects. There are no additional infrastructure requirements when you use MorphX VCS, which makes it a perfect fit for partners running many parallel projects. The file format used is the standard Microsoft Dynamics AX export format (.xpo). The elements persisted on the version control server are file representations of the elements in the AOT. TABLE 2-8 Overview of version control systems.Ĭhange list support (atomic check-in of a set of files) Table 2-8 shows a side-by-side comparison of the version control system options. MorphX Version Control System (VCS) is designed for smaller development projects that previously couldn’t justify the additional overhead that using a version control system server adds to the process. AX 2012 supports three version control systems: Visual SourceSafe 6.0 and TFS, which are designed for large development projects, and MorphX VCS. Developers are also unaffected by any downtime of a centralized development server.Įven though using a version control system is optional, it is strongly recommended that you consider one for any development project. A developer can rewrite fundamental areas of the system without causing instability issues for others. When modifications are ready, they can be checked in and made available to consumers of the build.
Isolated development Each developer can have a local installation and make all modifications locally.If a change doesn’t meet the criteria, it is rejected. With the quality standard, all changes are verified according to coding practices.
#Morphx boxart code#
Code quality enforcement The implementation of version control in AX 2012 enables a fully configurable quality standard for all check-ins.Revision history of all elements All changes are captured, along with a description of the change, making it possible to consult the change history and retrieve old versions of an element.Using a version control system offers several benefits: The tool is accessible from several places: from the Version Control menu in the Development Workspace, from toolbars in the AOT and the X++ code editor, and from the context menu on elements in the AOT. Microsoft Dynamics AX can integrate with VSS, TFS, and MorphX VCS, but you can extend the version control functionality to use other version control systems.The Version Control tool in MorphX makes it possible to use a version control system, such as Microsoft Visual SourceSafe or Visual Studio Team Foundation Server (TFS), to keep track of changes to elements in the AOT. Otherwise, versioning history may be lost.
Because versioning history is stored in the business database when you use MorphX VCS, you should back up the business database before you perform tasks that could lead to restoring the business database.
0 kommentar(er)
