File is Exclusilvely Checked out by another user -----HELP

Hot Topic

fxcop
Using validation rules to stop a web test
Suggestion: Extend InstantiateArgumentExceptionsCorrectly to include ArgumentException.ParamName
Checked out strange behaviour
Team Project creation fails by failing in task SharePointPortal
Can anyone show me a sample source code in reading SourceContext line number?
Problem with Visual Interdev and VB6 with Source Control in TFS
I cannot create unit test for my application?
TFS beta 3 installation
Testing for Exceptions in Unit Tests

VS Team System

Compare differences between branches?
Wil the real servername please stand up!
Team System Builds and dropping an MSI
BUG - Rank field
Restoring reports for a team project
How to force Repository Refresh?
Generate Typelib from Team Build
Microsoft Partner Program License Benefits FAQ
Where Can I download MSF V4 WhitePapers
Visio 7.1 for EA and VS2005

File is Exclusilvely Checked out by another user -----HELP

Hi,

How do I find out who is this user.

All the users I know have nothing in their Pending Checking windows.

It looks like the entire project has been checked out by this "Someone"

thanks

Answer this question

File is Exclusilvely Checked out by another user -----HELP

  • vitriolv

    There are a couple way to do this; first inside of VS:

    View the Source Control Explorer (View | Other Windows | Version Control Explorer); then you should be able to browse to the location in the repository you are interested in.  This should list the user with a pending change of lock.  If there are multiple pending changes then you could do the propery of that item.

    Or, you can use the command line:
    1.  In a VS Command Prompt, cd into folder (workspace/working folder) where the file in question resides.
    2.  Issue the command:  "h.exe /status /user:* filename"

    Sample output from the command line:
    File name Change User                 Local path
    --------- ------ -------------------- -------------------------------------
    $/VersionControlAutomation_Basic/WS1/Rename/Sub1
    ABC       * edit DOMAIN\user1 F:\\WS1\Rename\Sub1\ABC
    ABC.txt   ! edit DOMAIN\user1 F:\\WS1\Rename\Sub1\ABC.txt

    From the example above you can see that user1 has one file checkout with a checkin lock and another file checkout with a checkout lock.

    Checkin Lock:  This lock prohibits users from checking in changes on this file while the lock exists.

    Checkout Lock:  This lock prohibits users from checking out or in changes on this file.
  • File is Exclusilvely Checked out by another user -----HELP
Answer this question