Wish Microsoft would open-source their secret UWP file explorer because even though it's terrible, they're doing things I can't figure out.

@algorythm

There must be some C language interop calls

@CozyPlanes I sure fucking hope not.

What are they doing that you can't figure out?

@M3m35terJ05h A couple things. I think it's because I'm using System.IO and perhaps they aren't. There's this weird issue where I can't get file info from files in the root of a drive, and they seem to be able to access files in c:\Program Files whereas I cannot

@AlgoRythm sounds like permission issues. Program files is supposed to be locked down so you need to be running as admin to do anything. I'm guessing explorer has some special secret permission to run as admin without the uac prompt or it's talking to some system process. Or maybe you need to do something to say you only want to read there

@AlgoRythm it is
Uwp is locked down, you can't really access to system files directly unless you run some background service in nother language and make calls with that and your uwp app somehow...(just my random thoughts)

Or, like it was said, it uses native system calls, not that weird uwp sandboxing contraption. That's most probable.