VSTS/DevOps: Hidden file checked out to another workspace
up vote
0
down vote
favorite
I am having an issue where a .cs class in my entity framework (edmx) is checked out in another workspace, but doesn't exist in TFS:
When I attempt to add the file to TFS I get:
TF10151: Cannot lock item $/[...]/CLP.cs for check-out. The item $/[...]/CLP.cs is checked out by [User] in workspace [Workspace].
The checkout does not show in TFS Sidekick Status and I have even tried the following command using Developer Command Prompt but I get 'It is not currently locked in your workspace':
tf undo "$/[...]/clp.cs" /collection:[My Collection] /workspace:[Workspace];[User]
Any idea? The workspace in question goes back a year or so for somebody who no longer works for the company. Seems like it's a ghost file that TFS has some sort of reference to but doesn't actually exist? Perhaps it's getting confused with the edmx file?
Any fix or work around would be much appreciated as it's stopping us from using automated builds.
Thanks
entity-framework tfs
azure-devops asked Nov 20 at 10:35
Andrew Dally
1
add a comment |
up vote
0
down vote
favorite
I am having an issue where a .cs class in my entity framework (edmx) is checked out in another workspace, but doesn't exist in TFS:
When I attempt to add the file to TFS I get:
TF10151: Cannot lock item $/[...]/CLP.cs for check-out. The item $/[...]/CLP.cs is checked out by [User] in workspace [Workspace].
The checkout does not show in TFS Sidekick Status and I have even tried the following command using Developer Command Prompt but I get 'It is not currently locked in your workspace':
tf undo "$/[...]/clp.cs" /collection:[My Collection] /workspace:[Workspace];[User]
Any idea? The workspace in question goes back a year or so for somebody who no longer works for the company. Seems like it's a ghost file that TFS has some sort of reference to but doesn't actually exist? Perhaps it's getting confused with the edmx file?
Any fix or work around would be much appreciated as it's stopping us from using automated builds.
Thanks
entity-framework tfs
azure-devops asked Nov 20 at 10:35
Andrew Dally
1
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am having an issue where a .cs class in my entity framework (edmx) is checked out in another workspace, but doesn't exist in TFS:
When I attempt to add the file to TFS I get:
TF10151: Cannot lock item $/[...]/CLP.cs for check-out. The item $/[...]/CLP.cs is checked out by [User] in workspace [Workspace].
The checkout does not show in TFS Sidekick Status and I have even tried the following command using Developer Command Prompt but I get 'It is not currently locked in your workspace':
tf undo "$/[...]/clp.cs" /collection:[My Collection] /workspace:[Workspace];[User]
Any idea? The workspace in question goes back a year or so for somebody who no longer works for the company. Seems like it's a ghost file that TFS has some sort of reference to but doesn't actually exist? Perhaps it's getting confused with the edmx file?
Any fix or work around would be much appreciated as it's stopping us from using automated builds.
Thanks
entity-framework tfs
azure-devops asked Nov 20 at 10:35
Andrew Dally
1
I am having an issue where a .cs class in my entity framework (edmx) is checked out in another workspace, but doesn't exist in TFS:
When I attempt to add the file to TFS I get:
TF10151: Cannot lock item $/[...]/CLP.cs for check-out. The item $/[...]/CLP.cs is checked out by [User] in workspace [Workspace].
The checkout does not show in TFS Sidekick Status and I have even tried the following command using Developer Command Prompt but I get 'It is not currently locked in your workspace':
tf undo "$/[...]/clp.cs" /collection:[My Collection] /workspace:[Workspace];[User]
Any idea? The workspace in question goes back a year or so for somebody who no longer works for the company. Seems like it's a ghost file that TFS has some sort of reference to but doesn't actually exist? Perhaps it's getting confused with the edmx file?
Any fix or work around would be much appreciated as it's stopping us from using automated builds.
Thanks
entity-framework tfs
azure-devops entity-framework tfs
azure-devops asked Nov 20 at 10:35
Andrew Dally
1
asked Nov 20 at 10:35
Andrew Dally
1
asked Nov 20 at 10:35
Andrew Dally
1
asked Nov 20 at 10:35
Andrew Dally
1
asked Nov 20 at 10:35
Andrew Dally
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
If the developer no longer works for the organisation then you can just delete the workspace.
You will probably need project administrator permissions to do this.
This question has a bunch of answers that should show you how to do this
answered Nov 20 at 10:50
James Reed
12k4155
Worked great, thanks. Didn't think just to delete the Workspace. Quite odd the file didn't show up as being checked out though
– Andrew Dally
Nov 20 at 15:04
It might have been as Pending "Add" so TFS knew about the file and it's name but it had never actually been checked in. Or perhaps a delete and add. Server workspaces can be a pain sometimes
– James Reed
Nov 20 at 17:02
Ah, that may explain it as I don't actually recall ever seeing it in TFS since we moved. Thanks again
– Andrew Dally
Nov 22 at 12:25
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53391095%2fvsts-devops-hidden-file-checked-out-to-another-workspace%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
If the developer no longer works for the organisation then you can just delete the workspace.
You will probably need project administrator permissions to do this.
This question has a bunch of answers that should show you how to do this
answered Nov 20 at 10:50
James Reed
12k4155
Worked great, thanks. Didn't think just to delete the Workspace. Quite odd the file didn't show up as being checked out though
– Andrew Dally
Nov 20 at 15:04
It might have been as Pending "Add" so TFS knew about the file and it's name but it had never actually been checked in. Or perhaps a delete and add. Server workspaces can be a pain sometimes
– James Reed
Nov 20 at 17:02
Ah, that may explain it as I don't actually recall ever seeing it in TFS since we moved. Thanks again
– Andrew Dally
Nov 22 at 12:25
add a comment |
up vote
0
down vote
If the developer no longer works for the organisation then you can just delete the workspace.
You will probably need project administrator permissions to do this.
This question has a bunch of answers that should show you how to do this
answered Nov 20 at 10:50
James Reed
12k4155
Worked great, thanks. Didn't think just to delete the Workspace. Quite odd the file didn't show up as being checked out though
– Andrew Dally
Nov 20 at 15:04
It might have been as Pending "Add" so TFS knew about the file and it's name but it had never actually been checked in. Or perhaps a delete and add. Server workspaces can be a pain sometimes
– James Reed
Nov 20 at 17:02
Ah, that may explain it as I don't actually recall ever seeing it in TFS since we moved. Thanks again
– Andrew Dally
Nov 22 at 12:25
add a comment |
up vote
0
down vote
up vote
0
down vote
If the developer no longer works for the organisation then you can just delete the workspace.
You will probably need project administrator permissions to do this.
This question has a bunch of answers that should show you how to do this
answered Nov 20 at 10:50
James Reed
12k4155
If the developer no longer works for the organisation then you can just delete the workspace.
You will probably need project administrator permissions to do this.
This question has a bunch of answers that should show you how to do this
answered Nov 20 at 10:50
James Reed
12k4155
answered Nov 20 at 10:50
James Reed
12k4155
answered Nov 20 at 10:50
James Reed
12k4155
answered Nov 20 at 10:50
James Reed
12k4155
12k4155
Worked great, thanks. Didn't think just to delete the Workspace. Quite odd the file didn't show up as being checked out though
– Andrew Dally
Nov 20 at 15:04
It might have been as Pending "Add" so TFS knew about the file and it's name but it had never actually been checked in. Or perhaps a delete and add. Server workspaces can be a pain sometimes
– James Reed
Nov 20 at 17:02
Ah, that may explain it as I don't actually recall ever seeing it in TFS since we moved. Thanks again
– Andrew Dally
Nov 22 at 12:25
add a comment |
Worked great, thanks. Didn't think just to delete the Workspace. Quite odd the file didn't show up as being checked out though
– Andrew Dally
Nov 20 at 15:04
It might have been as Pending "Add" so TFS knew about the file and it's name but it had never actually been checked in. Or perhaps a delete and add. Server workspaces can be a pain sometimes
– James Reed
Nov 20 at 17:02
Ah, that may explain it as I don't actually recall ever seeing it in TFS since we moved. Thanks again
– Andrew Dally
Nov 22 at 12:25
Worked great, thanks. Didn't think just to delete the Workspace. Quite odd the file didn't show up as being checked out though
– Andrew Dally
Nov 20 at 15:04
Worked great, thanks. Didn't think just to delete the Workspace. Quite odd the file didn't show up as being checked out though
– Andrew Dally
Nov 20 at 15:04
It might have been as Pending "Add" so TFS knew about the file and it's name but it had never actually been checked in. Or perhaps a delete and add. Server workspaces can be a pain sometimes
– James Reed
Nov 20 at 17:02
It might have been as Pending "Add" so TFS knew about the file and it's name but it had never actually been checked in. Or perhaps a delete and add. Server workspaces can be a pain sometimes
– James Reed
Nov 20 at 17:02
Ah, that may explain it as I don't actually recall ever seeing it in TFS since we moved. Thanks again
– Andrew Dally
Nov 22 at 12:25
Ah, that may explain it as I don't actually recall ever seeing it in TFS since we moved. Thanks again
– Andrew Dally
Nov 22 at 12:25
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53391095%2fvsts-devops-hidden-file-checked-out-to-another-workspace%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
