Configuration

WebEdit.NET persists information related to the application's configuration in various files. These are mostly XML files.

Configuration Files

Configuration files store things like program settings, toolbar configuration, the document history, the FTP cache, and so on.

Most configuration files are either edited by means of WebEdit's GUI (for example, via the Settings dialog, or indirectly by arranging tool windows). WebEdit.NET loads and saves configuration automatically when needed. If you want to edit a configuration file by hand, make sure the application is not running, or else your changes will be overwritten.

Configuration files are normally stored in the "AppConfig\<Profile-Name>" sub directories of the installation directory. For example, "C:\Programs\WebEdit\AppConfig\Default".

With the "/usersettings" start option, the "Gregor.NET\WebEdit" sub directory of the user's local application data repository is used alternatively to store customized files. For example, "C:\Documents and Settings\John Doe\Application Data\Gregor.NET\WebEdit\AppCustom\Default").

In both cases, the "/profile:<name>" option can be used to choose a configuration profile, so selecting a profile subdirectory. If no profile is given, "Default" is assumed. Any missing directories are created as needed.

Here's the list of the configuration files:

    - WebEditSettings.xml:    general program settings
                              (Tools/Settings)

    - WebEditToolbars.xml:    toolbars customization (button selection,
                              text/icon display, textual command buttons)

    - WebEditToolWindows.xml: workspace and user interface stuff

    - WebEditLanguages.xml:   syntax coloring, auto-complete,
                              auto-conversion, and edit assistance
                              customization

    - WebEditTemplates.xml:   a list of templates for quick access
                              with the templates dialogs

    - WebEditSearches.xml:    recent criteria for the find/replace
                              tool window

    - WebEditHistory.xml:     the document history (can be edited
                              manually if the history gets too big)

    - WebEditCache.xml:       the FTP cache

The files, too, are created when needed, but there will be an error message for missing files nevertheless.

Saving configuration can be suppressed with the "/keepsettings" start option.

Settings

Settings are configuration points controllable through the settings dialog ("Tools"/"Settings" menu item) and saved to the "WebEditSettings.xml" file.

[to be supplied]

Language Configuration

Language configuration resides in the file WebEditLanguages.xml. Any relative paths therein (such as references to alias files or token lists) specified in "relpath" attributes are relative to the location of the languages configuration file (ig., C:\Programs\WebEdit.NET\AppConfig\Default).

The following things may be configured per language:

• File Extensions for automatic language detection.
• Custom keywords with range categories for syntax coloring (this is supported by most syntax parsers).
• A syntax parser type.
• A syntax provider type (for ScriptAddIns, assembly browser syntax).
• An auto converter type (for automatic editing conversions).
• An outline provider (for Outline tool window contents).
• A code assistant type (for assembly browser based wizardry).
• A code DOM provider type (for Script AddIn compilation).
• A fixup provider (for Script AddIn code snippet wrapping).
• A code tokenizer, code parser, and code interpreter (this information is not being used for code evaluation yet: it's always .NET Console).
• Token List files for AutoText.
• Special, Token Lists defined by the application or AddIns (such as the document list, called "Document") for AutoText.
• Alias files for alias substitution in AutoText.
• Build commands (selected via the "Build" menu).

For syntax details and examples, see the original WebEdit distribution.

Template Configuration

[to be supplied]

Other Files

Note that the application may optionally use other resources, such as projects (collections of documents and textual commands) or additional token lists. These things are stored at places specifically chosen by the user.

Note that for projects, the user is promted for saving on exit. Changes to token lists are saved automatically.

.NET Framework Configuration

Certain settings in the Machine.config XML file, which can be found in the framework directory (ig., C:\WINNT\Microsoft.NET\Framework\v1.1.4322\Config), affect WebEdit.NET.

Proxy Settings

If you connect to the internet via a proxy, you may need to specifiy the proxy address in the /configuration/system.net/defaultProxy/proxy element. Normally, .NET uses the system default, which is what you can configure in the Internet Settings control panel applet. However, this does not work if "configuration scripts" or "automatic configuration" are used (see the comments in the config file). Here's an example for to configure a proxy in these two cases:

<!-- Machine.config -->
<configuration>
    <!-- ... -->
    <system.net> 
        <!-- ... -->
        <defaultProxy>            
            <!-- ... -->
            <proxy usesystemdefault="false"
                   proxyaddress="proxy.mydomain.com"
                   bypassonlocal="true" />
            <!-- original: <proxy usesystemdefault="true" /> -->
<!-- ... -->

The proxy story affects any HTTP-related features in WebEdit.

See Also: Setting Up WebEdit | Start Options