What's the best way to version control graphical assets on Windows?

I’m a web developer / designer, and I want to be able to version control graphic files (Photoshop / Fireworks / Illustrator / Stock Photos / etc).

This would normally be fine but some of the files I have tip the scales at around 800MB, which TortoiseHG chokes on. I currently have a server I put all my files on so all my computers can access (it’s my work computer and I have some flexibility as to installing some linux packages).

  • How can multiple people contribute to resolving conflicts during a large DVCS rebase operation?
  • How to quickly switch source control providers in Visual Studio 2010?
  • For binary files should I use bfiles or bigfiles?
  • Merging: Hg/Git vs. SVN
  • What is a changelist in IntellJ IDEA ? A list of changes compared to what? An accurate explation is sought for
  • What makes merging in DVCS easy?
  • Any advice on the best way to go about this would be appreciated.

  • How can I use Beyond Compare 3 as the diff3-cmd for svn?
  • NetBeans 7.x and Subversion 1.7.1
  • Why does `git remote` not list anything on my git-svn repo?
  • TFS to SVN
  • How can Windows file and folder shortcuts be created via C#.NET code?
  • Codeplex + SVN. How good is SVN bridge?
  • 2 Solutions collect form web for “What's the best way to version control graphical assets on Windows?”

    Unless those graphic files changes every day, a better way to store them would be to:

    • avoid VCS (CVCS like SVN or DVCS like Git or Mercurial): those are made to keep the history of elements, with the possibility to compare with older versions.
      You rarely need that with graphic files.

    • use a generic repository (i.e. a shared directory with naming convention of tagging feature, not one with branching and merging like a VCS).
      I generally use a maven-based repo like Nexus.
      I then store in the VCS a text file which will contain the exact label of the artifacts (in your case the “set of graphic files”) referenced in the Nexus repository. That text file also include a MD5 checksum.

    That solution allows your repositories (both the VCS one and the artifact one) to scala nicely together.

    I’m not sure whether they’ll suit your needs but you can find a couple of suggestions at http://sixrevisions.com/project-management/the-ultimate-guide-to-version-control-for-designers/

    Git Baby is a git and github fan, let's start git clone.