web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / TFS mapping with AX en...
Microsoft Dynamics AX (Archived)

TFS mapping with AX environments

(0) ShareShare
ReportReport
Posted on by Community Member

Hello,

I followed few links and found that in order to use TFS with AX 2012 below mentioned patch needs to be installed on client computer:

1. Team Foundation Server 2010 SP1 Object Model.

2. Visual Studio 2010 SP1 Team Foundation Server Compatibility GDR.

I have installed these in my DEV machine and my AX-TFS mapping works fine. Do I need to install these in my TEST and LIVE server also? 

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Martin Dráb Profile Picture
    Martin Dráb 239,178 Most Valuable Professional on at

    Version control is used for development. If you don't develop in TEST and LIVE {which you shouldn't), you don't need development tools there.

  • Community Member Profile Picture
    Community Member on at

    Thanks Martin!

    I agree with you, but we have to setup the "Version control parameter" form in TEST and LIVE also. When I try to do it I got below error:

    Could not load file or assembly 'Microsoft.TeamFoundation.Client, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.

    Is this related to any prereq component or am I missing something here. I believe we have to set this up in order to move code from DEV --> TEST --> LIVE

  • Martin Dráb Profile Picture
    Martin Dráb 239,178 Most Valuable Professional on at

    Do you mean that you're going to develop in production despite that you know that it's a terrible idea? :-O Run away from that project!

    If you really want to get yourself and your client into troubles, go on and install Team Explorer.

  • Community Member Profile Picture
    Community Member on at

    No we will not be doing development in TEST or LIVE. I thought setting up Version control parameter is required in TEST also. But as you mentioned, it is only required if we want to develop and not for code migration. Thanks for the clarity.  Let me put my query this way:

    Once my development is completed in DEV and it is checked in to TFS DEV branch. How can I promote this code to TEST and LIVE environments.

    I can use Merging option to move code to TFS TEST branch ,  what is the next step to move it to TST server.

  • Suggested answer
    Sukrut Parab Profile Picture
    Sukrut Parab 71,735 Moderator on at

    You can merge change sets to your test branch from dev branch.

  • Community Member Profile Picture
    Community Member on at

    I can merge change sets from TFS DEV branch to TFS TEST branch. But now the changes have been copied to TFS TEST folder. How can I import it to my TEST environment application.

  • Suggested answer
    Martin Dráb Profile Picture
    Martin Dráb 239,178 Most Valuable Professional on at

    I suggest having a build server taking source code from version control and building a model. Then you install the model to TEST using the usual tools.

    This gives you a much better control and if there is a problem such as a compilation error, it's detected on the build server and you don't break the TEST system.

  • Community Member Profile Picture
    Community Member on at

    Ok, which means I will be having DEV and BUILD server with TFS tools where the code will be moved using TFS branches. Once the code is ready in BUILD server after successful compilation, then import it to TST using usual AX tools (using xpo or axmodel). Similar approach for TEST -> LIVE

  • Suggested answer
    Martin Dráb Profile Picture
    Martin Dráb 239,178 Most Valuable Professional on at

    A model, not an .xpo.

    .xpo files don't guarantee that the code is transferred in full - you may forget some objects, you can't transfer information about deletions, something may get imported incorrectly (e.g. when imported in a wrong order) and so on. Also, model deployment is easier to automate (e.g. if you want automatically deploy new application to TEST every night after a successful night build).

    Note that this doesn't require using branches.

    The recommended way for deployment to LIVE is using a modestore import.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
CP04-islander Profile Picture

CP04-islander 16

#2
GiacomoRovai Profile Picture

GiacomoRovai 4

#3
Douglas Noel Profile Picture

Douglas Noel 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans