Read Me

This project consists of 2 utilities to assist in the use of Microsoft Visual Studio 2005 via a command line interface.

The utilities:
    vs_commander 
    sends commands to a running instance of VS

    InsideMan
    Visual Studio addin for executing custom commands. 
    Note that these may be invoked by vs_commander

GLOSSARY:
    addins dir - typically "My Documents\Visual Studio 2005\Addins"
    IM - expand this to InsideMan
    VC - expand this to vs_commander

INSTALLATION:
    - build both projects in Visual Studio
    - copy the InsideMan.Addin and InsideMan.dll file from the InsideMan
      directory to your addins dir
    - copy the .dll file from the InsideMan/bin to your addins dir
    - update the path to the dll inside InsideMan.Addin
    - move the vs_commander.exe file from vs_command/bin to wherever you want
      it to be. perhaps some utilities directory? You'll be calling this
      execuatable from any environment that needs to invoke the powers of Visual
      Studio so it's up to you.

TO DEBUG/DEVELOP:
    - copy the "InsideMan.AddIn" file into your addins directory 
    - fixup the path contained in the file so that VS can find InsideMan.dll.
      I set this to be in the bin/debug/ dir of InsideMan.
    - close all instances of VS
    - temporarily move the .Addin file referenced at the first step
    - open the solution file (vim_apps.sln)
    - replace the .Addin file to it's home in your addins dir
    - debug/develop
    - submit bugs and features back to the project

    NOTE:
    I'm a noob at c# so if anyone is a pro, feel free to fix up codes as
    necessary.

    NOTE:
    Basically the trick here is that any VS instance opened while the .Addin 
    file is in place will load the addin and make you unable to rebuild the dll.

UNINSTALL:
    - remove both the InsideMan.Addin and InsideMan.dll file from your 
      Visual Studio addins directory
    - delete vs_commander.exe from wherever YOU put it.

EXAMPLE USAGE:
I personally use VIM, the greatest editor in the universe. At least the greatest editor that doesn't ensure hook yourself up with an RSI (emacs anyone?).

This is how I use vs_commander from VIM (from my config file):

function! VSCmd(cmd)
    silent execute '!c:\\vs_commander.exe ' . a:cmd
endfunction

map <S-Tab> :call VSCmd('File.OpenFile %:p Edit.GoTo ' . line("."))<CR>
map <F7>    :call VSCmd('InsideMan.Connect.BuildActiveProjectAndViewBuildOrder "" ')<CR>
map <F5>    :call VSCmd('InsideMan.Connect.DebugActiveProjectAndViewBuildOrder "" ')<CR>
map <F9>    :call VSCmd('File.OpenFile %:p Edit.GoTo ' . line(".") . ' Debug.toggleBreakpoint "" ')<CR>