v8.1.26727.0-Beta2
·
9 commits
to master
since this release
- WebDAV Drive sample on macOS now supports cookies authentication.
- WebDAV Drive sample on macOS now provides custom protocol "fuse:" implementation.
- All Windows platform samples now run on .NET 8.
- Challenge-response authentication dialog (Basic, Digest, NTLM, Kerberos) is replaced with system authentication dialog in WebDAV Drive sample on Windows platform.
- On Windows platform the IFileSystemItem.GetPropertiesAsync() and IFileSystemItem.GetThumbnailAsync() were called only if remote storage ID was set for the item. Now these methods are called for any item.
- On Windows platform if the IFileSystemItem.GetPropertiesAsync() is called before the Engine is has started, the ArgumentNullException is thrown. Now the IFileSystemItem.GetPropertiesAsync() is never called before the Engine start.
- In WebDAV Drive sample on Windows if web sockets failed to connect, the client was trying to reconnect to server infinitely. Now web sockets try to re-connnect only if first connection was successful. Otherwise RemoteStorageMonitorBase.StartAsync() throws exception. If SyncID or CRUDE web sockets are not supported, the timer pooling is used now in WebDAV Drive sample.
- If remote storage did not support resource-id property on the root item, the WebDAV Drive sample was throwing WebDavException "resource-id or parent-resource-id is not found. Your WebDAV server does not support collection synchronization. Upgrade your .NET WebDAV server to v13.2 or Java WebDAV server to v6.2 or later version." On sample start. Now if resource-id is not supported on the root item, the sample runs with CRUDE remote storage monitor or timer pooling.
- In WebDAV Drive sample for Windows, if remote storage did not return resource-id on files and folders creation exception was thrown. Now this bug is fixed.
- PreferredIncomingSyncMode is added to the WebDAV Drive settings on Windows platform. Allowed values are: SyncId, Disabled, TimerPooling.
- In Windows platform samples if any file is read-only, unmounting failed. The read-only attribute is now removed during unmounting.