Problem Saving resource file IVF Visual Studio 2008 in Windows 7

[dannycat]

I've recently "upgraded" my laptop the Windows 7 Professional from Vista in the hope that I might get a more robust operating system and a slight increase in performance. I used to use CVF to compile my main fortranapplication but had a parallel IVF workspace solution set up using the same source files mainly for creating a64 bit version of the program. I stuck with CVF as it provided a more robust (under Vista) environment in which to develop the code. However as everyone is probably aware CVF does not work all at on Windows 7 so I have finally given up on it and will have to continue future developments using IVF and Visual Studio 2008. So far so good. The upgrade prcoess took longer than expected (all weekend in fact) but when I finally got everything reinstalled I hit a few snags. (Note: I did not need to copy my data during upgade process which was an unexpected surprise).

Firstly I tried the build the solution but ran into problems with projects that were associated with C libraries. The .lib files could not be read during linkingi.e.none oflibrary objects could be resolved by the linker,(or even overwritten when I tried a rebuild)by the compiler/lib process. I had to delete the .lib files explicity and then rebuild.

Secondly, and this is my current difficulty, when I modify a dialog resource by copying and pasting a control from another dialog in the same file (something I did quite often, in Visual Studio 6,to avoid changing the resource.fd/resource.h files)I cannot save the .rc file either under its original name nor any alternative name. If I just change an existing control (say by dragging it around) the .rc file can be saved. I've tried running as administrator, renaming files, resetting secuity attributes all to no avail. It possiblysuggests that new resource.* files are being read or written and for some reason this actioncannot take place. A similar issue to that I mentioned above regarding .lib files. I am assuming this is a Windows 7 issue because I never actually used VS2008 for resource editting under Vista.

Has anyone else experienced this problem switching to windows 7 and if so what is the best solution?

As always any help would be appreciated, thanks in advance.

[Steven_L_Intel1]

What is the path to your project directory? Try copying the project/solution directory to your desktop and opening it from there.

What was the exact error message you got regarding the libraries?

[dannycat]

Hi Steve, a belated Happy New Year to you.

Regarding the libaries when I first tried to build the solution I got lots of "unresolved external" errors relating to object procedures within the "parent" fortran library (related to "child" C library). This did not happen with straight forward fortran libraries. Howeve when I tried to clean and rebuild the project containing the C libraries I got a message stating that the .lib file could not be created in LINK.

Regarding the resource problem; I have since tried simply adding a new control (check box) to a dialog and then renaming it to an existing ID. (From IDC_CHECK1 to IDC_OFFS). In CVF this would usually cause the resource.fd file to be modifed and therefore virtually every file in the solution would have to be rebuilt as they are directly or indirectly dependent upon the resource.fd file. To my surprise this did not happen in IVF/VS9 which suggests that either the developer environment is clever enough not to change the resource.fd/h files until the user saves the .rc file (which DID save OK by the way) and it has reason to change the fd file (By adding a new control ID for example) or there is still something wrong happening which is preventing these files being changed/saved as in CVF/V6.

I am also getting a multitude of warnings from linking 32 bit debug version:

2>LIBCMTD.lib(stricmp.obj) : warning LNK4099: PDB 'libcmtd.pdb' was not found with 'C:\Program Files\Microsoft Visual Studio 9.0\VC\lib\LIBCMTD.lib' or at 'C:\Win\FEM2000-32\Debug\libcmtd.pdb'; linking object as if no debug info

What do these mean?

[Steven_L_Intel1]

Those warnings are not normal, and I admit to being a bit puzzled as to how you are getting them. Can you attach a buildlog.htm from a rebuild where these occur? They are harmless, but...

[nvaneck]

I don't know if this sheds any light on it, but I've found I have to run the deftofd command separately after adding a new control and before building the project. This is not required if I only change existing control names and text.