Microsoft Dynamics AX 2009 White Paper: Integrating a Third Party Version Control System into Microsoft Dynamics AX 2009

A new white paper has been published on how to intergrate a third party version control system with AX2009. The white paper is a case study of the steps the MorphX team had to go through in order to integrate Team Foundation Server (TFS) into AX2009.  

The white paper is available for download at these locations:

Microsoft Download Center:



Comments (6)

  1. mfp says:

    The version control integration in AX that we are investing mostly in is TFS.  And that is orthogonal to the discussion of which IDE.  TFS is Microsoft’s bet on VCS, Bug tracking, etc, and VS is Microsoft’s bet on the development environment.   AX is heading towards both.

  2. Waldemar Pross says:

    Well, Strider, in some kind You are right. VSS has many bugs and is not really "just working". We had very often problems at start, as we tryed just to use it. Then we noticed some issues and while next project we tryed to workaround them.

    But I can agree, VSS isn’t the best VCS around here but still better then developing w/o any VCS.

  3. Strider says:

    We are using VSS as a version control system and the MorphX integration is ridiculous! Updates get skipped all the time during synchronization, and the client freezes 2 out of 3 times on big repositories. My team would be more productive with no version control at all!!!

    Instead of publishing white papers you should spend your time and energy on debugging your crappy implementations!

  4. Waldemar Pross says:


    thank You for expplaining. I’m not that good in english. Didn’t remember "as an example".

  5. Vincent_Vijt says:

    Waldemar, as explained in the introduction of the whitepaper:

    "This whitepaper provides detailed step-by-step instructions to integrate a VCS with the MorphX IDE, by using how TFS was included in Microsoft Dynamics AX 2009 as an example."

    TFS is a file based VCS and there are many others that have this same basis, like the one you mentioned; SVN. You could (re)use much of the code/design choices to add support for your favorite flavor of VCS, and the whitepaper is an excellent guide for it.


    I for one chose to use TFS integration for my Dynamics Ax projects but not as designed. Support was added to be able to develop as a (relative small) team on a single AOS server which required some rewriting of the standard TFS integration, e.g. removing the Team Server and actually checking TFS if an AOT element can be modified instead of relying on the file permissions of the repository files. Some additions where made like the integration of Work Items which opens the door even more to the full ALM capabilities of TFS (Together with our RLM strategy, one of the main reasons why MorphX VCS wasn’t a choice).

    When VS/TFS 2010 goes RTM, manual testing will be added with Test and Lab manager.

    However, the question I have; how will TFS integration evolve in the Dynamics Ax roadmap since there are rumors(Channel9) that in the (distant?) future development will move to Visual Studio?

    Thank you,


  6. Waldemar Pross says:

    Thank You for sharing this Information!

    Do I understand right, that this white paper takes TFS as EXAMPLE how to integrate third party VCS (Sub version e.g.) or is TFS allways used to integrate third party VCS?

    Thank You!


Skip to main content