All information about your package resides in a manifest file that is loaded by the host process. It describes the modules in the package, and the files and metadata for each module.
From this file is determined entry points for your module(s), dependent files that need synchronising between the WinGate engine and WinGate Management Console and to ensure they haven't been tampered with. In order to prepare a manifest file for distribution you need to run the ManifestPrep utility on it For a manifest to be usable by a retail WinGate, it needs to be signed with the Manifest Prep tool which is found in the tools directory of the SDK.
...
Describes the package as a whole. See About Packages, Modules, Components and Interfaces for more information.
id - The UUID of your package.
...
Root node for the modules within your package. There can be any number of modules in a package.
<module>
Describes a single module within your package.
name - User friendly name of this module.
| Tip |
|---|
You may wish to distinguish between the UI or Engine versions of your module when specifying the name in order to make it easier to identify in the Modules panel in the WinGate Management Console |
...
id - The UUID of the module, including the braces.
subPath - Must be empty.
...
Root path for module dependencies. See About Packages, Modules, Components and Interfaces for more information.
<dependency>
Describes a single dependency file for the enclosing module.
file - The filename of the file
...
os - The operating system that this dependency will be synchronised for. Supported values are AnyWinAny, Nt351WinNt351, Nt4WinNt4, XpWinXp, 2kWin2k, 2k3Win2k3, VistaWinVista, 7Win7, 2k8, 2k8R2 - Windows 8 and 10 TBDWin2k8, Win2k8R2, Win2k12, Win2k12R2, Win8, Win81, Win10
<destination>
value - Where the dependency's destination is. Values are:
...