Compartir a través de

Intercepting Legacy Language Service Commands

  • Artículo

Applies to: yesVisual Studio noVisual Studio for Mac

Note

This article applies to Visual Studio 2017. If you're looking for the latest Visual Studio documentation, see Visual Studio documentation. We recommend upgrading to the latest version of Visual Studio. Download it here

With Visual Studio, you can have the language service intercept commands that the text view would otherwise handle. This is useful for language-specific behavior that the text view does not manage. You can intercept these commands by adding one or more command filters to the text view from your language service.

Getting and Routing the Command

A command filter is an IOleCommandTarget object that monitors certain character sequences or key commands. You can associate more than one command filter with a single text view. Each text view maintains a chain of command filters. After you create a new command filter, you add the filter to the chain for the appropriate text view.

Call the AddCommandFilter method on the IVsTextView to add your command filter to the chain. When you call AddCommandFilter, Visual Studio returns another command filter to which you can pass the commands that your command filter does not handle.

You have the following options for command handling:

  • Handle the command and then pass the command on to the next command filter in the chain.

  • Handle the command and do not pass the command on to the next command filter.

  • Do not handle the command, but pass the command on to the next command filter.

  • Ignore the command. Do not handle it in the current filter, and do not pass it on to the next filter.

    For information about which commands your language service should handle, see Important Commands for Language Service Filters.