Download and Setup

Prerequisites

Hardware Requirements

128 MB of RAM (256 MB recommended).
5 MB of free disk space (no recommendations here).
A CPU that runs at 500 MHz (unless it's some sort of Celeron or the like).

Software Requirements

Windows 2000, XP, Vista, or Seven.
Microsoft .NET Framework Version 3.5.

Security Considerations

WebEdit.NET requires certain code access permissions, such as those related to the file system, networking, the clipboard, and using unmanaged code. The CLR security settings for a typical user account should normally suffice.

Download

You want to download WebEdit.NET program files (libraries, executable, configuration, help) off my web site (for .NET Framework version 3.5). This download also includes .NET 3.5 source code.

Please read this page for some general information on download practices and policies.

Installation

The application expects a certain directory structure, as well as the presence of certain configuration files therein. The directory structure and the necessary files are contained in program files archive.

After you've downloaded the program files archive, simply open the zip archive, and extract the files under "Assemblies" to some suitable directory, for example, "C:\Program Files\WebEdit.NET". That's all.

The directory structure should now look as follows (for example, under the "Program Files" directory); directories are in bold type:

WebEdit.NET
    AppConfig
        Default
            (predefined config and support files)
    AppCustom
        Default
            (customized config and support files)
    AppHelp
        (various help files)
    bin
        (the DLLs and the EXE)

Note that if WebEdit starts with the "/usersettings" start option, custom configuration (AppCustom) files will be saved to the "Gregor.NET\WebEdit" sub directory in the "Local Application Data" repository for the current user. Before starting with "/usersettings", you should copy the "AppCustom" folder to that location; otherwise, there will be error messages during startup (although the app will eventually create those file on its own).

WebEdit also supports configuration profiles. See Configuration for more details.

Choosing a .NET Runtime

WebEdit.NET supports the .NET runtime versions mentioned above. You can specify using a particular version by placing a configuration file named "WebEdit.exe.config" into the "bin" subdirectory, with the following content ("v2.0.50727" is for version 2.0, for example):

<configuration>
    <startup>
        <supportedRuntime version="v2.0.50727"/>
        <requiredRuntime version="v2.0.50727"/>
    </startup>
</configuration>

To find out which .NET versions you have installed, open the directory "C:\Windows\Microsoft.NET\Framework", and have a look at the names of the subdirectories therein.

Configuration Trouble Shooting

Have a look at the Configuration topic for information on how .NET Framework configuration can affect WebEdit.NET.

Starting WebEdit.NET

You can start the application by running WebEdit.exe in the "bin" subdirectory. If you create a shell link, I recommend that you set the working directory option (in the link's property page) to the "bin" directory.