Purpose of TFS and MorphX VCS


What is the use of TFS(Team Foundation Serever) And Morphx VCS functionality in ax. Can any one explain

Both are version control systems - their primary purpose is safely store all version of code and metadata, with additional information about when changes were done, by whom, developers can provide comments explaining reason of changes and so on. Therefore you’ll never lose any code, you can revert to any previous version if needed, you can identify why a certain change was done, how did it, you can identify all changes done in a certain period (e.g. to generate release notes) and so on and so on. It’s absolutely crucial tool for any development. I personally use TFS (or more precisely VSTS) to store important documents as well, such as PPTs for lectures.

MorphX is a very simple tool with many limitations, which TFS/VSTS is a very robust, mature version control system with many additional features. MorhphX VCS stores data directly in the AX database, so you can’t use it across several environments and you must be careful when backing up restoring the database. TFS uses it’s own database, so you can store data from several AX environments there and even if all your AX environment gets completely destroyed, all you code is intact in TFS. TFS also offers changesets, so you can work with a single change (including several changed objects) as a single unit, concurrent development (several developers can work on the same object at the same time), work item tracking (you can plan and track your project in TFS, code can be linked to requirements), code branches (you can develop several versions in parallel and track which changes have been promoted to which branches), you can easily get any version of your application (MorphX can’t do that), you can use it for automated builds, you can configure security and much more.

Thanks for reply…

is CheckIn CheckOut functionality same for both Morphx VCS and TFS

Both use common version control operations such including CheckIn and CheckOut (and Add, Delete etc.), but they obviously do technically different things for different systems.
Don’t forget about the other operations. For example, if you delete an object just from your DEV environment but not from TFS, it will still be available to other developers, it will be included in builds and so on.