backup client with very specific logic

A proposal for this project is a must. I only accept C# for Visual Studio 2013 Code must be commented Source code must be delivered before final release This project must have a project solution file (*.sln) A text file must be writen indicating added references to the project No 'Tiers' or 'MVC' programming will accepted No external packages will be accepted No external or third party references will be accepted Description Need a program that allow me to backup, all files in a shared folder (with user/password) in a Windows 2008 R2 Fileserver Requirements The client must have the following functionalities: - the backup operation will put files in a windows folder (PC or Shared Folder in a server) - backup folders, subfolders and files - file properties (Created, Modified, Size) must be original of the source file - option to exclude files by extensions (not to backup files .mpeg, .mp3, .mp4, etc.) - backup all files with its current properties, exactly as they are in source - a log file (.txt, .ini or .xml) must be generated after every backup ends. - the program should generate a [login to view URL] (or .xml or .ini) list with all the files not backed up, this way I can 'Retry to Restore' . - the program should be able to run a command to 'Retry Now' to restore all pending files (there should be a list of them). - report the following errors: network not available, no destination folder found. - support windows 7, 8, 8.1 (home and professional) LOGIC HERE: EXAMPLE: today, the backup client should run at 19:00. tomorrow, the backup client should check how many backups there are, not more than 3 backups of the same file should be in the destination folder. the first backup is the original one, taken from the very first time I backedup my documents tomorrow... we may call it, "day2" the backup client should run again at 19:00 and check versions for documents if a version exists and it is the very first one, the backup client should add a second version of that document, probably adding a number-2 at the end of the filename. now, past tomorrow (2 days more than today) we may call it "day3" in day3 the client should check versions of the documents and if the client finds version 1 (original), version 2 (a number 2 at the end of the filename) and no other version is found, the client should add a 3rd version of the file adding a number "3" to the end of the filename. on day4, there should only exist 3 versions to be kept, so as it is day4 we should remove version 2, keeping version 1 (original), 3 and 4. on day5, as we should only keep 3 versions... version 3 should now be removed, keeping version 1, 4 and 5 on day 6, versions 1, 5 and 6 on day7, versions 1, 6 and 7 and so on...