Settings and activity
5 results found
-
5 votes
An error occurred while saving the comment -
5 votes
An error occurred while saving the comment 
Scott Barton
commented
A configurable history size and a “clear recent comparisons” command would make this safer for shared machines. Comparison paths can expose project or customer names, so there should also be an option to disable saving history entirely. Reopening a pair from the list should restore the comparison settings as well as the paths, so the result matches the original run.
-
5 votes
An error occurred while saving the comment Scott Barton
commented
Virtual line breaks should be display-only and keep the original line numbers intact. A toggle would also help: some comparisons benefit from strict side-by-side alignment, while others are easier to scan without inserted blank space. This would make the outlining boxes less necessary.
-
5 votes
An error occurred while saving the comment Scott Barton
commented
Reusable folder profiles would be more useful than storing only one pair of paths. Let users name each comparison and save its filters and options too, so recurring checks can be reopened without rebuilding the setup each time.
-
5 votes
An error occurred while saving the comment Scott Barton
commented
A compatibility note would help alongside the timeline: whether the current Code Compare build works in VS 2022, and whether users should expect an extension update or a new installer. Even a status such as “in evaluation” would be more useful than silence.
Persisting this as a Code Compare preference would apply the toolbar choice to every comparison opened from Visual Studio, not just the current window.