To set up the MorphX Version Control System (VCS) in AX simply press the
Microsoft Dynamics AX button (Alt + M) and navigate to Tools | Development tools | Version Control | Setup | Parameters.
First of all,you have to select Enable in the Source control status. Then, you need to select the version control type that you would like to use. The main reason for this is that it doesn't require each developer to have a full AX installation locally like the Visual Source Safe and Team Foundation Server do.
If you are creating a new module for AX, or if you are already using Team Foundation Server, then selecting Team Foundation Server as version control for AX might be a better option.
When using the MorphX VCS, the repository is actually inside the AX database, so you will always have an access to it as long as you are logged on to your AX solution.
You can also select to have the AOT elements color coded depending on the VCS status and to receive a warning when reverting objects
After setting these parameters, you can choose to create a repository by pressing the Microsoft Dynamics AX button (Alt + M) and navigate to Tools | Development tools | Version Control | Setup | Create repository.
This will basically check in all elements in the AOT with a shared comment at that point of time. If you have a new solution without any modifications to standard AX, this is not needed, as you always have the possibility to go back to the original version in the system layers.
You can also set some rules as to what should be allowed and denied when trying to check in an element into the VCS by pressing the Microsoft Dynamics AX button (Alt + M) and navigating to Tools | Development tools | Version Control | Setup | System settings
Microsoft Dynamics AX button (Alt + M) and navigate to Tools | Development tools | Version Control | Setup | Parameters.
First of all,you have to select Enable in the Source control status. Then, you need to select the version control type that you would like to use. The main reason for this is that it doesn't require each developer to have a full AX installation locally like the Visual Source Safe and Team Foundation Server do.
If you are creating a new module for AX, or if you are already using Team Foundation Server, then selecting Team Foundation Server as version control for AX might be a better option.
When using the MorphX VCS, the repository is actually inside the AX database, so you will always have an access to it as long as you are logged on to your AX solution.
You can also select to have the AOT elements color coded depending on the VCS status and to receive a warning when reverting objects
After setting these parameters, you can choose to create a repository by pressing the Microsoft Dynamics AX button (Alt + M) and navigate to Tools | Development tools | Version Control | Setup | Create repository.
This will basically check in all elements in the AOT with a shared comment at that point of time. If you have a new solution without any modifications to standard AX, this is not needed, as you always have the possibility to go back to the original version in the system layers.
You can also set some rules as to what should be allowed and denied when trying to check in an element into the VCS by pressing the Microsoft Dynamics AX button (Alt + M) and navigating to Tools | Development tools | Version Control | Setup | System settings
No comments:
Post a Comment