diff options
Diffstat (limited to 'src/VisVim/VsReadMe.txt')
-rw-r--r-- | src/VisVim/VsReadMe.txt | 91 |
1 files changed, 91 insertions, 0 deletions
diff --git a/src/VisVim/VsReadMe.txt b/src/VisVim/VsReadMe.txt new file mode 100644 index 0000000..f480c6b --- /dev/null +++ b/src/VisVim/VsReadMe.txt @@ -0,0 +1,91 @@ +======================================================================== + DEVELOPER STUDIO ADD-IN : VisVim +======================================================================== + + +The Add-in Wizard has created this VisVim DLL for you. This DLL not only +demonstrates the basics of creating a Developer Studio add-in, but it is also +a starting point for writing your own add-in. + +An add-in mainly does two things. + (1) It adds commands to Developer Studio, which can then be tied + to keystrokes or toolbar buttons by the user or programmatically + by the add-in. + (2) It responds to events fired by Developer Studio. +In both cases, the add-in code has access to the full Developer Studio +Automation Object Model, and may manipulate those objects to affect the +behavior of Developer Studio. + +This file contains a summary of what you will find in each of the files that +make up your VisVim DLL. + + +VisVim.h + This is the main header file for the DLL. It declares the + CVisVimApp class. + +VisVim.cpp + This is the main DLL source file. It contains the class CVisVimApp. + It also contains the OLE entry points required of inproc servers. + +VisVim.odl + This file contains the Object Description Language source code for the + type library of your DLL. + +VisVim.rc + This is a listing of all of the Microsoft Windows resources that the + program uses. It includes the sample toolbar bitmap that is stored + in the RES subdirectory. This file can be directly edited in Microsoft + Developer Studio. + +res\VisVim.rc2 + This file contains resources that are not edited by Microsoft + Developer Studio. You should place all resources not + editable by the resource editor in this file. + +VisVim.def + This file contains information about the DLL that must be + provided to run with Microsoft Windows. It defines parameters + such as the name and description of the DLL. It also exports + functions from the DLL. + +VisVim.clw + This file contains information used by ClassWizard to edit existing + classes or add new classes. ClassWizard also uses this file to store + information needed to create and edit message maps and dialog data + maps and to create prototype member functions. + +///////////////////////////////////////////////////////////////////////////// +Add-in-specific files: + +DSAddIn.cpp, DSAddIn.h + These files contain the CDSAddIn class, which implements the + IDSAddIn interface. This interface contains handlers + for connecting and disconnecting the add-in. + +Commands.cpp, Commands.h + These files contain the CCommands class, which implements your + command dispatch interface. This interface contains one method + for each command you add to Developer Studio. + These files also contain stub implementations of handlers for all events + fired by the Developer Studio Application object. + +OleAut.cpp + These files contain a general OLE automation class used to communicate + with vim. + +Reg.cpp + These files contain functions to access the registry. + + +///////////////////////////////////////////////////////////////////////////// +Other standard files: + +StdAfx.h, StdAfx.cpp + These files are used to build a precompiled header (PCH) file + named VisVim.pch and a precompiled types file named StdAfx.obj. + +Resource.h + This is the standard header file, which defines new resource IDs. + Microsoft Developer Studio reads and updates this file. + |