Mercurial > vim
diff runtime/doc/if_ole.txt @ 30727:645722244c3f v9.0.0698
patch 9.0.0698: VisVim is outdated, does not work with current Visual Studio
Commit: https://github.com/vim/vim/commit/251c1e2ed810d532f7c7d7eb5d6ed5e28a12e501
Author: Martin Tournoij <martin@arp242.net>
Date: Sat Oct 8 17:15:28 2022 +0100
patch 9.0.0698: VisVim is outdated, does not work with current Visual Studio
Problem: VisVim is outdated, does not work with current Visual Studio.
Solution: Remove VisVim. (Martin Tournoij)
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Sat, 08 Oct 2022 18:30:03 +0200 |
parents | f8116058ca76 |
children | 199e0d672feb |
line wrap: on
line diff
--- a/runtime/doc/if_ole.txt +++ b/runtime/doc/if_ole.txt @@ -1,4 +1,4 @@ -*if_ole.txt* For Vim version 9.0. Last change: 2019 Dec 07 +*if_ole.txt* For Vim version 9.0. Last change: 2022 Oct 08 VIM REFERENCE MANUAL by Paul Moore @@ -156,18 +156,14 @@ To avoid the message box that pops up to gvim -silent -unregister ============================================================================== -5. MS Visual Studio integration *MSVisualStudio* *VisVim* +5. MS Visual Studio integration *MSVisualStudio* -The OLE version can be used to run Vim as the editor in Microsoft Visual -Studio. This is called "VisVim". It is included in the archive that contains -the OLE version. The documentation can be found in the runtime directory, the -README_VisVim.txt file. +The old "VisVim" integration was removed from Vim in patch 9.0.0698. Using Vim with Visual Studio .Net~ -With .Net you no longer really need VisVim, since .Net studio has support for -external editors. Follow these directions: +.Net studio has support for external editors. Follow these directions: In .Net Studio choose from the menu Tools->External Tools... Add