Thread: Using Autodesk Vault for Source Control
View Single Post
  #3   Spotlight this post!  
Unread 08-12-2009, 17:22
Trent B Trent B is offline
College Mentor
AKA: Trent Borman
no team (Surviving Grad School)
Team Role: Alumni
  
Join Date: Dec 2008
Rookie Year: 2008
Location: Ames, IA
Posts: 479
Trent B is a splendid one to beholdTrent B is a splendid one to beholdTrent B is a splendid one to beholdTrent B is a splendid one to beholdTrent B is a splendid one to beholdTrent B is a splendid one to beholdTrent B is a splendid one to beholdTrent B is a splendid one to behold
Send a message via AIM to Trent B Send a message via Yahoo to Trent B
Re: Using Autodesk Vault for Source Control
Subversion.

Other options are Git (Github) or Mercurial (Bitbucket) if you can get your school to allow those on the network comps (we were able to get our IT to put Labview and TortoiseSVN on some laptops)

Another option is Dropbox, it actually keeps past versions for 30 days if you have the free version (which I would assume you would find catastrophic errors within 2/3 of the build season which would require reverting)

With dropbox installed on computers, anything in the Dropbox folder gets auto uploaded with each new version, in windows you can right click and using a menu item view deleted items, or find old versions online.

Dropbox wins in the sense it auto uploads every save you ever make, but it loses to SVN/Git/Mercurial as you cannot make "commit" notes about what was changed.
__________________
Former 2502 (Talon) Captain and 3928 (Neutrino) Mentor, currently teamless and attending Penn State for graduate school.
Have questions about Iowa State University or Penn State University? Feel free to email or PM me