MonoManager.asset

Questions & Answers
1

According to the documentation on external source control, you should add all of the *.asset files to the source control repository. Since all of the asset files are binary, it becomes very problematic when commiting changes (Even with the projects source control option enabled). Especially when we have upwards to 10 developers simultaneously working on a project.

Doing several tests, it seems that it is possible to leave the MonoManager.asset out of the repositiory, as long as you import any newly added scripts. To simplify things, you could force a reimport of every script after syncing to the head of the repository.

Does this seem reasonable, or will something else in Unity explode? My greatest fear is that months of work could be destroyed by this breaking something within the prefabs and scenes that I do not know about.

The .asset files really should be converted to something that can be merged once the external source control option is enabled. It would alleviate a lot of the headaches we have ran into with source control.

2

I can't give you a definitive answer, and my team does have this file checked into SVN with our own project, but what we have found is that it seems pretty meaningless. We are constantly overwriting this file with one version or another since it cannot be merged, and it seems to have no effect whatsoever. Whatever data is stored in here doesn't seem to be related to anything particularly meaningful to the game execution itself, or is something that just gets auto-created every time, at least. We haven't lost any work by doing resolve conflict with "use theirs" with major changes happening on both sides, so I'm fairly certain it is safe.

3

I was wondering about it also. It seems this file is NOT listed with the other .asset files mentioned in http://unity3d.com/support/documentation/Manual/ExternalVersionControlSystemSupport.html.