So I installed the latest build of CodeCompare to replace the built-in merge tool with TFS2010/VS2010. The CodeCompare tool works great! There appears to be a strange side-effect, however. Both myself and 3 other teammates of mine are experiencing this issue post-install. What we are seeing is that the built-in outlining in VS is collapsing code blocks that we have open when we change from the current tab to another tab. When we come back to the original tab, the code/method is collapsed. This is a rather frustrating issue. I'm wondering if anybody else has noticed this? Is there any known solution?

Thank you Artem. I tried both the check boxes in that section. I first tried the one you mentioned. Then I tested unchecking its parent. I even went so far as to close/reopen VS after each. Still no change. I have uninstalled CodeCompare and it is now working as desired. Shall I reinstall and test again?

I am switching between two open class files in a project under TFS2010 source control. However I have tested this with a simple Web App project not under source control. I switched between the aspx and the aspx.vb files with only 1 method in the codebehind, and this did not collapse. I added a second method to the codebehind and then it did collapse. Current settings are the "Use Outlining" is checked and "Smart Collapse after file opening" is unchecked. Thank you for your help. If you need more information, I'm willing to help in any way I can.

Here's some more information. When I initially load up the project, outlining is off. I right-click and select outlining->collapse to definitions. As long as the current file is the only one with outlining enabled, it will not collapse after leaving/returning. However, once I go to another file and perform the same collapse to definitions, the issue appears. I expand a method in file1, switch to file2. When I return to file1 everything is collapsed. Hopefully this provides some more insight? Thanks again for your help.

Thank you very much for your assistance in this matter Artem! It was a pleasure to have the process go as smoothly as it did. I checked today, and there was a new build posted on th 27th, version 2.50.10. Is this the build with the fix in it? I didn't see anything sounding like the issue from the release notes.