How to implement IStorageProviderCopyHook in a Desktop Bridge application

Stefan Angelov 26

Greetings,

I would like to know what is a proper way to implement the IStorageProviderCopyHook interface in the context of a 'desktop bridge' application for a cloud sync engine (using the cloud filter API).
The available documentation (https://learn.microsoft.com/en-us/windows/win32/shell/nf-shobjidl-istorageprovidercopyhook-copycallback) states:

"To register a copy hook handler for cloud folders, set the CopyHook value under the HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/CurrentVersion/Explorer/SyncRootManager/{SyncRootId} key to the CLSID of the copy hook object."

However, I am not sure how to achieve this in a 'desktop bridge' application. As I am aware, the code is containerized and has no access to HKLM, hence modifying the registry programatically will not work. I could also not find relevant configuration options for the Package.appmanifest file.

I'd appreciate any advice on how to implement this interface and incorporate that into the 'desktop bridge' application I am working on.

Thanks and regards,
Stefan

Jeanine Zhang-MSFT 9,431 Reputation points Microsoft Vendor

2022-04-07T02:53:13.29+00:00

@Stefan Angelov

According to the Doc: Build a Cloud Sync Engine that Supports Placeholder Files

The provider registers their copy hook by setting the CopyHook registry value under their sync root registry key to a the CLSID of their COM local server object. This local server object implements the IStorageProviderCopyHook interface.

The cloud files API does not currently support implementing cloud sync engines in UWP apps. Cloud sync engines must be implemented in desktop apps.

Sync engines using the cloud files APIs are designed to use the Desktop Bridge as an implementation requirement.

Why you want to implement IStorageProviderCopyHook in a Desktop Bridge application? Implement the IStorageProviderCopyHook interface is the local server object. And sync engines must be implemented in desktop apps.
Stefan Angelov 26 Reputation points

2022-04-07T06:20:41.457+00:00

Greetings,

and thank you for your reply!

I think I need some further clarification of this line: "Implement the IStorageProviderCopyHook interface is the local server object."

By reading the available documentation from Microsoft and more specifically the line (which you also mention above):
"Sync engines using the cloud files APIs are designed to use the Desktop Bridge as an implementation requirement."
I am under the impression that I am advised to package the application as an MSIX package, which I am doing. I am also under the impression that I have to package the implementation of IStorageProviderCopyHook in the same MSIX package which is delivering the cloud sync engine (after all, I would like to have control over copy/move/delete operations only for sync roots registered by the storage provider delivered through that same MSIX package.

Please, let me know where my thoughts are wrong, and if there exists a sample implementation of this interface anywhere in the samples collection of Microsoft do point me to it.

Thanks and regards,
Stefan
oknick 101 Reputation points

2022-04-08T21:32:23.343+00:00

Not sure if this helps, but you could control all of these operations (and more) through the CfConnectSyncRoot function. I'm not sure why you would ever need IStorageProviderCopyHook if this exists.

Share via

How to implement IStorageProviderCopyHook in a Desktop Bridge application