If I read the docs correctly I should not put my Library folder under source control. What should I have under source control so that other programmers can checkout, build and run the project? My structure looks like this.
Game\
Assets\
Standard Assets\
Plugins\
Game.unity
Library\
cache\
metadata\
ScriptAssemblies\
lots of *.asset files
AssetVersioning.db
assetDatabase3
assetservercachev3
I currently have everything under source control. And I feel this is just wrong - should I really have cache files & ScriptAssemblies under SVN?
EDIT: Has anyone else had issues where they needed to include the cach folders?
Is this only possible with the Pro version? I tried doing ‘Checkout’ from within MonoDevelop, but it doesn’t work as it’s stupid and creates a new solution for the project I check out. (This ‘Select Repository’ dialog has some serious issues, is this an untested alpha feature or what?)
I’m wondering if this is going to work anyway. Obviously you’ll want both your Unity project AND your shared code in your source-control system. However, if you do a checkout of a project into a sub-directory of another versioned project you can no longer do recursive updates of the containing project. I didn’t use Git much, but SVN for sure will complain about the path being wrong. And without recursive updates you’re pretty much hosed.
I don’t have the Pro version so I don’t know for sure how this is going to work. But it would be particularly painful if I go through the bureaucracy of have my company acquiring a Pro license just to find out what I need it most for is not going to work.