codessentials / yadis.net Goto Github PK

Yadis Notification system cannot show messages for tasks with name > 64 characters:

If a task has "Delete Events" enabled, it doesn't delete the file in the destination. I deleted the task & recreated it to be sure it wasn't corrupt in any way, but it still doesn't replicate the delete event.

I found the "Remote: Codessentials" reporting tool under "Messages". I tried to submit a bug report using it but I get the error message "Sorry, your bug report could not be sent. Please send your bug by email to [email protected]". :)

R1.10.7 needs to be beta tested.
Anyone who wants to participate can mail to [email protected]

Move all non GUI elements to libraries.
Separating the backup logic will

• ease the unit testing
• prepare the product for upgrading to WPF / Metro.

When deleting a folder in the source, the folder is not deleted in the target.
Folder and files are kept in the target.

self-backup is not offered explicitly to the user.
maybe we should ask if he wants to enable this option after some time/nr of tasks?

Good article on plugin structure to start with:
http://www.codeproject.com/Articles/105549/A-more-extensible-way-to-build-plugin-system

It is now (still) set to true.
Maybe it can be put lower on the screen too, since it is not that important anymore.

When the task setting "Verify change date" is selected, any backlog file of a file that is not newer than the file on the target is not removed from the backlog list.

Possible implementation example:
http://www.codeproject.com/Articles/22745/Volume-Shadow-Copies-from-NET

If you have multiple tasks and you want to run a Copy-all job for all these tasks, you need to request the Copy-all job for every individual task.
It would be nice to have an option to start a "Copy All" job for all tasks.

An exception has occured in FileChangeMonitorV2: The process cannot access the file.

Under "Proxy Settings", even if the proxy setting is correct, clicking on the "Test connection" button produces the error "Connection failed: Invalid URI: The hostname could not be parsed."

issue-17 handles about "Make processList and backlogList thread safe".
This needs to be done but since that is a major adjustment, we could first just suppress the error message. This is OK to do because the system will automatically recover from this issue by retrying the backlog process on a later time.

Suppress this message:

A Task filter should allow excluding subfolders from being watched.

Title: Critical application exception
Message: Thread is running or terminated; it cannot restart.
Exception: System.Threading.ThreadStateException: Thread is running or terminated; it cannot restart.
StackTrace: at System.Threading.Thread.StartInternal(IPrincipal principal, StackCrawlMark& stackMark)
at System.Threading.Thread.Start()
at Yadis.NotificationManager.start() in C:\Users\mvrm\Dropbox\Work\Yadis\NotificationManager.vb:line 43
at Yadis.NotificationManager.addRequest(NotificationRequest aNotificationRequest) in C:\Users\mvrm\Dropbox\Work\Yadis\NotificationManager.vb:line 15
at Yadis.NotificationManager.NotifyWarning(String pOrigin, String pMessage, Boolean pEvenOnShutdown) in C:\Users\mvrm\Dropbox\Work\Yadis\NotificationManager.vb:line 92
at Yadis.TaskConfiguration.notifyTargetUnavailable(Boolean aForse, BackupMode aMode) in C:\Users\mvrm\Dropbox\Work\Yadis\TaskConfiguration.vb:line 262
at Yadis.FileChangeMonitorV2.processBackLog(BackupMode pMode) in C:\Users\mvrm\Dropbox\Work\Yadis\FileChangeMonitorV2.vb:line 1427

If you create a task with a name longer than 64 characters, the task can be saved but it cannot be edited anymore afterwards.

Task name should be reduced to 64 chars

At this moment, if versioning is enabled on a task, the original file name is not kept.
It is extended with the date-time stamp. This makes it hard to restore files.

http://stackoverflow.com/questions/4197238/using-synclock-to-synchronize-access-to-listof-t

Use
SyncLock ctype(m_List, IList).SyncRoot
in
add / remove / iterate

The Yadis! Backup setup file now does not reflect the full assembly version and description info. For example, if a Beta version is released, the setup assembly is not showing this in any way.

TODO:

1. Improve the value of the setup.exe properties.
2. Let the installer indicate clearly that the user is installing a Beta version.