Issue(s): No Auto-Checkout & Icons not visible in VS 2010

[dmoring]

New upgrade from v4 (single user) to v5.1. Issues are on Win 7 Ult running VS 2010 and v5.1 Integration (Vault Client)

Issue 1:When editing a file, no auto-checkout occurs - so when trying to save, it errors showing the file as read-only. A Manual Checkout appears to work fine. Options > Source Control > Vault Options > Integration Options set to "When Checkout is Required on Edit: Auto Checkout"

Issue 2: Icons for check-out status are not displaying at all next to each file.

Thanks for any advice on how to fix!

[Beth]

Was Vault installed after VS 2010 or before?

Were you working with this project on this exact same machine previously?

[dmoring]

Was Vault installed after VS 2010 or before?

Vault Client (v4.x) was installed when VS2010 was installed - then Vault v5.1 was installed after both.

Were you working with this project on this exact same machine previously?

I don't know if it was checked out on this exact machine (the machine was recently completely reslicked with Win7) before, but the Project was a VS2005/Vault v4.1 project previously.

[Beth]

It sounds like it would be good to make sure the bindings are still good first. Since you were able to choose the option for auto-check out, I'm assuming you are using the Vault Classic Client. If that's not correct, let me know.

In Visual Studio, with your project open, go to File - Source Control - Change Source Control. Select all the lines in the window that opens and click Unbind, then click Ok. Save All. Then return to File - Source Control - Change Source Control. Select one line that represents a project and not the .sln file. Click Bind and follow the wizard to bind. If you get a valid status after binding that line, select the other lines, one at a time and bind each. Bind the .sln file last. Then click Ok and check in any changes.

Then check your settings one more time for auto-check out to make sure it's set and let me know your results when you try editing a file.

[dmoring]

It sounds like it would be good to make sure the bindings are still good first. Since you were able to choose the option for auto-check out, I'm assuming you are using the Vault Classic Client. If that's not correct, let me know.

No - I am (and believe was in VS2005?) using Enhanced Client!

In Visual Studio, with your project open, go to File - Source Control - Change Source Control. Select all the lines in the window that opens and click Unbind, then click Ok. Save All. Then return to File - Source Control - Change Source Control. Select one line that represents a project and not the .sln file. Click Bind and follow the wizard to bind. If you get a valid status after binding that line, select the other lines, one at a time and bind each. Bind the .sln file last. Then click Ok and check in any changes.

Then check your settings one more time for auto-check out to make sure it's set and let me know your results when you try editing a file.

Done and now the issue of the icons seems to be solved (thanks!), BUT any new editing of a document in VS2010 does NOT perform an auto-checkout of the file, but marks it as "Renegade" until it has been checked out at least once. For this project, I checked 'em all out - then back in, but is there a way to not have to do this? A few projects are pretty big!

[Beth]

This isn't normal behavior. Are all users using the Vault Enhanced Client? All users need to be using the same client.

I don't think the Enhanced Client doesn't have a check-box for auto-check out, which is why I thought you were using the Classic Client.

If you would like me to take a closer look, you could send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread. We will be closed for the holiday, but will be back on Monday.

[dmoring]

This isn't normal behavior. Are all users using the Vault Enhanced Client? All users need to be using the same client.

I don't think the Enhanced Client doesn't have a check-box for auto-check out, which is why I thought you were using the Classic Client.

If you would like me to take a closer look, you could send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread. We will be closed for the holiday, but will be back on Monday.

Thanks Beth - I will take a screenshot to show and post. There is only one user and really only one dev machine, but its the one we just upgraded to 5.x/VS2010.

[Beth]

I don't recall receiving the screenshot through email or on the forum. Did you need further assistance?

[madNBad]

We're kinda experiencing the same problem.
Here are the facts. Server 5.0.4.18845 with 2 user licenses.
I was using client version 5.04 and my manager was using client version 5.1
All the projects that I had in VS2008 worked fine, check-ins, check out etc but I was the only one accessing those projects.
However, a web project in VS2010 where we both have access to it and tried to modify files is a extreme pain in the neck.
We were both using vault enhanced client in our development environment.
Problem 1
When I check out a file...and start modifying it, it will mark it as renegade.
Then I cannot check in my changes.
I had to go to the web client and log in as admin to do undo-check out.
Problem 2
I right click on a file, select check out, make some changes and now the icon says..file is up-to-date.
although I already modified the file.
Close VS2010, open the Vault client and the file seems check out by me but it says Renegade.
Then I have to go back to the web admin console to undo-check out.
My project is bound since it prompts me to login when I open it.
But for every file I try to modify it shows the wrong icon (either the little user or the blue flag) instead of the red check mark.
Now..my project file (not solution file) is a renegade but I did that on purpose because I needed to change some references, but I
don't think that is an issue.

Trying to resolve the problem:
We both upgraded to client 5.1.2....my manager can check out/check-in/edit the files for that web project but I'm experiencing the same behavior as before.
At this point I'm just frustrated and only god knows if my VS2008 projects are going to work now that I upgraded the client.

Any help would be greatly appreciated.

[Beth]

Are the solution files checked in? The Vault Enhanced Client will behave strangely if the .sln is not checked in.

[madNBad]

Are the solution files checked in? The Vault Enhanced Client will behave strangely if the .sln is not checked in.

Thank you for your prompt reply.
Solution file is checked out by my manager.

I'll ask him to check in the solution file, we'll try again and let you know the outcome of this.

So in order to avoid this problem we have to make sure the sln file is checked in at all times?

[Beth]

It's not a question of whether the solution file is checked in, but whether it's in source control at all and bound.

If you have to force an undo check-out so that you can check out a file, then the other user could be using an exclusive lock on the file. What types of files go renegade? Are those files exclusively checked out?

[madNBad]

It's not a question of whether the solution file is checked in, but whether it's in source control at all and bound.

If you have to force an undo check-out so that you can check out a file, then the other user could be using an exclusive lock on the file. What types of files go renegade? Are those files exclusively checked out?

Project and Solution files have both valid bindings with Vault.
The other user is not even touching the files I'm trying to check out. Exclusive lock on the files is exactly what we want cause we work on different files at a time. The problem is..I check out, make changes, files becomes renegade and I cannot check back in.
Renegade file is extension .cs (C#)

[Beth]

Earlier you said you had to force an undo check out on the solution file for the other person who had that one checked out. Is that file, or possible a proj file, checked out by your or anyone else each time a file becomes renegade?

What are your default actions that are set under Vault Tools - Options - Local Files?

If you perform a refresh on Vault, is anyone else touching that file before you try to check it out?

[madNBad]

Hi Beth,
what I said before is that I had to force undo-checkout on a .cs file (C# code not project or solution file) that I checked out myself and becomes renegade right after I modify it.
Again, nobody is using that file, we are only two developers here.
My default options for local files are:

Modified working copy->Attempt automatic merge
[ ] Prompt before overwriting..
[X] Save files in backup folder before overwriting
[ ] Perform file deletes in working folders

Perform Repository deletion locally->Remove working copy if unmodified

Make writable->Make all files read only
Set File time -> current
On undo check out -> Revert
Override NAtive EOL Type-> Do Not override

[ ] Detect modified files using CRCs.....


Thanks for all your help and I apologize if my first posts were confusing.
FYI: we just upgraded today from 5.0.4 to 5.1.2 on the server.
We'll see if the strange behavior still persists.