WinGate SDK
Page tree
ConfigureSpace tools
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

NOTE: Do not distribute your WinGate plugin using the beta SDK as it may not work with a WinGate built against the final SDK.

Getting your product ready for distribution is relatively easy.

  1. Run ManifestPrep over your manifest file. See these instructions on how to use ManifestPrep.
  2. Package up your files using whichever method you choose.
  3. Distribute.

Installing your plugin so it works with WinGate

There are a few things you need to do in order for your plugin to be noticed and loaded by WinGate.

 

Under the registry key HKLM\Software\Qbik Software\WinGate\Packages you need to create a key which has the same name as the package UUID in your manifest file. e.g. HKLM\Software\Qbik Software\WinGate\Packages\{F83CE035-1BA1-4B8A-BAB3-81FC56BD33D9}

Under that UUID registry key needs to be a string value named Manifest whose data is the entire path to the manifest file. e.g. C:\Program Files (x86)\MyCompany\MyWinGatePlugin\MyPlugin.manifest.

As of this version of the SDK, all files that form part of your package must reside in the same directory as the manifest file if they are to be part of the module synchronisation process between the WinGate engine and WinGate Management Console.

 

 

  • No labels