Microsoft Dynamics AX (Archived)

Developing on the same VM with TFS

(0) Share

Report

Posted on by Community Member

Hi!

I have problem with developing on one server by several developers...

Each of them logs on server by his own credentials...

The problem is because MS Dynamics AX have shared settings... And TFS is configured to the specific account...

Is there any solution to cooperate by several developers on one server with TFS(also every account have own specific TFS account)...

Thanks

Regards

*This post is locked for comments

I have the same question (0)

All responses (23)

Answers (4)

Suggested answer

Vilmos Kintera 46,149 on at

Like (0)

Report

Have you read the documentation linked in the related thread? It talks about possible solutions for single and multiple instance development, see the Shared AOS Topoligy page which refers another document for exactly that scenario. It is a not recommended by Microsoft to do it that way though, and I agree.

community.dynamics.com/.../219914

Also please make sure you mark the helpful answers in your threads to close it, thank you!

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Unfortunately i'm not a member of CustomerSource comunity... So i can't read "Change Management and TFS Integration for Multi-Developer Projects White paper"...

All developers are added to the same TFS team project members... But the problem appears when i open AX... Infolog give me message "The directory C:\...... does no exist" because link to the another TFS repository on other user account...

Was this reply helpful? Yes No
Martin Dráb 237,803 Most Valuable Professional on at

Like (0)

Report

The integration between AX and TFS expects that each developer has his/her own instance of Dynamics AX. That makes sure that developers can work in parallel without affecting each other. You can happily do it on a single server, if you want.

But it seems that you're trying to use a single AX environment for several developers, which simply isn't supported (when using TFS). It's possible to customize AX it allow it, though, if you're ready to give up all advantages of isolation.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

By "Instance of Dynamics AX" you meant client or server ??

For me the most important thing is to create a multiple developers environment on one server...

I also want to maintain the code by TFS (community.dynamics.com/.../219659) to easily synchronizing LIVE, BUILD, TEST and DEV instances...

Was this reply helpful? Yes No
Martin Dráb 237,803 Most Valuable Professional on at

Like (0)

Report

An instance is a separate environment with it's own code and data. Code is in the modelstore database associated with AOS, so you clearly need a separate modelstore DB (storing code) and AOS (using the code). Data is in database, so you need a separate database as well. Client doesn't store either code or data, so you can use a single client to connect to several AX instances (e.g. DEV and TEST, or several DEV boxes). Just make sure it's a compatible version; also, different developers sometimes need different client libraries, so they may actually need separate clients as well.

As I said, you can install several databases and AOS on the same server machine (regardless whether you mean a Windows server or a physical server).

But if you mean AOS when saying "server" (what a vague term!), then they would all share the same code, so refer of what I said in my previous reply. This scenario isn't supported.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

The case is more complex that i've imagine...

By "server" i've meant phisical machine with Windows Server instaled on it...

Let me explain it again step by step using correct terminology:

I have physical machine with Windows Server, SQL Server etc...

I have installed on it Microsoft Dynamics AX 2012 R3 and CU11...

So i have an AX instance with AX data, AX model, AX baseline in SQL Database... Suppose that this is LIVE...

On the other 3 phisical machines i did the same creating instances BUILD, TEST and DEVx.

So i have 4 AX instances which are isolated on each other...

Now... i want to be able to deploy our solutions DEV->TEST->BUILD->LIVE and take branches LIVE,BUILD->DEV

DEV is an instance for single developer only and there is no need to give ability to maintain it simultaneously...

But TEST is an instance where several developers would work...

This is the point of this topic... How to create this ability ??

Sorry if my question is infantile but i'm on the beginning of my AX journey :)

Was this reply helpful? Yes No
Martin Dráb 237,803 Most Valuable Professional on at

Like (0)

Report

If you do development on the box called TEST, it's in fact a development environment. That it has a misleading name isn't important. If you want several developers developing at this single box at once, I've already explained that it's not supported and it would require a customization, if you decided to gave isolation of developers. Don't forger that if you use TEST for development, you'll have to build another environment where you will do testing.

If by "developers working there" doesn't mean development (e.g. they may be testing there), than you have no problem.

By the way, I hope that you don't actually have a single-box LIVE environment.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

To be honest i don't have any of them... Before i'll start to create a architecture for a new project (my first individual project) i want to consider everything very carefully... It is very wierd for me that there is no simple method to work simultaneously with one sourcecode file using TFS... Mayby there is an option to install seperated clients for each user ?? The main point of TFS is that many of developers can change the same part of code and then merge it correctly...

Was this reply helpful? Yes No
Vilmos Kintera 46,149 on at

Like (0)

Report

I think you misinterpreted the post we originally had in your other topic.

You would be developing in Dev, check in the changes there, and move changes to Test via an AX build environment that is only use for producing a modelstore for Test.

You do not need a branch for Test, unless you specifically want to (i.e. having Dev + Test + Prod branches), which complicates things further.

Was this reply helpful? Yes No