With full VS2010, and the Visual C++ component installed, you should be able to edit dialogs. You're sure you're in the VS2010 environment? Did you do a default install of VS2010 before installing Intel Fortran?

Yes - you should have received a warning when you installed Fortran if it did not find Visual C++. I suggest that you uninstall Fortran, install the Visual C++ component, then reinstall Fortran.

You should be able to just double-click on the .rc file and that should bring up the resource editor.

The problem now is that the folder containing the Windows SDK .h files is not in the Includes path. This ought to have been set up when Visual C++ got installed, but some customers find it didn't. Maybe the order in which you did the install contributed to the problem.

Find the folder on your system containing windows.h. It is possibly C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\ Add this to the list in Tools > Options > Intel Visual Fortran > Compilers > Includes.

It's the $(WindowsSdkDir) definition which is the problem. It comes from a registry entry which may not be correct. You can look at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows to see if CurrentInstallDir matches what you found above. It should. Otherwise, just add that folder to the list for Includes.

The different versions of the SDK install in different places. Just put:

C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Include

in the Includes list in Visual Studio.

Where do you get the error? When you try to open the resource file? This suggests to me that the registry entry for the Windows SDK is incorrect.

What do you have in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SDKs\Windows (if you are on an x64 system)?

What about HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows ?

There should be four values under that key, (Default), CurrentInstallFolder, CurrentVersion and ProductVersion.

You could try this. Uninstall Fortran. Do a "Repair" on VS2010 from Programs and Features, then reinstall Fortran. Or you can download and install a recent Windows SDK which might correct the problem.

Try installing the SDK. It's not Fortran that defines these entries. I am not sure what causes the current and product versions to be different here.

Ok, big hammer time. Add the following to your system environment variables:

WINDOWSSDKDIR
C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\

Be sure to include the trailing slash.

To edit environment variables, right click on Computer, select Properties. Click on Advanced System Settings, then the Advanced tap, then Environment Variables. Create a new system variable as above. Log out and in again.

I've been playing with my system to see if I can understand how $(WindowsSdkDir) gets defined by VS, but haven't figured it out.

What happens if you copy windows.h into the same folder as the .rc file? There must be something else odd going on here I'm not seeing.

Let's try this. Look at the instructions for VS2010 in this article. However, instead of updating Library Files, add the complete path to where the .h files are to the Include Files list for C++. I'm convinced that the issue has to do with the use of $(WindowsSdkDir).

Fascinating. I've just added a single line (#include "windows.h") rc file to a random ifort project then double clicked on it, and guess what error I get... Same if I add a new rc file to an brand new ifort project.

But from within VC++ projects and at the ifort command line I have no such problems.

After a spot of breakfast I shall investigate further...

On a relatively fresh XP VM with ifort 12.1.5 on top of VS2010 professional, things work (my test is simply to try and create a project using ifort's Windowing Application > Dialog Code template).

On a Vista machine, with a colourful history of installations and removals, the same test fails - when the integration tries to compile the rc file as part of the project creation process (presumably so that it can add the resource view) it complains about missing include files (winres.h). Bizarrely it will quite happily compile the rc file if I right click on it and select "compile".

On that same machine I can happily create a new VC++ project that has resources as part of the project template without any problems.

I have tried starting devenv from a command prompt that already has INCLUDE set to cover the relevant directories, but that doesn't seem to change the outcome.

Does the integration use rc.exe to do that initial compile - or is it a DLL-ised variant of the rc code? If the former, then i'll subvert the rc executable with a nefarious exe of my own design and see what the command line and environment is when it is invoked.

You lost me.

To test whether resources can be edited within a VC++ project start VS 2010. Choose File > New > Project. Expand the Visual C++ group under Installed templates, choose the Win32 sub-category and then select Win32 Project. Give the project a name in the Name entry field below the project type selection area, click Ok.

The Win32 Application Wizard should be displayed. Accept all default settings by clicking Finish. If you don't subsequently get any errors then it is working. To confirm, when the new solution has finished loading select View > Resource View. In the resulting pane expand the item corresponding to the new solution, then expand the item corresponding to the the name of the automatically created rc file for the project, then expand one of the resource categories (say the dialog category) and then double click on one of the child resource entries. Admire the resource in its special editor. If it is the "About" dialog you double clicked on then you could move dialog controls around...

To test whether resources can be edited using ifort I followed a similar process, but I expanded the Intel Visual Fortran group in the list of installed templates, selected the Windowing Application subcategory then chose Dialog Code. After clicking Ok (accepting the default project name) I get the pop-up that says the resource compiler has choked big time - and no resource view.

It doesn't appear that rc.exe is actually being invoked to create the binary representation of the rc file necessary for the resource view, so I was unable to diagnose further.

Very puzzled. Please install the most recent Windows SDK from the link I posted earlier and see if that helps.

Ok - that situation (VC++ resource editing works, ifort resource editing doesn't) is exactly what I get on my vista laptop. So you are not alone...

The repair seems to have helped a lot. But the error you now get is rather strange. Would you please copy and paste the actual error rather than retyping it (as you apparently did)? Also please attach the .rc file you are using (ZIP it first).

Thanks, I'll see what I can figure out.

Sorry, my system was giving me trouble last week. I also need the .h file generated by resedit.

Ok, this is progress.

First, I can also see the issue you had with windows.h - I am investigating that on the side.

The main problem here is that the resource editor doesn't like including windows.h, which pulls in a LOT of things, apparently some with symbols longer than it likes. Please replace the series of #include lines in grade.rc with:

#include "afxres.h"

and see if that's better.

Did you also remove the #include of resource.h? Put it back. Sorry, I was not clearer in my earlier post.

Remove these lines:

#include "richedit.h"

#include "commctrl.h"

Urg. Add back in the #include of commctrl.h

Or add this:

#define WC_STATIC "Static"