Changes in vfprof files

[a_leonard]

Just curious. Have the settings "MustRebuild" and "SwitchesHaveChanged" disappeared from the vfproj files with IVF 10? After making some changes and saving the project files, I don't see them anymore.

[Steven_L_Intel1]

Lots of things change with project files in version 10, mainly to help people who save projects in source repositories such as SourceSafe. In previous versions simply opening a project and closing it would cause the project file to change and rearrange the order of things. There are also some keywords that were used in 9.1 that are no longer used in version 10 though I do not know a complete list.

I hesitate to ask: why do you care?

[a_leonard]

I am one of the persons that complained about the project files being rearranged, so I'm glad it has been changed. My more general question is really: Are there any differences in the project files that are important? Everyone else I work with has is still using 9.1. Can we still share the project files or do I need to get everyone else to upgrade?

Should we expect any differences in results in codes compiled with 9.1 vs 10.0 (with default optimization settings)? I have some co-workers that are hesitant to change without a really good reason.

[Steven_L_Intel1]

I know of one issue if you use a project file saved in 10.0 with 9.1 - it loses the "compile only" setting and you have to manually add /c to the "additional options".

As for differences in results - you can get that any time the instruction sequence might change due to better optimization or library changes. If you are expecting bit-for-bit same floating point results, you MAY see some minor differences. It depends on the application. The "really good reason" is that we fix bugs. But you can have 9.1 and 10.0 installed and switch among them in Visual Studio - this is the mode I would recommend while you are deciding.