Previous Discussion	Next Discussion

Visual Source Safe issue -- pretty urgent Ok, here's the problem: First, I MUST use Visual Source Safe (company decision, not mine). Anyway, I can check out a file (using the VSS Editor) and edit it. But when I check it back in, the changes aren't applied to the checked in file. I have to have a co-worker do a check out/check in for the changes I made to take effect. What could be the problem? This is kind of an urgent matter, as I have been having this co-worker check out/in several times per day, and it's probably starting to drive both of us batty. Started By Monte on Jan 27, 2011 at 10:30:50 AM

4 Response(s) | Reply

Earlier Replies | Replies 1 to 4 of 4 | Later Replies

brian on Jan 28, 2011 at 12:38:15 AM (# 0) This message has been edited. Can't say I've ever encountered this but it could be the location of the files. Have you confirmed before check-in that the file you are indeed checking in is the one you've changed. Are you checking in via Visual Studio or the VSS client? I have to say I hated VS but my new job, it kinda became necessary to use it. As long as you steer clear on design view it is a really powerful tool. 2010 in particular is great. I never would have thought I'd use studio but have been converted... Monte on Jan 28, 2011 at 5:59:50 AM (# 1) I'm using the VSS client. What's interesting about the problem is that I can check out a file, make a change, check the file back in, then check it back out, and the change is there in VSS, it just doesn't seem to take effect when I check it through the web browser. I have to get a co-worker to check it out and back in after I do for any changes to take affect. brian on Jan 31, 2011 at 12:51:03 AM (# 2) Sounds like a config issue on the VSS server/repository or possibly the web interface although I've not used VSS for a while and don't ever remember it having a web interface. If a colleague can check out or access your changes they are in there. If the web thing is a third party tool it is most likely that. We had loads of issues with third party stuff since they locked the repository for backup and things like that. we almost lost our entire set of source code because of that one. These days using SVN which has its own issues but is better. brian on Jan 31, 2011 at 12:57:00 AM (# 3) Sounds like a config issue on the VSS server/repository or possibly the web interface although I've not used VSS for a while and don't ever remember it having a web interface. If a colleague can check out or access your changes they are in there. If the web thing is a third party tool it is most likely that. We had loads of issues with third party stuff since they locked the repository for backup and things like that. we almost lost our entire set of source code because of that one. These days using SVN which has its own issues but is better. Monte on Jan 31, 2011 at 7:21:37 AM (# 4) Ok...let me be a bit more clear. When I edit the file and check it back in, I'm checking it into our development server. So when I pull the HTML up in the browser, I mean the development file. The file is a JavaScript file within an HTML file.

Earlier Replies | Replies 1 to 4 of 4 | Later Replies

To respond to a discussion, you must first logon.

If you are not registered, please register yourself to become a member of the SiteExperts.community.