如何获取Word操作历史栈引用？Word 2016 VSTO插件开发问询

Hey there! Let's break down how to solve this problem—you want to undo a specific earlier action (like that text you typed) without rolling back later operations (shapes, images), and you've already noticed Word's built-in Doc.Undo() only handles the last action, while StartUndoRecord() is for bundling your own code's operations.

First, a critical limitation to clarify: Word's object model does NOT expose a direct reference to its internal undo history stack. This is intentional on Microsoft's part—they keep the undo stack's internal implementation closed off, so we can't just "grab" it and pick a specific entry to undo directly.

But don't worry, there are practical workarounds to achieve exactly what you need:

1. Manually Track User Actions (Most Reliable Approach) #

Since we can't access Word's native undo stack, we can build our own custom history by listening to Word's event model and recording every relevant user action. Here's how to implement this:

• Listen to targeted events: Use Word's built-in events to capture actions like text insertion, shape addition, and image pasting. Key examples include:
  • Document.ContentAfterInsert for text or rich content inserts
  • Document.ShapeAdded for floating shapes
  • Document.InlineShapeAdded for inline images
• Record action details: For each event, store critical information needed to reverse the action. For instance:
  • For text input: Save the Range object where the text was inserted, plus the text content itself. To undo, you'd call Range.Delete().
  • For a shape: Save the shape's ID or direct reference. To undo, call Shape.Delete().
  • For a pasted image: Save the inline shape's reference, then delete it to undo the paste.
• Maintain your own undo stack: Keep a list/stack of these recorded actions, so you can let users select which one to undo, then execute your custom reversal logic for that specific entry.

This approach requires handling edge cases (like overlapping actions or user-initiated native undos that might conflict with your stack), but it gives you full control to undo specific operations without touching later ones.

2. Use Undo Records for Controlled Operations (Limited Use Case) #

If you're able to wrap user actions before they happen (e.g., your add-in triggers the text input, shape creation, etc.), you can use StartUndoRecord() and EndUndoRecord() to create distinct, named undo units. For example:

// Wrap text insertion in a named undo record
Globals.ThisAddIn.Application.StartUndoRecord("Text Insertion");
// Code that inserts text
Globals.ThisAddIn.Application.EndUndoRecord();

// Wrap shape addition in another undo record
Globals.ThisAddIn.Application.StartUndoRecord("Shape Addition");
// Code that adds a shape
Globals.ThisAddIn.Application.EndUndoRecord();

Then, users could use Word's native undo dropdown to pick "Text Insertion" to undo just that action. But this only works if your add-in is initiating the actions—you can't retroactively wrap user-spontaneous actions (like typing or pasting) into undo records.

Key Notes #

• Word's native undo stack is document-specific, but again, we can't access its internal entries.
• When building your custom history, make sure to sync with Word's native undo/redo events (like Document.BeforeUndo or Document.BeforeRedo) to keep your stack aligned if the user uses Word's built-in undo buttons.

At the end of the day, manual tracking is the only way to get the granular control you need for undoing specific non-latest operations in a VSTO add-in.

内容的提问来源于stack exchange，提问作者user8223690