Absolutely and you’re probably already using some of them because the Azure SDK ships with five plugins. The ones we probably use the most are Diagnostics, Caching and RemoteAccess. The other plugins that ship with the SDK are RemoteForwarder, WebDeploy.
Plugins are installed in this directory:
C:\Program Files\Microsoft SDKs\Windows Azure\.NET SDK\[version]\bin\plugins
This project aims to extend the capability of the SDK by providing a wide range plugins with a community maintained library, and a command line installer.
Don’t see anything interesting? Visit http://richorama.github.io/AzurePluginLibrary/ for the complete list of azure plugins.
While I was looking at using Cloud Service Startup Tasks in order get incompatible code bases to cooperate, I came across plugins. At first, they look very appealing and it was extremely tempting to create my own.
Actually, creating a plugin is fairly easy and works like a charm! But here be dragons… This functionality is not documented by Microsoft, consequently if anyone decides to go down this path, they’re pretty much on their own. Personally, I like to think that anything that’s not explicitly documented can change and break without notice. So be warned, these come with no guaranties and with a couple headaches related to deployment, build and maintainability.