Alternative to DTE for Debugger and calling built-in VS commands?

[moon6969]

I read discussion #66 Should DTE be avoided? with interest.

My Google-Fu is failing me trying to find non-DTE methods for my Extension.
Are there any migration guides, references etc. about?
(I've seen the VSIX Cookbook that has some recipes & snippets.)

Is there a non-DTE way for the following? (don't need code, just hints on where to look!).

• iterate, create & edit Breakpoints (dte.Debugger.Breakpoints...)
• use an UndoContext (dte.UndoContext...)
• execute a built-in VS command (dte.Commands.Raise(formatSelectionCommand.Guid, ...))

Thanks.

[ErikEJ]

You can still use DTE if your extension targets only VS 2022

[moon6969]

Thanks Eric, my VS2022 extension does currently work as desired using DTE2.

I'm not sure why you say "if your extension targets only VS 2022"? What is the wrinkle if I wanted to target say VS2019 as well?

[ErikEJ]

Then you would need to build and publish two distinct extensions, (maybe from as shared codebase), as the "old" DTE references in VS 2019 are not allowed in VS 2022.

[moon6969]

Found one answer in the Object Browser...
await VS.Commands.ExecuteAsync(KnownCommands.Edit_FormatSelection);

[reduckted]

Replacement for the UndoContext:

Community.VisualStudio.Toolkit/src/toolkit/Community.VisualStudio.Toolkit.Shared/ExtensionMethods/ITextBufferExtensions.cs

Line 19 in e2d88dd

public static async Task<ITextUndoTransaction> OpenUndoContextAsync(this ITextBuffer buffer, string name)