- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm continuing to have difficulty with fortran projects and sourcesafe and have the following questions:
1) Is sourcesafe version 6.0 compatible with Intel Fortran 9.1 and Visual Studio 2005? Do I need an upgrade?
2) Is there a way to reset the sourcesafe connection on fortran projects such that they rebind to the appropriate directories.
3) Must the project files be checked out in order to open and close the solution in Visual Studio 2005? Since I added the new VFProj files to sourcesafe, Visual Studio crashes whenever I close the IDE.
I'm unable to open a solution with fortran project files (vfproj) without agreeing to work disconnected.
Link Copied
4 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have always found the binding of VSS and VS (of any version) quirky.
For what it's worth, the most reliable way of re-establishing it (and there are seldom problems afterwards) is:
- delete all .opt, .suo, .vss, .vspcc etc files from the solution directory (i.e. whatever you cannot recognize)
- delete .vspcc files from VSS storage
- Get the latest version from VSS user interface
- Open the .vfproj and .sln files manually in a text editor and fix the VSS database bindings manually (this step is also advisable when you create VSS branches or move projects in VSS -- branching a .dsp/.dsw/.vfproj/.sln file to another VSS folder still keeps the binding to project within the file).
- Open the solution in VS and hope for the best.
For what it's worth, the most reliable way of re-establishing it (and there are seldom problems afterwards) is:
- delete all .opt, .suo, .vss, .vspcc etc files from the solution directory (i.e. whatever you cannot recognize)
- delete .vspcc files from VSS storage
- Get the latest version from VSS user interface
- Open the .vfproj and .sln files manually in a text editor and fix the VSS database bindings manually (this step is also advisable when you create VSS branches or move projects in VSS -- branching a .dsp/.dsw/.vfproj/.sln file to another VSS folder still keeps the binding to project within the file).
- Open the solution in VS and hope for the best.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Intel Fortran doesn't generally know nor care about source control, as that is handled by Visual Studio. A brief look at Microsoft's web site suggests to me that VSS6 is not supported in VS2005, and that there is a new SourceSafe 2005 product which is supported in VS2005.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
VSS6 works fine for me in VS2005? I didn't test it extensively, as I received it few days ago, but it inherited VSS bindings of an ole project correctly, check-in/check-out work etc.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok - I couldn't get my copy of VS2005 to see VSS6. The Microsoft web site is rather vague on this topic.

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page