Book a Demo

Author Topic: TFS Source Control  (Read 3817 times)

dburrell

  • EA Novice
  • *
  • Posts: 4
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
TFS Source Control
« on: October 06, 2006, 10:10:37 am »
I can't checkout after I add a package to Source Control.

When I attempt to check out a package I get a "Checkout Failed.", but when I bring up Team Explorer the xml file is checked out.  I also loose the abititly to try again or refreash the status of the checkout.  I must manually undo checkou in Team Explorer to try again.  

I am the Overall Admin in Team Foundation, so I have full access to all options of source control.

dburrell

  • EA Novice
  • *
  • Posts: 4
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: TFS Source Control
« Reply #1 on: October 06, 2006, 04:30:53 pm »
Is anyone having this problem?  I can't let other developers make changes to the diagrams unless I have source control.  Please HELP!

dburrell

  • EA Novice
  • *
  • Posts: 4
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: TFS Source Control
« Reply #2 on: October 09, 2006, 02:34:57 pm »
How do we get support?  I used the report support feature of this website, and I posted my problem to this forum.  We need help

Marvis

  • EA Novice
  • *
  • Posts: 12
  • Karma: +0/-0
  • Creativity is allowing yourself to make mistakes.
    • View Profile
Re: TFS Source Control
« Reply #3 on: October 17, 2006, 06:18:22 am »
Hello. I think I have the same problem. I can't figure out what's wrong.
For now I will continu using the MSSCC pluging for TFS.

dburrell

  • EA Novice
  • *
  • Posts: 4
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: TFS Source Control
« Reply #4 on: October 19, 2006, 12:37:35 pm »
I will start using the plugin.  thanks for your reply

KeesDijk

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: TFS Source Control
« Reply #5 on: November 01, 2006, 05:29:55 am »
We had the same problem, our solution might work for you also.

In the Version Control Dialog we specified the domain with the username <domain>\username. It connected succesfully but check-outs would fail.

When we configured without the domainname it worked fine.