5 results found

1. Compare window should be open in new window.

   Today I integrated this tool with the VS2010. But before Check-in if compare files then compare window should open in new window. Else its not possible to see actual comparison.

   5 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

   declined  ·  3 comments  ·  Delete…  ·  Admin →

2. Bring back support for visual studio 2008

   "We have discontinued support of Visual Studio 2008 in Code Compare 3.0" --> Is it so hard to support VS 2008 really? It is by far the most stable VS ever released. No, 2010 and 2012 are bad, even though I am using them on a regular basis. BTW for SQL reporting VS 2008 is your only option today.

   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

   4 comments  ·  Delete…  ·  Admin →
   declined  ·  AdminDevart (_, Devart) responded

   See comments for more information

3. Scope Detection

   Code Compare has a lot of difficulties to deal with scope changes. More than often, adding a namespace will mess up the comparison algorithm pretty badly. You'll end up with a billion changes in a file because all the lines have been changed (added tabulation) and one line have been added at the top. I've even seen it glitch and report that all the lines were new content...

   A nice solution would be scope detection. Limit the comparison within scopes. Detect scope changes etc. That way, adding a namespace or a try/catch block could be detected and merged as one change.

   This is valid for any language with scope, including xml and json.

   Code Compare has a lot of difficulties to deal with scope changes. More than often, adding a namespace will mess up the comparison algorithm pretty badly. You'll end up with a billion changes in a file because all the lines have been changed (added tabulation) and one line have been added at the top. I've even seen it glitch and report that all the lines were new content...

   A nice solution would be scope detection. Limit the comparison within scopes. Detect scope changes etc. That way, adding a namespace or a try/catch block could be detected and merged as one… more

   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

   1 comment  ·  Delete…  ·  Admin →
   declined  ·  AdminDevart (_, Devart) responded

   For such a situation you should use the ‘Detect similar lines’ option.

4. paging
   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

   2 comments  ·  Delete…  ·  Admin →
   declined  ·  AdminDevart (_, Devart) responded

   Unfortunately, we can not understand what did you mean

5. Allow diffs to annotated

   Allow diffs to be annotated, much in the same way GitHub (or Git Blame) allows you to. This would be a major win for nearly every code-review-based process out there.

   These annotations would need to be persisted against the original files somehow. Possibly within a '.zip' variant containing both files and the annotations.

   This is related to http://devart.uservoice.com/forums/93035-codecompare/suggestions/1332369-diff-reports. If the results of the review sessions could be exported to PDF that would also probably work.

   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 →
   declined  ·  AdminDevart (_, Devart) responded

   We have tool for do job right you described:
   http://www.devart.com/review-assistant/download.html