Migrating Legacy Compaq Projects Problem

[mattintelnetfort]

I have been wrestling with a problem for several days now. I have a Visual Studio workspace that I am migrating from Visual Studio 6 with C++ and Compaq Fortran to Visual Studio .NET (unmanaged C++) with Intel Fortran 9.X. The legacy workspace has 25+ projects. Each project contains C++, or F77, or F90 source files but only one type of the three per project. The Fortran projects of which there are about 15 projects contain a total of about 1000 source files. All of the Fortran projects build static libraries except one which combines all static libraries into a single DLL that then is a dependency of some of the C++ DLLs in the workspace (migrated solution). I migrate each of the fortran projects within the migrated solution in Visual Studio .NET (using the "Extract Compaq Visual Fortran Project Items" operation),but when I get to the last few projects I can no longer save the solution without receiving the following error message - "The options file 'd:SampleSampleprojectSampleproject.suo' was not written successfully. Check that the location is available, the file is writeable and there is enough room on the disk". When I get to this point and try to save my solution and close Studio, it crashes and I have to remigrate all over again. I've done my projects in several orders and all seem to collapse at the tail end (possibly indicating an upper limit on number of files). Any thoughts would be appreciated, I have little time left to spend on this.

[Steven_L_Intel1]

Once you convert an individual project, you should not have to convert it again.

Try this. Create a new blank solution. Add the already-converted Fortran projects (.vfproj files) to it. Save the solution. Now reopen it, add one of the unconverted projects, convert it, then save and close. Repeat until all done.

I have not heard of this problem before. I do know there was an issue some time ago with lots of Fortran projects taking lots of virtual memory, but I think that was solved a few months ago, so be sure you are using a recent version of the compiler and its VS integration.

[mattintelnetfort]

Thanks for the input, I will try your suggestion. I do see that if I remove the problematic ".suo" file after it complains with the error described, the source file explorer no longer has the "Fortran" icon associated with each migrated fortran project in the project explorer of Studio. I also see that I do not have access to the Fortran compiler options until I remigrate the projects.

Also, what is the latest version of the Fortran compiler available that plays nice with Studio 2003? And when is the Studio 2005 compatible compiler available?

Again thanks!

[Steven_L_Intel1]

The .suo file should be entirely optional. It will get recreated automatically. You should be able to add .vfproj files as existing projects.

The latest version is 9.0.030. The version supporting VS2005 is due in early May.