I found the issue.... not the solution yet though. Turns out, everything I said was wrong, it does work. I was simply operating on files that have been run through my installer, which appears to not deal with unicode. When I navigate to the original files, they load up fine and display fine. Which makes much more sense as I could not bring myself to believe that I couldn't read unicode filenames.
So, my normal .NET MSI installer is canning the unicode characters only... any ideas? Jason
