ScriptFiles.md

About the script files

Known Issues

Solution.csx and FindResultsWindow.csx are manipulating the tool window of Visual Studio.
However, it becomes impossible to operate if it becomes the following state.

• The editor that executed the csx command is no longer active.
• The editor that executed the csx command is closed.

The reason for these is that the script gets the key event of the editor that executed the csx command and manipulates the tool window.

When using SimpleSurround.csx etc., the user needs to enter a value in the command margin.
The command margin at this time is a poor function that the cursor is not displayed and the arrow keys can not be used.

I use a lot of reflection in scripts. This is a unrecommended method. If VsVim or Visual Studio update, scripts may not work.

Description of each script file

• CalledCount.csx
• EasyMotion.csx
• FindAll.csx
• FindAllReferences.csx
• FindAllReferencesResults.csx
• FindAllReferencesWindow.csx
  This script does not work on its own.
• FindResults.csx
• FindResultsWindow.csx
  This script does not work on its own.
• IndentObject.csx
• JDash.csx
• Marks.csx
• MethodTextObject.csx
• Methods.csx
• Options.csx
  This script does not work on its own.
• Scroll.csx
• SelectionMove.csx
• ShowCommandText.csx
• SimpleSurround.csx
• Solution.csx
• Tabs.csx
• Tasklist.csx
• TinyVim.csx
  This script does not work on its own.
• Util.csx
  This script does not work on its own.
• VsVimFindResultsWindow.csx
  This script does not work on its own.
• VsVimFindResultsWindow.xaml
  This is xaml for use with VsVimFindResultsWindow.csx.
• WindowUtil.csx
  This script does not work on its own.