I am trying to use vsDiffMerge.exe to recommend code changes allowing users to review code before applying it. I have several issues with it: The original file is missing syntax coloring When opened, the view is always positioned on the file's first line, while I expect it to navigate to the first difference automatically. How to achieve it?

Hi @Tobiasz Tomczyk, Thanks for your feedback. I could reproduce your issue with missing syntax coloring on left window of merge-view. I suggest you report it to product team in Developer Community . Besides, for Diff.NextDifference command, it is designed to use in diff viewer window instead of merge window. You can see Keyboard shortcuts in Visual Studio document to check this command. Sincerely, Anna If the answer is helpful, please click " Accept Answer " and kindly upvote it. If you have extra questions about this answer, please click "Comment". Note: Please follow the steps in our <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fanswers%2Farticles%2F67444%2Femail-notifications.html&data=05%7C01%7Cv-anxiu%40microsoft.com%7Cfbafa63a6d244bc7b02308dab02dffeb%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638016009146709048%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=fQwgaRxLofINtfGCjYbP6ygI0lVyksSFgHo7VnshDEY%3D&reserved=0" rel="ugc nofollow">documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

How to use vsDiffMerge.exe to have full syntax coloring and highlight first difference in the view?

Tobiasz Tomczyk 0

I am trying to use vsDiffMerge.exe to recommend code changes allowing users to review code before applying it. I have several issues with it:

The original file is missing syntax coloring
When opened, the view is always positioned on the file's first line, while I expect it to navigate to the first difference automatically. How to achieve it?

Tobiasz Tomczyk 0 Reputation points

2024-09-10T13:20:05.1333333+00:00

Okay, I have managed to jump to the first difference using built-in VS command Diff.NextDifference in Diff-view, but in Merge-view it does not work (it should be the same API, right? Because why not??)

I have not found any solution for syntax coloring.
Anna Xiu-MSFT 29,006 Reputation points Microsoft Vendor

2024-09-11T03:44:22.8933333+00:00

Hello, which version of Visual Studio are you using? Do you mean that the differences between the files are missing the background color?

If you select two files (use Ctrl-click to select) in Solution Explorer, then right-click and choose Compare Selected to open the diff view to compare the two files, could you find the syntax coloring or a background of the differences between the files?
Tobiasz Tomczyk 0 Reputation points

2024-09-11T16:09:19.2333333+00:00

I need to support it starting with VS 2019, but the component behaves the same in VS 2019 and VS 2022.

Please note that I am using merge (not diff) mode. In that mode, the left pane is never coloring the syntax properly. The right pane and bottom pane are coloring it as expected. In diff mode that issue does not occur.

Is it expected that Diff.* commands will not work in merge mode? IMO, it is unexpected as the component is the same but with additional actions available.
Anna Xiu-MSFT 29,006 Reputation points Microsoft Vendor

2024-09-12T09:33:01.81+00:00

Hello, are you using version control? Is it TFVC or Git?
Tobiasz Tomczyk 0 Reputation points

2024-09-16T22:21:16.4866667+00:00

Comment added by mistake (sorry but the web interface works badly when adding comments :( )
Tobiasz Tomczyk 0 Reputation points

2024-09-16T22:24:09.3633333+00:00

Comment added by mistake (sorry but the web interface works badly when adding comments :( )
Tobiasz Tomczyk 0 Reputation points

2024-09-16T22:24:52.72+00:00

In my development I use Git, but this information is irrelevant here.

My solution is independent of source control, as I am preparing a temp file that is a modified version of the original file. Then those two files are presented in merge view so the user can review and merge proposed changes if he is okay with them.
Anna Xiu-MSFT 29,006 Reputation points Microsoft Vendor

2024-09-17T09:29:58.09+00:00

Hello, could you share me a screenshot for further check?
Tobiasz Tomczyk 0 Reputation points

2024-09-18T14:10:45.75+00:00

There is no syntax highlighting on the left pane. Other than that, the Diff.* commands mentioned do not work (IMO, it is a more important issue).

1 answer

Anna Xiu-MSFT 29,006 Reputation points Microsoft Vendor

2024-09-19T09:50:55.8433333+00:00

Hi @Tobiasz Tomczyk,

Thanks for your feedback.

I could reproduce your issue with missing syntax coloring on left window of merge-view. I suggest you report it to product team in Developer Community.

Besides, for Diff.NextDifference command, it is designed to use in diff viewer window instead of merge window.

You can see Keyboard shortcuts in Visual Studio document to check this command.

Sincerely,

Anna

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

How to use vsDiffMerge.exe to have full syntax coloring and highlight first difference in the view?

1 answer

Your answer