MSSCCI client issue under VS2008

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
dist0rti0n
Posts: 112
Joined: Mon May 01, 2006 10:50 pm
Location: Birmingham, AL

MSSCCI client issue under VS2008

Post by dist0rti0n » Thu Jan 17, 2008 8:12 pm

[Admin Edit: Moved from the 4.1 Beta Forum]

Thanks for the reply, Ian.

The problem they reported to me is more of an annoyance than an actual bug, but when you have a Web Site or Web Application project bound with the 2003 client in Visual Studio 2008, whenever you edit a file (a code-behind in particular) there will be a dialog that pops up saying something to the effect "Error checking out file <file path>, you already have that file checked out." I believe the developers have the option to check out on edit enabled.

Please let me know if I need to report this in a different forum.

Thanks!
<a href="http://www.vertagen.com">Vertagen Solutions</a>

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Fri Jan 18, 2008 8:14 am

Do you know the state of the file's read-only attribute at the time the user begins the edit?
Jeff Clausius
SourceGear

dist0rti0n
Posts: 112
Joined: Mon May 01, 2006 10:50 pm
Location: Birmingham, AL

Post by dist0rti0n » Fri Jan 18, 2008 7:18 pm

I'm fairly certain the read-only attribute is set.
<a href="http://www.vertagen.com">Vertagen Solutions</a>

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Mon Jan 21, 2008 8:35 am

Is it possible the file's read-only attribute is set, and you DO have the file checked out?

In either case, I"ll make a note of this and we'll see if we can re-produce anything as we'll be planning some changes in this client in an upcoming release.

If you do come up with something with reproducible steps to recreate the behavior, please update this thread.

Thanks.
Jeff Clausius
SourceGear

dist0rti0n
Posts: 112
Joined: Mon May 01, 2006 10:50 pm
Location: Birmingham, AL

Post by dist0rti0n » Mon Jan 21, 2008 4:23 pm

This may not be an issue worth persuing since the team members have since upgraded to the 1.1b2 client, which fixes the issue and simultaneously destroys my test case :|
<a href="http://www.vertagen.com">Vertagen Solutions</a>

jclausius
Posts: 3706
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Mon Jan 21, 2008 4:29 pm

No problem. Thanks for the initial report.
Jeff Clausius
SourceGear

jbgoode
Posts: 2
Joined: Mon Sep 11, 2006 8:11 am

we've been having this problem too...

Post by jbgoode » Fri Feb 29, 2008 9:41 am

We're using Vault 3.1.9.

I tried to eliminate some of the possible causes you outlined above. I unbound the project in VS08, got the latest version of all the files in the project with the vault client, and then rebound the project in VS08. I chose to allow source control to silently overwrite the files in the resulting dialog.

I went to a file, edited something, and got the dialog that warned me I already had the file checked out. If I click OK and proceed, everything works fine.

I'm using the option to detect modified files using CRCs instead of modification times (for files smaller than 10MB), if that helps.

Thanks!

Post Reply