Can you elaborate on the concurrent checkouts (particularly merging check-ins).
Also, can the "Change List" be identified later on the Team Foundation Server side so the change set can be fetched for deployment or building on a test server?
The biggest problem we've had with using version control is that it provides absolutely no help in deploying our changes in a controlled manner.
For example, we make a new project for each Change Request we get from our users. From the VCS side it is impossible to identify which XPO files belong to an AX project. We also haven't found a good way to identify which versions of objects have been deployed to our test and production systems, and which versions in VCS have been tested and marked as "approved" for deployment.
If you look at an object in the AOT of your production AOS, is there anything that identifies the version # from the VCS that was deployed? I'd like to be able to look at an object in production and see that it corresponds to version "n" in our VCS.
And would you guys PLEASE consider using GUIDs for object IDs and ditching the "Team Server" entirely? It makes development very difficult when we have partners and remote developers who don't want to be VPN'd to our network just so they can be connected to the team server.