Project convertet generates boucoup bugs

[WSinc]

I was experimenting with the new VS 2010 that comes with build 7....

It works OK with new projects, but the problems arise when converting an older project
made with VS 2008 or earlier. They have a "project converter."

(1) I get messages saying "This was not compiled with debug information" or some such, and

(2) When it runs, it ignores console input entrirely. It will not step thru the program with
F10 for example, and READ * statements are also ignored.

(3) What does it mean by "cannot find PDB file?"

So, what do we do with older projects? Have to rebuild from scratch from the source code?

[Steven_L_Intel1]

I doubt the project conversion was the problem. It sounds to me as if you are trying to debug a Release build. Please be sure that the project configuration is set to Debug (it will say Debug in the toolbar) and rebuild the project. The PDB file is where debug information is stored.

[WSinc]

OK, will look at that, although I never used "release" for whatever I was testing. But shouldn't it still
recognize the console input for those as well?

Does this project converter also work for VS 2005 projects?

It's possible that one of those sneaked in there.

PS: I still haven't figured out how to attach a screen shot.
Does that require me to make a file out of it first, via Paintbraush, Draw, etc?

Also, when I copy a LICENSE file to my computer, where is it supposed to
be placed? The reason I ask is: that I can't find the Fortran licenses in the
computer when I already have an operational compiler and VS 200? going.

That's why I was wondering if they are "hidden" files.

Thanks; Bill S.

[Steven_L_Intel1]

The project converter supports VS2005 and even 2003 projects.

Yes, you need to make a file of a screenshot. There are many ways to do that. Windows 7 has a very nice "Clipping Tool" you can use for this purpose, there are a variety of free screenshot programs out there and you can paste into Paint or Word if you like. When saving the screenshot, please use GIF, PNG or JPG types, not BMP.

The licenses are files with the .lic file type and they are put in Program Files\Common Files\Intel\Licenses. That "Program Files" is "Program Files (x86)" on a 64-bit Windows system.

[WSinc]

I looked again, and the projectconfigurationis set to "debug."

Like I said before, I never used a RELEASE configuration with this particular program.

It ignores the console input, either while debugging or with READ statements.
For example, when I start without debugging, it skips over the READ statements entirely.

Another way I verified this, is that all the compiled relocatables were in the DEBUG folder, with theirassociated files as well.

This problem probably does not occur with graphics projects, so far as I can tell.

[Steven_L_Intel1]

It probably does not "skip over" the READ statements but instead reads from some other source, such as a file in your project folder or maybe if you specified redirection in the project property. Without being able to see your application and project, it is difficult for us to give you more detailed advice.

[WSinc]

HI -

I was looking over the Fortran 12 XE notes, under 'Moving and copying projects"
Apparently this process is fairly complicated, in fact too much so to quote right here.

I guess when you leave the project hierarchy in place, it does work better.
In other words, everything that was under "microsoft vs2008/projects" should STAY THERE.
Likewise for those under "microsoft vs2005/projects"

You have to ba very careful about moving projects around.

I invite the others to take a look, see what they think. Maybe we need something to better automate this proces (?)

Or just leave the folders alone. If it ain't broke, don't fix it - - -

[Steven_L_Intel1]

I am not sure what notes you are referring to.

Visual Studio solutions, with their projects, can be easily moved - just copy the folder. If you have created projects outside the solution folder, you may need to remove and re-add them for the new location.

For myself, I do not use the default locations for projects - I create a separate Projects folder in the location of my choice and put all my projects under there. This is independent of VS version. Once you create a solution in a new folder, VS remembers your selection and will default to the new location in the future.

[WSinc]

The notes I saw were downloaded with the documentation when the compiler was installed.
The topic is: "Moving and Copying Projects"

According to those release notes, you can't just copy a project anywhere you feel like
without taking a few precautions first.

Apparently if you don't then you see the problems I mentioned earlier.

It seems to work OK if I leave the projects where they were originally.