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. Here is an example manifest file for an imaginary .
| Code Block | ||
|---|---|---|
| ||
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<wingatePackage packageVersion="1.0">
<package id="{1a3e50d9-bd41-4c1a-a8eb-b81b2aa593f3}" name="Facebook sanitiser" description="Turns all Facebook pictures into pictures of cats" >
<modules>
<module name="Facebook Sanitiser" host="UI" id="{2a1d44a9-db14-2c3c-a1eb-b61b3db697e3}" subPath="" debugPath="UI\Debug" releasePath="UI\Release">
<dependencies>
<dependency file="FBSanitiserUI.dll" description="Sanitiser UI dll" entryPoint="1" >
<md5 value="" />
<platform os="Any" />
<destination value="local" />
<signInfo path="%SourceRoot%\MyModules\FBSanitiser\UI\Release" />
</dependency>
</dependencies>
</module>
<module name="Facebook Sanitiser" host="Engine" id="{0b3b5011-ca0d-23d6-a9ea-711c5b43f7bd}" subPath="" debugPath="Engine\Debug" releasePath="Engine\Release">
<dependencies>
<dependency file="FBSanitiserEng.dll" description="Sanitiser Engine dll" entryPoint="1" >
<md5 value="" />
<platform os="Any" />
<destination value="local" />
<signInfo path="%SourceRoot%\MyModules\FBSanitiser\Engine\Release" />
</dependency>
</dependencies>
</module>
</modules>
</package>
</wingatePackage> |
...