Beaver Config File

Overview

Beaver reads an optional configuration file named Beaver.config when it starts up.
The file describes what Beaver should set up at start-up. At the moment it is used to
list the plug-in DLLs that are loaded automatically.

The file is plain XML, so you can edit it with any text editor, keep it under version
control, and copy it to another machine.

Location

Beaver.config must be placed in the same folder as Beaver.exe.

C:\Program Files\Beaver\Beaver.config
C:\Program Files\Beaver\Beaver.exe

The file is optional. It is not created by the installer, and Beaver starts normally
when it does not exist. Create it yourself when you want to load your own plug-ins.

Format

<?xml version="1.0" encoding="utf-8"?>
<BeaverConfig Version="1">
  <Plugins>
    <Plugin Path="MyPlugin.dll" />
    <Plugin Path="C:\MyPlugins\Another.dll" />
  </Plugins>
</BeaverConfig>

Plugins

Each <Plugin> element names one .NET plug-in DLL to load at start-up.

The DLLs listed here are loaded in addition to the plug-ins that ship with Beaver, so
you do not have to list the standard Beaver DLLs.

Each DLL that is loaded is reported in the Command view, so you can check at a glance
which plug-ins came from this file.

See “.Net API” for how to write a plug-in DLL.

Notes

The file is read once, while Beaver starts up. Restart Beaver after you edit it.

If you only want to try a DLL out without editing the file, use the NETLOAD command.
It loads a DLL into the running session, and the effect is lost when you exit Beaver.

If a DLL cannot be found or cannot be loaded, Beaver reports it in the command pane and
carries on starting up. If Beaver.config itself cannot be read as XML, Beaver reports
that in the command pane and starts without loading any plug-in from the file. A mistake
in the file never prevents Beaver from starting.