I have just started using Visual Studio Team Services (team foundation server/TFS) to manage some of my NAV projects.
Love it so far, and its free up to five users. Still a lot of challenges, but mostly PowerShell seem to be able to handle it. Several of my MVP colleges have made a lot of videos on YouTube about TFS and NAV Source code management that I can recommend.
Source code control is actually just a small part of TFS. Its so much more. Like build-in bug and feature requests, testing and builds.
But one thing that is a bit annoying when you manage Navision projects on source code level, is the cascading changes that happens when you change a field name. Don't know if cascading changes is the correct technical term. What I mean is if you change the field name, then every object in NAV, where this field is used, then the source is also changed. Despite the actual object does change physically.
So we end up with a lot more source code changes than actual changes!
Has anyone found a solution to this.
Not doing it would of course be my own first response, changing the caption instead, but sometimes that's not really enough.
No, I do not always do this full export. I only export the objects I am working on. And BTW: I always do that manually, basically because we tend to cut features into small parts. Scripting this does not really make sense. Let's say the scrum way: not more than a couple of hours or maximum of a day or 2.
When updating my database I rely on the fact that this is a task I do at least once a day, when I start working. In TFS I first merge all changes from others into my branch and then I import only those objects that have changed since the day before. We still do that manually (also) as we have not put effort in scripting that and ... we do it quite fast. But of course there could be some hole in this mechanism and for that, among other reasons, I always do the compare I mentioned above.
Have you already registered for my workshop at NAV TechDays? This what we will be working on. ;-)