Windows C# backup client and tray-icon

Note that this project is far more than just send files to a remote server. Please read through each requirement carefully. Software must be able to backup (zip/encrypt) files to a WebDAV (https) server and only transfer changed files. This can be speeded up by having local list fetched from webdav with checksums compared to local list and more details instead of actually downloading. It must also keep track of revisions of files. Important to avoid as mutch transfer/connections as possible, having temp-lists should have dramatic effect (do NOT download files and compare them there, waste of resources). See suggested backup approach on the blog-entry further down. Installer (msi or exe): Ask for username/password, along with an secret password (used for encrypting backup). Backup-destination (hostname/port) are read on install from a [login to view URL] file. Windows (client): Screen 1 - Backup: Similar to CrashPlan (attached). Show destinations/size of selected dirs/drives. Option to start/pause. Screen 2 - Restore: Choose a date and option to choose files/dirs to restore to original destination. Screen 3 - History: Show latest runs (how many files backed up/changed) Screen 4 - Settings: How often backup run and when Tray-icon: - Option to Start, Stop or Pause. - Show animation and status on running backups. Suggested technical approach: - [login to view URL] Other requirements: - Handle interrrupted/resumed transfers gently (retry or resume) - User friendly interface - Must be allowed to re-distribute to clients and others (license wise) - Source code/prject-file must be delivered on final project Inspiration: - Attached Crashplan. - And [login to view URL] - A similar client like that, just with directory-trees and restore/revision restore in addition, is acceptable. Just a litle bit more in direction of CrashPlan, with similar look on each screen. Technology required - AES-256 encryption - Zip-compression - Use Shadow backup on windows (ensures file integrity) - WEBDAV-component from third-party can be accepted cost (check with me first) if it saves dev-time and stability.