Why shouldn't I use SharePoint for source control?
Why using sharepoint as a sorce control is stupid idea:
- Performance of sharepoint is much worse than any Source Control Tools for example Team Foundation Server or SVN
- Sharepint doesn't allow to compare different historical versions of the same file
- SharePoint dosen't allow for branching, merging and labeling.
- Sharepoint doesn't link changes in set of files as a one change (this is very helpful if you want to track the changes)
- As far as I know SP doesn't allow to have different versions of whole project in the same time.
- SharePoint dosen't have customized gui to manage source control code.
- Sharepoint doesn't allow to link requirements with code changes. For example TFS links work items with check ins. This is also very helpful if you want to track your business requirements and code changes.
Licensing Costs... You can get many many many tools that cost much less (even if they turn up their noses at free tools) for the same cost as SP.
Also, no branching and/or merging.
Using SP for source control is like living in a factory because it's got 4 walls and a roof. Totally ignores functionality and intent.
Another problem with SP, if there are versions being removed by someone, SharePoint doesn't keep the full history on who removed them (as far as I know).
The sad thing is a lot people, including our company, don't have the concept of revision control. The point is they need to be educated on how important it is to have a configuration management or revision control process.