[Feature Idea] Is version control for MVC projects possible/worthwhile?

[tzdanows]

So today, I presented for my second review(UAT tester) and the day prior I made a "demo script" which consisted of my intended tests for the application. The script was meant to show all of the functionality I had working and after making this script I continued making changes to the application. The next morning, I woke up and wrote up some additional feature changes, fixes, and decided to do a run-through of my demo script which to my surprise had no longer worked in some sections but it was also difficult for me to fix it despite documenting what changes I had made.

So this entire story I've discussed could be prevented by a few factors. One factor I would consider good habits, such as testing after every implementation which I intend to do in the future. But another consideration I had was that version control support for MVC projects would be a great thing to have for such a situation.

So my question is: would a version control implementation in the future be a viable route? I think its a standard in developing modern software and web applications and while our platform is structured quite differently, I still think its worth starting some dialogue in this space.

Side note: There might be a version control or alternative already present somewhere, I'm just not aware of it.

[JustinVanRegenmorter]

Version control can be managed using the Import/Export feature. This allows the user to export one or many objects to XML files and reimport them to override the existing version or create a new object in a project.