Page tree
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

Version 1 Next »

On this page:

Summary: this section provides information about sharing a custom extension you have created.


If you have created a custom extension that you are actively using and you think other users could benefit from this, you can share your extension:

  • with the wider CAST community using CAST's "NuGet" server for third-party custom extensions
  • within your organization using your own "NuGet" server

NuGet server

CAST uses the free and open source package manager known as NuGet to distribute CAST AIP extensions (whatever the author).

In addition if you do not have internet accesse or for any other reasons, you can also install a NuGet server in your own organization if you want to distribute CAST custom extensions internally.


Publishing extensions

First step : create the NuGet package

First you need to build a .nupkg file from that folder


Use Share a custom extension command line action pack with the path to the plugin.nuspec as parameter. Place yourself outside of your extension directory, for example just above:

set EnableNugetPackageRestore=true

NuGet.exe pack\plugin.nuspec

If succeed, it will create a file.

nuget pack command ignore empty directories. So those emply directories will not be included in the resulting package. If you need to rely on existence of empty directories inside your extension you need to do a 'on demand' creation of that directory inside your own code.

Known examples are:

  • Temporary folder for UA preprocessing
    • Configuration\Languages\<language>\plugin\gen
    • Configuration\Languages\<language>\plugin\results
    • Workaround is to create them if needed


Second step : publish  the extension for sharing

You have several solutions for sharing extensions :

  • have an http server and publish to it
  • have a shared folder and copy nupkg files into it


The HTTP server way

You need a NuGet server.

Here we assume that you publish to the existing CAST NuGet Server located here :

Command line for uploading a nupkg to this server :

NuGet.exe push -s password


where <password> is the server password (not mentioned here, you need to ask the server administrator).


Then this plugin will be available through ExtensionDownloader as the server is activated by default.

The Shared folder way

Simpler : copy the into that folder.

Then this plugin will be available through ExtensionDownloader if you have configured that folder path as an active server.


  • No labels