Maintenance overhead often increases.
Some teams find that the level of discipline required for continuous integration causes bottlenecks.
This often requires a shift in the developer mindset.
The immediate impact of a check-in often causes a backup because programmers cannot check in partially completed code.
Exclusive check-out locks are not enforced.
A high number of files may result in performance degradation.
All local copies of files are set to read-only. If a solution is opened offline, you’ll be prompted to overwrite changes every time.
In offline mode, core abilities such as adding, deleting, renaming or undoing changes to a file are not available