Steps
I start beyond compare, and go to the SCI options area. Then I add my Source control project mapping, see "ss1.jpg" and "ss2.jpg"
then i do a comparison w/ files under my source control tree. I am prompted to connect to a TFS server the first time, see "ss3.jpg"
and then am immediately greeted w/ the problem addressed by this thread, see "ss4.jpg," on each and every comparison involving a file under the source tree from here on out
If i disable SCI, i am able to compare the same files w/ no error prompts.
If indeed this is an error thrown to us by TFS, then I am curious as to what's causing it. Our entire development team has no source control issues w/ either VS.net 2005, 2008, 2010, or the TFS powertools shell extension. BC is the only one that exhibits this behavior.
I start beyond compare, and go to the SCI options area. Then I add my Source control project mapping, see "ss1.jpg" and "ss2.jpg"
then i do a comparison w/ files under my source control tree. I am prompted to connect to a TFS server the first time, see "ss3.jpg"
and then am immediately greeted w/ the problem addressed by this thread, see "ss4.jpg," on each and every comparison involving a file under the source tree from here on out
If i disable SCI, i am able to compare the same files w/ no error prompts.
If indeed this is an error thrown to us by TFS, then I am curious as to what's causing it. Our entire development team has no source control issues w/ either VS.net 2005, 2008, 2010, or the TFS powertools shell extension. BC is the only one that exhibits this behavior.
Comment