Windows Phone Plugins

Writing a plugin for Cordova on Windows Phone requires a basic understanding of the architecture of Cordova. Cordova-WP7 consists of a WebBrowser which hosts the application JavaScript code and manages native API calls. There is a BaseCommand (WP7CordovaClassLib.Cordova.Commands.BaseCommand) class in C# which you can extend, and it comes with the majority of the 'plumbing' built for you already.

  1. Select your project, and right-click to choose Add → New Item…
    • Preferably add it to the 'Plugins' folder, but it is up to you
  2. Select 'Class' and name it Echo.cs
    • The name of this class must exactly match what you call into cordova.exec(win, fail, "Echo", ...)
  3. Include the base classes implementation

     using WPCordovaClassLib.Cordova;
     using WPCordovaClassLib.Cordova.Commands;
     using WPCordovaClassLib.Cordova.JSON;
  4. Extend your class from BaseCommand

     public class Echo : BaseCommand
         // ...
  5. Add a method that is callable from JavaScript

     public class Echo : BaseCommand
         public void echo(string options)
             // all JS callable plugin methods MUST have this signature!
             // public, returning void, 1 argument that is a string


The default namespace for unqualified commands is:

namespace Cordova.Extension.Commands
    // ...

If you want to use your own namespace, you need to make a fully qualified call to cordova.exec. For example, if you want to define your C# class like this:

namespace com.mydomain.cordovaExtensions
    public class Echo : BaseCommand
        // ...

Then, in JavaScript you need to call exec like this:

cordova.exec(win, fail, "com.mydomain.cordovaExtensions.Echo", ...);

Interpreting your arguments in C#

The data received by your plugin method is a string value, but in actuality looking at our JavaScript code, we see our intention was to pass an array of strings. Looking back at our JavaScript call to cordova.exec, we see we passed [str]:

cordova.exec(win, fail, "Echo", "echo", ["input string"]);

If we inspect the options string passed in to our Echo.echo method, we see that the value is actually:

"[\"input string\"]"

All JavaScript exec arguments are JSON encoded before being passed into C#.

If we want to treat this as the string we were expecting, we need to decode it. We can use simple JSON deserialization.

string optVal = JsonHelper.Deserialize<string[]>(options)[0];
// optVal now has the value of "input string"

Passing results from C# to JavaScript

The base class BaseCommand provides methods for passing data to your JavaScript callback handlers. To simply signal that the command has succeeded, when no additional result info is needed, you can simply call:

DispatchCommandResult(); // calls back with an empty plugin result, considered a success callback

To pass data back, you need to call a different version of DispatchCommandResult:

DispatchCommandResult(new PluginResult(PluginResult.Status.OK, "Everything went as planned, this is a result that is passed to the success handler."));

To pass structured object data back to JavaScript, it should be encoded as a JSON string:

DispatchCommandResult(new PluginResult(PluginResult.Status.OK, "{result:\"super awesome!\"}"));

If you need to signal that an error has occurred, you can call DispatchCommandResult with a PluginResult object:

DispatchCommandResult(new PluginResult(PluginResult.Status.ERROR, "Echo signaled an error"));

Handling serialization errors in your plugin's C# method

When interpreting your arguments, it is a good idea to use a try/catch block in case we have bad input. This is a pattern used throughout the Cordova C# code:

string optVal = null;

    optVal = JsonHelper.Deserialize<string[]>(options)[0];
    // simply catch the exception, we handle null values and exceptions together

if (optVal == null)
    DispatchCommandResult(new PluginResult(PluginResult.Status.JSON_EXCEPTION));
    // ... continue on to do our work

Plugin XML

These are windows phone specific examples of using the plugin.xml file, refer to the Plugin Specification for more details


On windows phone the <source-file> element is currently used to define all plugin resources (ie. .cs, .xaml, .xaml.cs, .dll, image assets etc).


The <config-file> element defines what elements get put into a config file. For example to add a plugin to the platforms config.xml, you would do something like this :

<config-file target="config.xml" parent="/*">
    <feature name="PluginName">
        <param name="wp-package" value="PluginName"/>
</config-file> If we wanted to add the contacts capability to the WMAppManifest.xml, it would look like this :

<config-file target="Properties/WMAppManifest.xml" parent="/Deployment/App/Capabilities">
    <Capability Name="ID_CAP_CONTACTS" />

Advanced Plugin Functionality

See other methods that you can override in:

For example, you can hook into the 'pause' and 'resume' application events.

Debugging Plugins

To debug the C# side, you can use Visual Studio's debugger, just set a break point at any of the methods exposed by your class.

JavaScript is a little more difficult to debug on Windows Phone. You need to use console.log to output the state of your plugin, or inform yourself of errors.

Common Pitfalls

  • Be careful when deciding on the arguments you pass to native in your JavaScript implementation. Most device platforms expect the args passed to cordova.exec to be an array, but if you have different types of objects in this array, it becomes difficult or impossible to deserialize.

      cordova.exec(win, fail, "ServiceName", "MethodName", ["this is a string", 54, {literal:'trouble'}]);
    • This means that your C# code receives a difficult to decode string value, such as:

        "[\"this is a string\", 54, { literal:'trouble' }]"
    • Consider converting ALL parameters to strings before calling exec:

        cordova.exec(win, fail, "ServiceName", "MethodName", ["this is a string", "54", "{literal:'trouble'}"])	;
        string[] optValues = JsonHelper.Deserialize<string[]>(options);
  • It is usually a good idea to do parameter checking in your JavaScript code, before you call exec. This allows you to re-use more JavaScript code among your plugin's various native implementations.