There is an unsaved comment in progress. You will lose your changes if you continue. Are you sure you want to reopen the work item?
PDFRider compilation is not properly configured for 64-bit systems
On 64-bit systems, .NET JIT compiler runs in 64-bit mode when the application is compiled as processorArchitecture=msil.
OK, that's nice - almost "good" - for programs that are self-sustaining with no external dependencies (like a browser control), but when the program relies on external plugins inside an external container (web browser), it gets messy.
There is no 64-bit Adobe Reader, so since the 64-bit mode of PDF Rider opens a 64-bit Internet Explorer control, it tries to open a PDF handler that's registered only with the 64-bit version of Internet Explorer (verified by the same behavior occurring in "Internet
The symptom this causes is that PDF Rider opens normally, but when you open a PDF, it shows that the file couldn't be opened, and it opens Adobe Reader in a new window (which is the 64-bit IE behavior).
Using "CorFlags.exe /32BIT+ PdfRider.exe", I was able to modify the program to explicitly run in 32-bit mode, and it works 100% perfectly with 32-bit emulation ("PDFRider.exe*32" in Task Manager).
Simply changing the processorArchitecture from "msil" to "x86" should correct this problem, although I'm not a .NET developer (...yet) and have no idea where that parameter would be hidden... probably somewhere in the project options. But
that'll make PDFRider work with 64-bit systems, as I can 100% guarantee it's non-functional for most users right now running 64-bit Windows ;)