How do I connect Visual Source Safe to CVI 7.1

[ljstrick]

I have a project in VSS that I am trying to connect to with CVI. I can check in/out manually and with SlickEdit just fine but CVI refuses to connect. It seemed to be easier with 6.0 than it is with 7.1. I've read thru the various threads here and have found anything that lets this work. I am using VSS 6.0d. This project was previously connected but we needed to reconfigure the directories and some of the files and we haven't been able to get it connected again.

I have started with a fresh VSS project, added the files to VSS, created a new CVI project (left it "Untitled"), edited the project, connected to VSS, selected create (and change), selected the VSS project, selected existing and non-existing directories, set admin as the user name and none of these have created a project with connections with VSS (most have done absolutely nothing).

Lloyd

[Charlie S.]

Hello Lloyd,

Are you receiving any errors at all (under Window >> Source Code Control Errors)? Have you taken a look at this thread?:

http://forums.ni.com/ni/board/message?board.id=180&message.id=14432&requireLogin=False

We've done some testing with source safe and shown it to work -- I will have to double-check the version, though. Let me know if the steps in the thread above help at all.

Thanks!

[ljstrick]

Yes I tried the thread you mentioned, the instructions are for CVI 6.0 but I made the proper substitutions in 7.1. I know it works, I have a previous instance of this same project working, we needed to modify the destination directory and add some files along with changing the project name. This is when it broke.

Lloyd

[ljstrick]

It looks like something gets corrupted or not updated sometimes, I created a new workspace and project in CVI. I was able to connect that project to VSS. I was then able to add the original project to the new workspace and could connect to VSS again (even after getting rid of the new project). I did a comparison of the two workspaces and found that under [SCC Options 0001] the local path was wrong (though all the files were referenced in the right directory). I manually modified this entry to match what VSS had and it all started working again. It seems that Labwindows doesn't read what VSS is saying is the working directory if something already exists in the path variable there.

Lloyd

[Charlie S.]

I'm glad to hear you got it to work! That's good information to know. I'll make a note of what you did to fix in case we come across something similar in the future.

Thanks for posting the solution!