I am trying to transfer to a new Computer. However the resource compiler is not being activated on the new computer. When I do Rebuild on the old computer it comes up with 1>Compiling resources.... On the new one this does not come up. What are the various switches that should be checked to get the resource compiler to run? I have set the default application for .rc files to visual studio as this is what the old computer has and also to c:\program files (x86)\Windows Kits\8.1\bin\x64\rc.exe but neither worked. One of the other posts mentioned a reset button under tools\options\intel compilers\Fortran but I cannot find it. I am using Visual studio Community 2015 on Windows 7, Parallel_studio_xe_2016.3.059
Thanks for your help
The resource compiler is installed as part of the C language so you need to ensure that that is selected during the visual studio install. I am not sure that is added by default. I would do an re-install of VS. The setting you are playing with should all be set up automatically by the install.
Thank you. I managed it at the second attempt.
You need to remove any association of file extensions .rc .rc2 and .rct before running Visual Studio install, (repair might do it.)
I have same problem with resource compiler. Resinstallation did not solve the problem. What is also funny Visual Studio C++ DOES WORK but fortran project do not. That makes me thing that something is wrong with Intel Fortran Composer (Im using 2013 version).
As in this case that you posted to here, are you also using Visual Studio Community 2015?
If so, did you verify during the installation of that what is cited in Installing Visual Studio 2015 for Use with Intel Compilers?
The earlier thread here contains advice on other things to check/try:
Hope that helps
I eventually found the problem.
When I installed Winteracter on the new computer I ticked the box saying associate .rc files with the Winteracter resource editor. I had to manually removed the association with Winteracter resource editor, before running the Intel compiler setup program again to get the correct association. The Intel compiler setup would not reset the association if it had already been associated.
What I have usually done in these situations is delete the registry entry HKEY_CLASSES_ROOT\.rc and do a "repair" on Visual Studio.