Devart Forums

Hello there,

We have got the similar issue to this one.
But we are using VS2010 and CC is integrated in it.
Source Control is also VSS 2005.
CC version is 2.70.7.
OS is Win7.

Some details:
- It does not freeze right away but rather after several comparings
- There is no way to close CC window other than through the TaskManager
- To make it work again we have to restart VS

This is quite an inconvenience for us. We have been using Araxis before with no problems whatsoever but it is not free that is why we gave CC a shot.

Thank you in advance for your cooperation.

We are sorry but we cannot reproduce this issue. We will be very much obliged if you describe steps to reproduce the problem in more details including information about types of projects and documents that you are working with, installed add-ins and extensions, applications that are open during freeze.

Hi Artem,

Here are more details on the issue:

VS10 would launch standalone version of CC in spite of being integrated.

Modules being compared are written in C#.

My solution includes different types of projects:
- Windows Forms App
- ASP.NET Web Apps
- Windows Azure Project
- Class Libraries

Installed Add-Ins:
- AAutoCode 2010
Installed Extensions:
- CodeMaid
- IndentGuides
- Javasript Parser
- JScript Brace Matching
- JScript Editor
- JScript IntelliSense Para
- JScript Outlining
- JScript Word Highlighter
- JSEnhancements
- NuGet Package Manager
- Power commands for VS2010
- Process Template editor
- Productivity Power Tools
- VS10x Code Map v2
- VS10x Method Block Highlighter
- VSCommands 10
- Web Essentials
- WITDesigner
- WoVS Default Browse Switcher

Applications that are open during freeze:
- VS10 --> 2 instances
- SSMS 2008 R2
- Azure Storage Explorer
- Outlook
- Chrome
- Firefox
- Evernote
- Windows Live Messenger
- Notepad++
- Skype

Hope this would help.
Regards,
Rodion.

1. Comparison for one of the changes from the first Visual Studio was open in the second Visual Studio.
2. You haven't close these comparisons and clicked some changed file in the "Pending changes" window in the second Visual Studio.
3. The comparison opened in standalone Code Compare (it happened because two Visual Studios were locked at that moment) and froze.
Do I understand this correctly? Unfortunately, even having performed these steps, we are unable to reproduce the freeze. We have not yet created the exact test environment you described, but please tell us any other details that can help us to find the cause of this problem. In particular, did you modify your working copy files during comparison? And did you have any merge conflict or those were the simple diffs?

Artem wrote:1. Comparison for one of the changes from the first Visual Studio was open in the second Visual Studio.
2. You haven't close these comparisons and clicked some changed file in the "Pending changes" window in the second Visual Studio.
3. The comparison opened in standalone Code Compare (it happened because two Visual Studios were locked at that moment) and froze.
Do I understand this correctly?

No, not really.

Integrated CC would not start at all, always the standalone.
I was working only in one VS10 instance at a time.

Artem wrote:did you modify your working copy files during comparison? And did you have any merge conflict or those were the simple diffs?

No merges, no edits, simple diffs.

I was working only in one VS10 instance at a time.

In that case there's no reason to integrate Code Compare into Visual Studio, because VS locks it and all comparisons will be opened in the standalone mode. Try to reinstall Code Compare without the integration option, maybe it will become a workaround for this problem.

Artem wrote: VS locks it and all comparisons will be opened in the standalone mode.

Why would it lock it?

Artem wrote: Try to reinstall Code Compare without the integration option, maybe it will become a workaround for this problem.

Sure, I'll give it a try.

I made a misprint. I had VSS (Visual SourceSafe) in mind.

VSS uses the following scheme of work:
1. Extracts content from repository to temporary files.
2. Calls diff tool and waits until the tool returns a result. During that time Visual Studio does not respond.
3. Deletes temporary files.

So, the sole way to solve this problem is copy/move these files and return control to VSS right away. We will include this improvement in the next version perhaps.

Artem wrote: 2. Calls diff tool and waits until the tool returns a result. During that time Visual Studio does not respond.

Oh, yeah, it is quite annoying indeed, would be nice if you guys nailed it.
Drives me crazy when I want to have diff open and simultaneously put in comments for check-in operation.

This seems to be different issue though.

Visual Studio freezing was an expected behavior but CC freezing was not.

BTW I am having hard times reproducing the issue and I have not re-installed CC yet as you suggested before.