Sorry, I have nothing really to offer you as far as solving the issue. But I did want to say that your issue really seems to underscore a fundamental belief I developed over the years. And that belief is that a trade off always occurs when you "integrate" two applications such as RoboHelp and a Source Control system. You find that things that would be simple to achieve aren't quite that simple when you allow one application to control another.
It is for this very reason that I've always preferred working with things independently. I guess one might refer to me as being a "segregationist". LOL But when you think about it, by isolating the applications and using them independently, you may just find yourself removing some frustration along the way.
Helpful and Handy Links
It's very annoying indeed. I do believe that it's TFS's fault since I also get these popups when I check something in from outside RoboHelp, but since I very rarely rename more than a single file I haven't really looked into it. It may very well be a TFS setting. Be sure to ask your TFS administrator.
Personally, when I have such large tasks, I follow the following steps: (In the case of renaming)
- Close RoboHelp.
- Check out the files from TFS
- Rename all the files/directories.
- Edit the .fpj files of the Robo project so all fpj files point to the correct files. (Rename the .fpj to reflect the names of the directories.)
- Remove the CPD.
- Start RoboHelp and check for broken links. Redo steps if needed.
- Check in all changes at once.
This may not be a solution, but it works for me. I'm open for any suggestions!
Thank you for your proposal for solution.
It's a good work around I used too. But like you say it isn't a solution.
I believe the problem is on the side of RoboHelp.
Because if i rename something in windows explorer with TFS right-mouse-click -> Team Foundation Server -> rename, it's one action named "rename" on TFS and not "edit","add", "add" each file, "delete" old folder.
It seems that RoboHelp uses the wrong command, maybe someone know how I can solve this problem.
In that case it's a RoboHelp bug, I don't think you can just solve it. My guess it's something in the RH code itself. You may want to report this as a bug: http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform&product=38