-
Notifications
You must be signed in to change notification settings - Fork 392
Build Environment
- Install the Visual SDK for your Visual Studio Version:
- Open the Solution
VsVim.sln
- Build
-
VimCore.sln
- the part of VsVim that doesn't depend on the full Visual Studio environment -
VsVim.sln
- builds the VsVim Visual Studio extension -
VimAll.sln
- likeVsVim.sln
but includes VimApp which isolates VsVim into a standalone application
The extension solutions are set up to debug the VsVim that is built inside an experimental instance of Visual Studio. The experimental instance can (and should) have different extensions installed that your primary Visual Studio instance. The fewer the better!
Core editor feature development and testing is made faster and easier by using the VimApp standalone application. The whole of Visual Studio doesn't have to fire up, breakpoints are reached sooner, etc.
To install the version you built into your "normal" instance of Visual Studio:
- remove any previous version of VsVim using Tools -> Extensions and Updates...
- close Visual Studio
- double-click, e.g., the file
Src\VsVim\bin\Release\VsVim.vsix
Installation of vsix files can also be done manually (assuming the extension is not already installed in a different folder) by simply unzipping the vsix file into any folder under, e.g., %LOCALAPPDATA%\Microsoft\VisualStudio\11.0\Extensions
and deleting the corresponding cache file, e.g., %LOCALAPPDATA%\Microsoft\VisualStudio\11.0\Extensions\extensions.en-US.cache
. If this approach is used, the first time it is installed this way it will be disabled but can be enabled using the extension manager.
- master: Stable branch
- staging: Used for releasing new versions
- fixes*: Both short and long term fixes
- dead*: Branches which will never integrate with master again.