0

Team Foundation Source Control integration does not work properly

John Morris

12 October 2007 10:02

None

Follow

I am having a lot of issues with the TFS source control integration. When I open a project, it asks me if I want to check it out. I say "yes". Once the project is open, I can't edit anything because it says the file is checked out by someone else...and it's ME!!

Why does HelpStudio have an issue with multiple check-outs? These files are not binary and are not exclusively locked. Even more disturbing, why does the IDE think I cannot edit the file when it's ME that has the file checked out in the first place!

I am in the process of evaluating this product for our company's use, but this is a deal breaker unless it gets fixed.

 Thanks!

John

 

• Facebook
• Twitter
• LinkedIn

4 comments

• 0
  
  Permanently deleted user 16 October 2007 06:24

  I apologize for any frustration this problem has caused you. A common cause of this problem is having an existing workspace defined for the local path in which your project is saved where that workspace is owned by a different user.

  Could you possibly examine the workspaces in the TFS Source Control window within Visual Studio (double click Source Control from the Team Explorer pane) to see if you have a workspace defined with a different owner?

  We do have a debug .dll I can send you that should reveal more about the problem - if you are willing to give that a go could you drop me an email to richard@innovasys.com.

• 0
  
  Steve D 23 October 2007 08:42

  Trashing your workspaces often works.

  Also, make sure you do not have the files checked out by or in Visual Studio. In VS, do a check-in on your entire branch. Ensure nothing is checked out.

  Next, in VS 'Get latest Version'.

  In HS, open the hsp file from your local VS tree. When prompted to save locally, save into the same tree.

  Here forward, only check HS files in and out of HS. NEVER check-in / out in VS.

• 0
  
  John Morris 26 October 2007 14:19

  I am the only user who users/owns that workspace and the folder location is unique.

   Trashing my workspace when something like this happens is not an acceptable resolution. In addition, they should be no issue depending on where I check out the file. A simple refresh of the source control status should fix any issues if that's the case.  From our testing it looks like the source control integration needs a lot of work to come up to par with integrations like Visual Studio (and even RoboHELP).

  We've decided to stick with RoboHelp. The SCC integration (using the TFS MSSCCI Power Toy) provides a better experience and better stability than the HelpStudio integated support.

• 0
  
  Permanently deleted user 26 October 2007 15:04

  Hello John,

  I didn't see a reply from you after my last post so had assumed you had resolved the issue you were encountering. We would not suggest that it is ever necessary to trash your TFS workspaces to resolve any issues with HelpStudio integration, and we are more than happy to assist and support anyone having problems with Source Control Integration in HelpStudio.

  We have many customers (including ourselves) that are using Source Control Integration eatures in HelpStudio to great effect, and we believe we have the most seamless, granular and hassle free Source Control Integration of any Help Authoring tool available today.

  If you are willing to work with us to get to the bottom of the issue you are experiencing we would be more than happy to assist you further - please contact me direct at richard@innovasys.com if I can be of any help.