memsdev(1)

[Home] [Commands] [Variables] [Macro-Dev] [Glossary]

NAME

memsdev - Microsoft Developer Studio Add-in for MicroEmacs '02

SYNOPSIS

memsdev.dll

DESCRIPTION

meMsdev is a Microsoft Visual Studio Add-In that allows MicroEmacs '02 to be integrated as the default text editor. It will be used instead of the Visual Studio built in editor when you double click on a file or press F4.

INSTALLATION

1) Copy mesdev.dll into the MicroEmacs directory i.e.

c:/Program Files/JASSPA/MicroEmacs

2) Edit the me32.ini(8) file in your Windows directory and identify the location of the MicroEmacs executable. The executable name is used to spawn MicroEmacs if it is not already running. The entry takes the form:-

; Identify the location of the MicroEmacs executable so that the 
; Developer Studio "Add-In" can locate the executable 
[Location] 
exe=c:\Program Files\JASSPA\MicroEmacs\me32.exe

Change the exe entry to match the location and name of your executable.

3) For MS-DEV V5.0 only; from a DOS box, register the DLL using regsvr32.exe(1) i.e.

> cd c:/Program Files/JASSPA/MicroEmacs 
> regsvr32 memsdev.dll

For MS-DEV V6.0 it is not necessary to perform this registration step.

4) Start Visual Studio and goto:-

Tools 
    Customize... 
        Add-Ins and Macro Files

5) Click on Browse and point Visual Studio to your memsdev.dll file.

6) Click the check box to indicate that you want to use the Add-In, and close the Customize dialog box.

7) You should notice the MicroEmacs tool bar showing the MicroEmacs Icon. This invokes a dialog that allows you to attach and detach MicroEmacs as the default editor.

USING meMsdev

Clicking on the MicroEmacs Tool bar shows the meMsdev configuration dialog. Check the boxes when MicroEmacs edit session is required as default; uncheck the boxes if you wish to revert to the built-in dialog.

Use Visual Studio as normal, and MicroEmacs should almost always bring MicroEmacs to the foreground to edit the document. If a MicroEmacs is already running then "meMsdev" will attach to an existing session and will load the file. If MicroEmacs is not detected then a new version is spawned off and then an attachment is made.

RUNNING A DEBUG SESSION

meMsdev does not currently provide any debugging capability (but we are working on it !!). To start debugging it is suggested that the Editor is decoupled (MicroEmacs Dialogue -> Uncheck Boxes) and work within the Developer studio.

When you have finished debugging and wish to move back to an edit session then re-enable MicroEmacs (MicroEmacs Dialogue -> Check Boxes) AND close any windows that are open within the MS-Dev environment ( Window->Windows...->Select All and Close All Windows). Then commence editing again.

While MicroEmacs is attached, selecting any of the find file lines, compilation error lines etc within the response panes will take MicroEmacs to the specified line.

BUGS

meMsdev works by hooks exposed by Visual Studio. Most of the functionality works from the OpenDocument (look it up in VS 5) hook. So...If a document is ALREADY open in Visual Studio, and you double click the file in the File Browser...Emacs will NOT come to the foreground. Since the document was open in the Visual Studio editor, the OpenDocument event never occurred.

ACKNOWLEDGEMENTS

meMsdev is based on the initial work from VisEmacs performed by Christopher Payne <payneca@sagian.com> for GNU Emacs. This software comes under the GNU General Public License, as such, meMsdev is covered by the same licensing.

Many thanks to Christopher for putting together this technology, this manual page is derived from the documentation supplied with VisEmacs.

LICENSING

meMsdev is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version.

meMsdev is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with GNU Emacs; see the file COPYING. If not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.