BeaverSync application first commit:
- we have two projects in solution:
  1. BeaverSyncLib as business logic and object model library of application,
  2. BeaverSyncTest as unit-tests of BeaverSyncLib

Start object model:
- SyncFile class as file metadata presentation (file size, file path, last modified date, etc)
- SyncFilesPair class as business logic for synchronize pair of file (as SyncFile)
- FileSystemManager class as encapsulated work with file system (using System.IO namespace), now it's not implemented empty. For testing purposes use MockFileSystemManager Class implement IFileSystemManager interface
- defined FileMetadata struct
- IFileSystemManager.GetSyncFileMetaData renamed to GetFileMetadata and returning type changed to FileMetada
- SyncFile.RetrieveFileMetadata method implemented with using FileSystemManager object instance inside SyncFile
- added SyncFile test-constructor with IFileSystemManager injection
- accomplished MockFileSystemManager with add files repository (as sortedlist) inside
- all SyncFilesPairTest is OK
- move MockFileSystemManager to separate file
- made SyncFileTest class with unit-tests for SyncFile
- implemented FileSystemManager with System.IO using
- converted FileMetada.ByteSize field from int to long
- redesigned SyncFile class logic and inner structure:
  - removed fields ByteSize and LastModified, now just return FileMetadata object from RetrieveFileMetadata method
  - removed RetrieveFileMetadata calls from constructors (cause it's possible exception throwing inside)
start develop Console BeaverSync simple application example:
- define app.config BeaverSync section
- test console app reads syncPairs from config file and do sync for all pairs on user input
- add ToString method for IFileSystemManager
- keep BeaverSync configuration in separate file (beaverSync.xml) inside app work dir
- add example of beaverSync.xml
- make the test for check backup nonactual file on sync method with using FakeItEasy
- add FakeItEasy and Moq libraries to the test project (packages downloaded with Nuget )
*Moq library not using yet..
- add backup functionality to the SyncFilesPair class
- moved FileMetadata class to separate file
- marked MockFileSystemManager.cs as obsolete
Merge branch 'feature/read-syncFilePair-from-config' into develop

Conflicts:
	BeaverSync/BeaverSyncLib/IFileSystemManager.cs
- restore ToString realization from feature/read-syncFilePair-from-config branch
- fixed backup file path (replaced ':' to '-' in filename, and used '\\' instead of '/' as path separator)
- fix tests (updated backup file path)
- boolean flag NeedBackup (when true nonactual file will be backuped)
- BackupDirPath property (define directory for storing backup files)
Merge branch 'feature/backup-overwritten-file-on-sync' into develop
- automatic enable backup functionality for all pairs from config in console test app
- add method FileSystemManager.CreateDirIfNotExist
- made FileSystemManager as singleton
- edit hours format for backup filename to 24-hours
Merge branch 'master' of github.com:alexander-makarov/BeaverSync into develop
induced commit, really changes nothing
Merge branch 'develop'