Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

Source files corrupted

Intel_C_Intel
Employee
588 Views
I now use SourceSafe with Visual FORTRAN to maintain the history and modification to source files. This combination however seems to result in the total corruption of the source file (the .f90 file) currently displayed by the editor when, during exection of the target program under visual studio, a BSOD occures. Whatever source progam Visual studio is displaying gets changed to all null's and the orginal .f90 is nowhere to be found. Visual Studio is set to save files before executing so the correct file should have been saved. This did not occur until SourceSafe was integrated with the compiler. As a workaround is there any way to make the Visual Studio editor make a backup copy?
0 Kudos
1 Reply
Steven_L_Intel1
Employee
588 Views
About all I can say is that we've known of many people using VSS with CVF and have never seen such a problem. Here, all the code is Microsoft's - including how Developer Studio integrates with VSS. It's no different than using Visual C++.

Any time a BSOD happens, any open file is likely to be corrupted. In fact, I have a W2K partition on my home machine that is now unbootable because of one too many BSODs. I don't know how the use of VSS plays into the problem you're having - I'm puzzled that anything that happens before a checkin corrupts the store.

Steve
0 Kudos
Reply