Accessing Network-Mapped Devices from Packaged WinRT Application

[lukeblevins]

In Files, we use the FindFirstFileExFromApp API to enumerate storage locations. When accessing a network drive this way with the broadFileSystemAccess capability, it works as expected. However, when the app is compiled for release to the Microsoft Store, none of the files inside the drive are shown. Is there a capability I'm missing, or should Project Reunion improve the filesystem apis and/or relevant capabilities to allow for access to mapped NAS devices when packaged?

[lukeblevins]

@jonwis Do you have input on this scenario? It seems like I'm missing a capability, but it displays my NAS drive files perfectly fine in debug mode.

[jonwis]

Ok, then @keith-horton, you're next!

[smaillet-ms]

According to a quick read of the code the UNC access check is double layered, the firewall is queried for the user and package to detect if the location is controlled with the privateNetworkClientServer capability AND additionally the enterpriseAuthentication capability is required.

[lukeblevins]

@smaillet-ms Just added the enterpriseAuthentication capability to my app, repackaged it, and it still doesn't work...

[lukeblevins]

I also tried to get around the issue by catching the invalid handle, and adding the respective StorageFolder to the Future Access List, but it doesn't work this way either.

[lukeblevins]

I would just use Windows.Storage to enumerate the location, but the FromApp methods are far faster. @jonwis @smaillet-ms I wonder if it has something to do with the FromApp method I'm using? The docs for it state that it abides by the UWP security model, yet it might only be for the local filesystem.

[sunjw]

Hi, @lukeblevins
Does this problem solved? I have the same issue with CreateFileFromApp function to open files on SMB share.