So I am working on a simple .NET program for work and hit a bit of a weird roadblock I can’t figure out. The application makes use of a configuration file which adds applications to a dropdown menu. However, before it’s added to the menu, it does a system.io.file.exists to verify that the file exists, at least at the time the menu is created.
However, System.IO.File.Exists(@”C:\Windows\System32\SnippingTool.exe”) returns false, but the executable is there. Likewise, stikynot.exe also returns false. Other files in the system32 directory return true(like notepad). I can filestat these applications, but my .net program just can’t read them them and system.io.file.exists returns false. I have checked various permissions with no luck. It seems to be isolated to a few applications, but I am not sure why.
That’s a feature of 64 bit Windows.
In x64 you have two folders with system files: system32 and SysWOW64.
If you put anything in system32, it will be seen by all 64 bit applications. SysWOW64 is there for compatibility reasons – anything put there will be visible by 32 bit (sic!) apps.
So as far as .NET is concerned, the file does not exist. It works for notepad, because notepad.exe is present in both of those directories.
You can test this behaviour. Create a text file in one of the directories, but not the other and check for its existence. Then change your project configuration (right click on solution -> Configuration Manager) between x86 and x64 and enjoy the result.