Sorry - correction to my previous answer

hi.

i have a solution with 40+ projects in it. allmost every time i add a new project, check out a file or do a 'get latest version' one of the projects gets checked out automatically. (its allways the same project). the output window has a message that says 'project nameOfProjectHere was checked out automatically for editing'.

however, nothing has been done to that project. none of the files in the project have been changed for ages. the project itself has not been touched for ages.

why is it getting checked out automatically all of the time any ideas

WM_THX
thomas woelfer
http://www.die.de/blog

Answer this question

Sorry - correction to my previous answer

beaker101
Alin,

i have done this for several times. (that is, i allowed the checkout, saved everything, and checked the project back in.)

it's still beeing checked out the next time i add a new project to the solution.

any other ideas

WM_THX
Sam43
Alin,

thanks!

WM_CHEERS
-thomas woelfer
groves
Alfredo,

we're using the version of vss that came with beta 2 of vs2005. the plug-in is 'Microsoft Visual Source Safe'.

WM_THX
thomas woelfer
cjpa15
It is possible to be a bug in the project system.

It sounds like the project is calling QueryEdit to change/update some setting in the project file and the scci checkout the file (the automatic checkout is controlled from Tools/Options/SourceControl/Environment/OnEdit...Automatically checkout the file)

For the beginning, I would allow the checkout, save everything, then use File/SourceControl/Compare command on the project file to see what differences are from the server version. If the difference makes sense, I would checkin the file, and hopefully the next time you do the get the project will not try to update again the project file.

Alin
simran
Hi Thomas,

Are you using by any chance VC projects (managed or native)

If yes, there was a known Beta2 issue that caused this behavior. Here are the related Whidbey bugs:
452794 (Remove the code from VCProject.dll and VCProjectEngine.dll that supports ClickOnce but maintain the ability to read vcproj file that the ClickOnce section)
455063 (ScciCpp and ScciMC suites fail in Beta2 branch, Lab22dev and soon to be RI into VsCore)
They didn't meet the bar for fixing in Beta2, but they were fixed after that and the fix should be visible builds more recent than April.

If you're using a different project type (vb/C#), I'd recommend opening a bug against that project type. I have no idea why the project system insists on adding that <VisualStudioProject> tag and checking out the project file, but that'a a bug in the project.

In any case, I would checkin the modified project file, perhaps that will "convince" the project to stop checking out the file anymore (I suspect that next time the project will be open the project will find the tag there and won't checkout the file again).

Alin
EVH
What version of Visual Studio are you using
What is the Source Control plug-in that shows this behavior
BogdanZ
i just had that problem again, and checked again. well, there _is_ a difference:

in the <VisualStudioProject> tag, one version says SignManifests=true, the other version doesn't have this entry.

however, nobody has touched the project. it seems, this entry is beeing written automatically - and this causes the change. however, i have no idea what causes this to be written... any ideas whats happening here. (i don't even know what 'SignManifests' means.)

WM_THX
thomas woelfer
http://www.die.de/blog
Sorry - correction to my previous answer

Answer this question