I also had this problem after installing "SAP Crystal Reports, version for Microsoft Visual Studio" recently - over two years later.
I specifically installed Support Pack 8 on 64-bit Windows 7 Pro and found that the fix for me was to:
(1) Run the install executable rather than an MSI per SAP's note that this is critical to full integration with Visual Studio (all the way back to the RTM release):
Please note: To integrate "SAP Crystal Reports, developer version for Microsoft Visual Studio" into VS 2010 or 2012, you must run the Install Executable. Running the MSI will not fully integrate Crystal Reports into VS. MSI files by definition are for runtime distribution only.
(2) Run it with Visual Studio closed.
(3) Run it as Administrator.
Even doing (1) and (2) in the list above without (3) yielded an error at the end of installation (even though the account I used was a member of the local Administrators group). Unfortunately I (uncharacteristically) did not note the error and just continued. :P
Bottom line, even though "SAP Crystal Reports, version for Microsoft Visual Studio" showed in Windows' Programs and Features control panel and I could add CR items to and reference CR assemblies in Visual Studio projects afterward, hex-like garbage rather than the expected report designer greeted me when I opened CR .rpt
files in Visual Studio - just like the OP described.
So I closed Visual Studio and uninstalled "SAP Crystal Reports, version for Microsoft Visual Studio" through Windows' Programs and Features control panel.
Further doing (3) in the list above when I ran the installer executable again (i.e. running it as Administrator), I encountered no errors; and afterward the expected report designer rather than hex-like garbage greeted me when I opened CR .rpt
files in Visual Studio: problem solved.