I've a problem in debugging my application compiled with VS2013 and IVF Compiler 17 update 8.
In Local Variables windows, allmost all variable appears in Hex, and the options "Show in hex" is of disabled. Trying to enabling it and then disabling again doesn't work. In Watch I get error CXX0017 - cannot find symbol - I cannot see any variable, despite some of them are visible in Local Variables window.
I read this topic and I firstly tried solution two (uninstalling IVF, repair VS installation, reinstall IVF). Nothing changed. Then I tried the first solution, in the folder:
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Packages\Debugger
there's no CppEE.dll and no ForDbgSW.dll. Renaming NatDbgEE.dll to CppEE.dll causes errors when launching debug ("cannot start program, NatDbgEE.dll not found".
Can anyone help please?
Caveat: I am not a Windows/Visual Studio expert and barely us it myself. But I believe you can try this:
Uninstall Intel Fortran
Run the Visual Studio Installer. I think from Setup, Add or Remove Programs select Visual Studio
When the installer comes up there should be an option to MODIFY/Repair
try that - let it repair your VS installation
then re-install Intel Fortran
Like I said, I'm not a Windows person but I do remember doing this sometime in the past.
here is a link to the System Requirements in teh Release Notes for your 17u8 compiler
Were I you I would try to completely remove Intel Fortran and VS, reboot, and reinstall from scratch. v17 is no longer supported and I don't have a VS2013 around for testing so I'm afraid there is nothing more I can do in this case.
one last thought - before you uninstall everything
Have you tried creating a new empty Solution/Project. Then start simple with a Hello world and debug it, look for symbols? Perhaps your Solution or Project are somehow corrupted. Just a thought. That's what I would do first.
Thanks for reply - yes I tried this, same bad behaviour.
I'll update the compiler, it seems the only way.
for recent compilers, installers must be improved. Just for instance, a (repaired, just for above reasons) vs2013 installation is not recognized by recent installers. I had to use vs2019 to get all to work.
The support for VS versions is shown in the release notes. Ifort installers normally cover three versions of VS which seems reasonable to me.
You need to look at the release notes.
Despite that, in another pc ivf2020u2 is working with vs2013, correctly detected during installation. I assume that release notes are too limiting.
But nevermind, this is not the key point. The key point is that the installer does not detect the presence of vs2013 - I suspect that if you repaired the installation of vs2013, its installation path moves from "C:\program files(x86)" to "C:\program files".