Combine revisions from multiple authors into a single document docx from .NET code

Question

1.00/5 (1 vote)

See more:

It is necessary to agree on a contract between the two parties - organizations.
Each party works with its own copy of the original document. Several employees of one party jointly edit “Copy 1”. At the same time, several employees of the other party jointly edit "Copy 2". Representatives of different parties do not see each other's edits.
After completing the amendments, you need to get a final one document docx in which you can see all the differences between “Copy 1” and original document, marked as revisions of Party 1, as well as all differences between “Copy 2” and original document, marked as revisions of Party 2.
Possible solution:
The original document is compared with “Copy 1” by the “Compare” function of MS Word, with the author of the revisions marked as “Side 1”. The original document is compared with “Copy 2” - marked by the author of the revisions as “Side 2”.
Revisions from two documents obtained in this way are combined into one document using the MS Word function “Combine”.
The above logic must be implemented using .Net. We want to avoid using the Microsoft.Office.Interop.Word library. Unfortunately, we did not find any other library with the function analogous to “Combine” in MS Word.

What I have tried:

Microsoft.Office.Interop.Word library

Posted 9-Dec-21 23:25pm

Member 15462608

Updated 9-Dec-21 23:28pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2021-12-09T23:28:00

While we are more than willing to help those that are stuck, that doesn't mean that we are here to do it all for you! We can't do all the work, you are either getting paid for this, or it's part of your grades and it wouldn't be at all fair for us to do it all for you.

So we need you to do the work, and we will help you when you get stuck. That doesn't mean we will give you a step by step solution you can hand in!
Start by explaining where you are at the moment, and what the next step in the process is. Then tell us what you have tried to get that next step working, and what happened when you did.

If you are having problems getting started at all, then this may help: How to Write Code to Solve a Problem, A Beginner's Guide[^]