Share
Report
3,542HI. I'm still very new to VSTS.
Myself and a fellow developer (my senior) are working on a model XYZ. It is one of the main products of my company, thus we add new functionalities on a daily basis.
The main XYZ is on a server that my senior works on. I have a copy of the server on my computer.
We want to use VSTS so that I get the work he did and visa versa and in general that our separate versions stay up to date with each other. I understand that is one of the main points of VSTS.
I have numerous tabs open at the moment regarding the above mentioned subject, but I get lost as the help pages are quite extensive.
I would really appreciate a 101 on the correct mapping/setup to use so that our versions can stay up to date.
The current mapping on both my side and my senior is:
Source control $/XYZ/XYZ maps to local C:\AOSService\PackagesLocalDirectory\XYZ\XYZ
Source control $/XYZ/Projects maps to local C:\AOSService\PackagesLocalDirectory\XYZ\Projects
It works fairly well... But I have a hunch that something is not right - there are bugs. For example in some cases when I get the latest version of an element and try to build it, I get an error: (Paraphrase) "The element could not be found".
I read somewhere that the descriptor and metadata also needs to be mapped....
In any case the current mapping is not relevant - we'll change it to the "correct" mapping (whatever it is).
Thanks in advance
*This post is locked for comments
All responses (
Answers (
