Settings and activity
5 results found
-
6 votes
An error occurred while saving the comment -
7 votes
An error occurred while saving the comment 
David Pollard
commented
An assembly-level diff should compare public types and member signatures, with IL changes as a separate view.
-
8 votes
An error occurred while saving the comment David Pollard
commented
A native macOS build would make Code Compare usable without relying on a Windows VM or compatibility layer.
-
10 votes
An error occurred while saving the comment David Pollard
commented
A JSON-aware diff should match object properties by key, so reordered settings don't appear as wholesale changes; arrays could remain order-sensitive, with changed values shown by JSON path.
-
11 votes
An error occurred while saving the comment David Pollard
commented
TortoiseGit already allows custom diff and merge tools, so this could be handled by adding Code Compare as a supported preset or installer option. The merge command needs to pass the base, local, remote, and output paths correctly; a documented setup would help users until then.
Custom language definitions would cover a lot without needing a full plugin API. Even a user-editable set of extensions, keyword lists, comments, and string rules would help for smaller or proprietary languages. For richer support, a documented plugin interface could let users contribute parsers and keep those integrations separate from Code Compare releases.