Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Why would VSS change the checkout folder to temporary?

7 views
Skip to first unread message

Mike Faynberg

unread,
Nov 4, 2009, 10:30:01 PM11/4/09
to
Hello everyone,

Recently we started experiencing a strange SourceSafe (Ver. 8.0 / VS2008 /
WindowsXP) glitch. When a file is checked in (I did not figure, what files it
happens with, and what does not). the Check Out Folder gets changed on its
own - and the new folder is a Folder for Temporary Files as defined in the
VSS options.
What could happen?

Thank you in advance,

Mike

Catherine Sea

unread,
Nov 9, 2009, 2:02:36 AM11/9/09
to
Hi Mike,

I've never encountered such problem. What steps did you took before
the issue happened?

Sincerely,

---------------------
Catherine Sea
http://www.dynamsoft.com
http://www.scmsoftwareconfigurationmanagement.com

Mike Faynberg

unread,
Nov 11, 2009, 7:23:01 PM11/11/09
to

Hi Catherine,
and thank you for your reply.
What happens looks like this. When a file is being checked in, the
SourceSafe sometimes needs to merge it - and in some situations it does it
automatically, not utilizing the user's input - just reporting that the file
was merged, and requesting the user's approval for saving the merged file.
When the user agrees to check in the merged copy, the Source Safe does the
job, but - again sometimes - it replaces the current file Checkout directory
with the one specified in the options as the temporary folder... At this time
no more details unfortunately.
Oh, by the way there is one more strange problem: it often happens that
checkin simply does not work. You choose to check-in, press the OK button -
and nothing - the check-in does not happen.
Any ideas?
Thank you again,

Mike


"Catherine Sea" wrote:

> .
>

Mark Tolonen

unread,
Nov 12, 2009, 9:57:07 PM11/12/09
to

"Mike Faynberg" <MikeFa...@discussions.microsoft.com> wrote in message
news:C60DF0B7-011F-4552...@microsoft.com...

Are you using Visual Studio 2008 source control integration? Visual
SourceSafe 2005 requires the Visual SourceSafe 2005 Update to work correctly
with Visual Studio 2008. This may be the cause of your problems.

-Mark

0 new messages