Please tell me that this has been solved in SP1...

When you try to add a link from a work item to a versioned item in Source Control you may get an error "Unable to save all edited documents..." in Visual Studio.

Someone said that this problem corresponds to a limitiation of the numbers of characters you may have in a file path (260 chars) but this happens to us in much shorter paths (around 100 characters). This is such a stupid limitation/bug which has huge consequenses on our project - please tell me that this has been solved in SP1

/Thomas Andersson



Answer this question

Please tell me that this has been solved in SP1...

  • rileyt

    I searched and found the bug, and found that it didn't make it to SP1. I have entered your feedback into that bug. As Dan said, please contact CSS if this is serious for you to find some workaround or hotfix. CSS number: 800/936-5800 if from US (see <http://support.microsoft.com/> for calling from other countries)

  • Dan_Dan

    I remember we working on a solution for this bug and I am checking with few people here to find if this was part of SP1 fix. I suspect it is not. The reason for the bug is because our source control stores full file name in link info and it has 255 char limitation. With localized builds, because of encoding it goes below 100. Sorry for the trouble you are going through because of this bug.

  • awj100

    Thank you,

    I will reconsider the option to contact Product Support.

    /Thomas


  • voidstar

    Thomas,

    Firstly I want to apologize for any inconvenience that this issue is causing you and your team. We will double check again to see if this is fixed in SP1, and I again apologize if this did not make it into SP1.

    If this bug is a serious issue for you (which it appears to be), please contact Product Support so that this issue can be escalated, and if necessary we can work on a hotfix for you.

    Thanks,



  • Shadowz O Death

    Hi Naren,

    Thanks for your answer!

    So you knew that this was a bug but didn't bother to fix it in SP1 Then I am afraid you don't know what impact this bug may have on us - a major part of our CM strategy is now useless for our project (we have over 100 use-cases, project teams spread out over the world and an advanced release management) and we have no good alternative way to go.

    What do you mean by the "localized builds" We use the "normal" english version of TFS but our database has collation "Finnish_Swedish_CI_AS" - is this what you mean by localized build

    Kind Regards
    Thomas


  • Please tell me that this has been solved in SP1...