Wiki: DebugInfo: VisVimDisinterest

transformedtext Object
(
    [_type] => pagetype_wikitext Object
        (
        )

    [_basepage] => VisVimDisinterest
    [_content] => Array
        (
            [0] => <div class="wikitext"><p class="tightenable top">To be honest, there is a bit of disinterest, because it causes a disconnect between the two system in a major way... but -- there is hope.  
            [1] => cached_wikilink Object
                (
                    [_page] => VisVim
                )

            [2] =>  maybe be dead, but Vim integration with vs.net isn't...</p>
<dl><dt class="tightenable">Check out</dt>
<dd class="tightenable bottom"><ul><li class="tightenable top">
            [3] => cached_externallink Object
                (
                    [_url] => http://vim.sourceforge.net/tips/tip.php?tip_id=368
                )

            [4] =>  -- this is just a tip showing you how to use vim as a plugin.</li>
<li class="tightenable bottom"><p class="tightenable top bottom">
            [5] => cached_externallink Object
                (
                    [_url] => http://vim.sourceforge.net/scripts/script.php?script_id=864
                )

            [6] =>  -- This vim script does stuff like ...</p>
<ul><li class="tightenable top bottom">Compile the current file. For C/C++ (menu: 
            [7] => cached_wikilink Object
                (
                    [_page] => VisualStudio
                )

            [8] =>  -&gt; Compile)</li>
<li class="tightenable top bottom">Build the current project. For C/C++ or C# (menu: 
            [9] => cached_wikilink Object
                (
                    [_page] => VisualStudio
                )

            [10] =>  -&gt; Build Solution).  Thanks to Leif Wickland for contributing to this feature.</li>
<li class="tightenable top bottom">Load the Visual Studio Output Window into the vim quickfix file (menu: 
            [11] => cached_wikilink Object
                (
                    [_page] => VisualStudio
                )

            [12] =>  -&gt; Output)</li>
<li class="tightenable top bottom">Get the file from the Visual Studio IDE editor and load it into vim (menu: 
            [13] => cached_wikilink Object
                (
                    [_page] => VisualStudio
                )

            [14] =>  -&gt; Get File)</li>
<li class="tightenable top bottom">Load the current vim file into Visual Studio as the active document (menu: 
            [15] => cached_wikilink Object
                (
                    [_page] => VisualStudio
                )

            [16] =>  -&gt; Put File)</li>
<li class="tightenable top bottom">Load the Visual Studio Task List into the vim quickfix file.  This is useful for easily jumping to compile errors from within vim (menu: 
            [17] => cached_wikilink Object
                (
                    [_page] => VisualStudio
                )

            [18] =>  -&gt; Task List).</li>
<li class="tightenable top bottom">Load the Visual Studio Find Results into the vim quickfix file.  This way you can use the Visual Studio &quot;Find in Files&quot; feature and then navigate the results with vim.  (menu: 
            [19] => cached_wikilink Object
                (
                    [_page] => VisualStudio
                )

            [20] =>  -&gt; Find Results 1 or 
            [21] => cached_wikilink Object
                (
                    [_page] => VisualStudio
                )

            [22] =>  -&gt; Find Results 2).</li>
</ul>
</li>
</ul>
</dd>
</dl>
</div>

        )

    [_description] => To be honest, there is a bit of disinterest, because it causes a disconnect between the two system in a major way... but -- there is hope.  VisVim maybe be dead, but Vim integration with vs.net isn't...
)