Sourcesafe issue/mystery

[LFCfan]

My colleague (SI) and I (MP) are both working on the same solution, using VSS.
For some reason, whenever I check out a file, it shows in sourcesafe as being checked out to SI rather than MP. If I restart my machine without checking all my work in, when I reload Visual Studio, I can't keep working on the file that I'd been working on, because Visual Studio thinks it is checked out to SI!

Does anyone know where Visual Studio keeps information locally about which Sourcesafe user it thinks you are?


~LFCfan

 

[jmeckley]

this forum is related to asp.net not versioning. try forum722 instead.

Jason Meckley
Programmer
Specialty Bakers, Inc.

 

[LFCfan]

Thanks for taking the time to respond.

I posted here because it was more of a Visual Studio question than a version control one - it seems Visual Studio is picking up the wrong login info, sees that a file is checked out to SI, somehow believes that I am SI and checks a file out to me erroneously.

~LFCfan

 

[LFCfan]

I have made a new thread in the VSS forum:
thread722-1452964

~LFCfan

 

[LFCfan]

Solved:

http://blogs.infosupport.com/raimon...use-the-correct-login-ID-for-Source-Safe.aspx

It says VS2003, but what he tried worked for my issue on VS2005

Persuading Visual Studio 2003 to use the correct login ID for Source Safe

I had an interesting issue where somewhere in the past I had used the guest account inside Visual Studio to connect to Visual Source Safe. However, since then, Visual Studio remembered this login ID.

It is visible using Tools->Options->Source Control->SCC Provider and it showed "guest" and was disabled.

Today I wanted to access this database using my own account, only Visual Studio stubbornly kept using the guest id.

I already had used the SSUSER environment variable to set the correct user; but although this makes the VSS explorer use the correct user, in this case it did not help to select the correct user for VS 2003.

In the end I performed this trick to make it work:

1. Temporarely rename the "wrong" ID (in this case 'guest') to something else.

2. Restart Visual Studio and open te source controlled project

3. Visual Studio will ask for an ID and Password because the one it knows does not work

4. Fill in the correct ID and password.

5. Close Visual Studio

6. Rename the "wrong" id back to its orgininal name.

This is the way it has worked for me; although I'd rather see a better solution for this problem....

~LFCfan

 

[jmeckley]

Visual Studio question than a version control one

ok, but this forum isn't about VS either, it's about asp.net.

remember to use the forum search box at the top of the screen to search for the forum which most closely matches your category.

Jason Meckley
Programmer
Specialty Bakers, Inc.

 

[LFCfan]

I looked through the forum list, couldn't see a specific VS one.
Apologies.

~LFCfan

 

[ca8msm]

There isn't a specific one for VS, so you've probably got the closest match you could of had in using this or the VSS forum.


-------------------------------------------------------

Mark,
[URL unfurl="true"]http://aspnetlibrary.com[/url]
[URL unfurl="true"]http://mdssolutions.co.uk[/url] - Delivering professional ASP.NET solutions
[URL unfurl="true"]http://weblogs.asp.net/marksmith[/url]

 

[LFCfan]

Thanks ca8msm, that's what I thought too.


~LFCfan