28 results found

1. Mismatched line comparison based on their similarity

   This feature allows you to compare files even when many small changes in the
   file lines are provided (e.g., refactoring).

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   completed  ·  0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Keep folder comparison tree in sync

   Folder comparisons get out of sync when the keyboard is used to expand/collapse the tree structure.

   1. Do a folder comparison of similar folders which contain sub-directories
   2. Close or open one of the sub-folders by clicking on the +/- icon with the mouse --> As expected, the folder closes/opens on both sides of the tree view, not just in the side that was clicked.
   3. Close or open one of the sub-folders by selecting it and pushing the left or right arrow key on the keyboard (or the plus or minus key). --> Only the side which has primary focus is opened/closed and the views become out of sync. Changing the selection brings the scroll positions back in sync temporarily but using the scrollbars gets them out of sync again, making comparing the folders very difficult, especially if you don't realise why it's now behaving so contrarily.

   Folder comparisons get out of sync when the keyboard is used to expand/collapse the tree structure.

   1. Do a folder comparison of similar folders which contain sub-directories
   2. Close or open one of the sub-folders by clicking on the +/- icon with the mouse --> As expected, the folder closes/opens on both sides of the tree view, not just in the side that was clicked.
   3. Close or open one of the sub-folders by selecting it and pushing the left or right arrow key on the keyboard (or the plus or minus key). --> Only the side which has primary focus is opened/closed… more
   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   completed  ·  AdminDevart (_, Devart) responded

   We have just released Code Compare 3.0: http://www.devart.com/news/2013/codecompare30.html

3. The Visual Studio TFS Merge result file should not be read only when using Code Compare

   When using Code Compare for TFS Merge, you get the 3-Way Merge panes. The center pane is the merge result. This merge result temporary file is read only however. After making alterations to the merge result you are asked to Overwrite this file. This scares me, because it looks like I am doing something wrong.
   When using the default TFS Merge compare tooling you are not asked to overwrite the merge result file.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   completed  ·  0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Navigate conflicts only (TFS)

   It's a function we have in Visual Studio 2010 when a conflict between 2 files is detected and we have to manually merge them. When this function is activated the "next conflict" button goes only on the conflicts that have to be merged manually. The others can be merged automatically.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   completed  ·  0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Feedback button

   That feedback button is hovering over text I want to read.

   The web site designer sucks. You have a good product why curse it with your hovering?

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   completed  ·  0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Settings for codecompare shell to open by default

   Personally I like CC to open in my current VS shell when I am using it to diff files in my solution (or against previous version in the solution).
   Specifically I like it to open in the VS session where I triggered it from, ie by right clicking in the solution explorer.

   Conversely in all situations where I diff files in explorer or any other file browser I want it to open in a standalone window. Both for file diffs and folder diffs.

   Obviously I accept that my desires won't match all (or possibly even most) users' but a few config options would help meet all needs.
   Usecases I would expect are:
   - the one detailed above for VS host of VS triggered diffs and standalone for all other trigger sources.
   - VS only
   - Standalone only
   - most recent shell
   - standalone for folder, VS for other
   - VS for specific files (eg *.cs, *.cpp, etc.)

   Example options off the top of my head:
   1. Always open in standalone Shell.
   2. Always open in triggering shell (eg VS)
   3. Open in shell based on extension filter
   4. Default to most recently accessed viable shell (ie in the latest VS or CC shell)
   5. Default to standalone shell
   6. Always use default

   if 1 is selected then it's always the standalone, if 2 is selected and the triggering shell is not a viable one then 4 or 5 will determine what shell to default to. 6 will decide whether the prompt dialog showes or not...

   Personally I like CC to open in my current VS shell when I am using it to diff files in my solution (or against previous version in the solution).
   Specifically I like it to open in the VS session where I triggered it from, ie by right clicking in the solution explorer.

   Conversely in all situations where I diff files in explorer or any other file browser I want it to open in a standalone window. Both for file diffs and folder diffs.

   Obviously I accept that my desires won't match all (or possibly even most) users' but a few… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   completed  ·  AdminDevart (_, Devart) responded

   We have just released Code Compare 3.0: http://www.devart.com/news/2013/codecompare30.html

7. Ability to enable/disable binary quick comparison dialog from showing when the same file is detected.

   I'd like to be able to disable the binary quick comparison dialog from showing when files are detected as being the same. I'm working with comparing literally a thousand files and those dialogs are really getting in the way when using the command line since I have to click through them all.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   completed  ·  AdminDevart (_, Devart) responded

   We have just released Code Compare 3.0: http://www.devart.com/news/2013/codecompare30.html

8. Allow open all files for comparison without closing them

   When you launch comparison of an opened file in the Code Compare extension for Visual Studio, we prompt to close it in order to continue opening comparison. This happens for HTML, JavaScripts, CSS, SQL, XAML, VB.NET, etc.
   Code Compare should allow opening these kinds of files without closing opened documents.

   0 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   completed  ·  0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close