You can use junction points or symbolic links for this purpose. The solution is to create a separate folder (and workspace) for every user and redirect them to a single common folder. Every user should have his own (private) workspace, but because common code is used in shared environments, workspaces need to use the same code as well (see also AX TFS FAQ). You probably won’t do without multiple workspaces and as it was said, AX2012 doesn’t support them out of the box, therefore it requires a code change.
#What happens if you delete microsoft team foundation server how to
So if you plan using shared AX2012 environment and TFS, you should think about how to solve this problem before starting the implementation. If you want to use the environment for normal development, public workspace probably won’t suit you very well. But it knows nothing about what user currently uses this public workspace. For example, if a file is checked out from version control, TFS knows in what workspace the file is used and knows what user owns the workspace. Strictly speaking, the public workspace is – from TFS perspective – still used by a single user – its owner. One solution is a public workspace – that works well as long as you are aware of its limitations. The previous article should have shown you that you may want to use entirely different approach.ĪX2012 supports only a single TFS workspace and that is created as private, so version control in such environment can’t be used by anybody but the owner of the workspace. This post describes how to solve one of these problems – namely how to use multiple Team Foundation Server workspaces in a shared environment of Dynamics AX 2012 (not supported by default). The comparison of both approaches should help you to choose the most suitable one and point out some problems that may need to be dealt with. It provoked unexpected amount of discussion – and that’s great. isolated Dynamics AX environments – primarily as an introduction to this post and to be able to refer to it. I originally wrote the previous article – Shared vs.
0 kommentar(er)
