Skip to content

Latest commit

 

History

History
55 lines (41 loc) · 1.99 KB

Developing.md

File metadata and controls

55 lines (41 loc) · 1.99 KB
Raw

Developing VsVim

When developing please follow the coding guidelines

Requirements

VsVim can be developed using Visual Studio 2022. The required workloads are:

  • .NET Desktop Development
  • F# Language
  • Visual Studio Extension Development

Multi Editor Support

VsVim supports multiple versions of Visual Studio: 2015 through 2019. While the underlying editor components are remarkably compatible between the versions, there are subtle behaviors differences that do show up. Further there are features, like async completion, which appear only in later versions of Visual Studio.

The the unit tests are designed to test against multiple versions of Visual Studio. This is done at build time with a series of #if directives to configure the unit tests to load a specific version of the VS editor components.

By default VsVim will run unit tests against the version of Visual Studio that is being used to edit the source code. This can be configured though by doing the following:

  • Setting %VsVimTargetVersion% to 14.0, 15.0 or 16.0
  • Running Build.cmd -testConfig <value> with 14.0, 15.0 or 16.0

The version of Visual Studio being targetted for testing does not need to be installed on the machine.

VimApp

The VimApp project in the solution is a light weight host of the VS WPF editor. It starts up quickly and is good for rapidly testing out new features and bug fixes.

The version of the WPF editor it loads is configured in exactly the same way as the unit tests.

CI

The goals of the CI is:

  1. To validate the VsVim behavior on supported editor versions
  2. To validate the consistency of the build: versions numbers, VSIX content, etc ...
  3. To upload successful builds to the Open VSIX gallery

Azure DevOps Links: