Finance forum

why use one VM for each developer in d365fo

(0) Share

Report

Posted on by Abdelrhman Hiba

321

why use one VM for each developer in d365fo , why canot all developers work on One VM ?

and tahk u

Categories:

Financial Management

Development / Customization / SDK

I have the same question (0)

All responses (5)

Answers (1)

Verified answer

nmaenpaa 101,162 Moderator on at

Like (1)

Report

Only one concurrent developer can work in the development environment.

- There's only one modelstore = one set of application files

- Multiple users can't map the version control in the same application folders at the same time

- Only one user can edit any file at the same time

- Only one build can be running at the same time

I think these are the biggest reasons. In general in software development each developer is working with their own local code in their own development environment. In previous AX versions the development environment could be shared (although it was not receommended in AX2012) but this is not possible anymore with D365FO.

Was this reply helpful? Yes No
Abdelrhman Hiba 321 on at

Like (1)

Report

Dear,Nikolaos

I would like to thank you very much for your response

Was this reply helpful? Yes No
PilgrimCZ 572 on at

Like (0)

Report

Hi Nikolaos,

Is there any chance to use VM with more developer not in same time? I mean that one developer in time, but with different accounts.

So not concurrent.

Thanks,

Marek

Was this reply helpful? Yes No
Suggested answer

Komi Siabi 13,109 Most Valuable Professional on at

Like (0)

Report

Hello PilgrimCZ ,

Yes, it is much possible for cloud hosted environment.

When you deploy a cloud hosted VM, Microsoft gives you two accounts: An admin and a User account.

Two developer can log on and create individual Visual studio projects and work. Nevertheless they are both working with the same metadata files.

Was this reply helpful? Yes No
Suggested answer

Martin Dráb 237,965 Most Valuable Professional on at

Like (1)

Report

You would have to decide how to deal with version control workspaces and pending changes. For example, you could use a public workspace, but lose some trackability. Or you would use a single common metadata folder and you would have to remove the other developer's workspace and add your own. Pending changes wouldn't be allowed and you would destroy them in the process, if there were any.

A more complex, but much more flexible alternative would be creating a separate repository folder for each developer and let developers create workspaces in their own folders. You would also need symbolic links to standard packages.

So it's possible, but letting developers work on their own DEV VMs is usually better. It allows concurrent development, using setup and tools according to each developer's preference, using different versions of F&O (e.g. one developer testing a new application version while others work on an older one) and so on.

Was this reply helpful? Yes No