Installation

MMALSharp has support for Mono 4.x, and experimental support for .NET Core 2.0 Preview (using .NET Standard 1.6). Installation differs between both runtimes, and the source code is shared between both runtimes.

Mono

Installation for Mono differs between the original Model A/B/B+/Zero boards and the newer Pi Model B 2/3 boards running the ARMV7/8 chipsets.

Model A/B/B+/Zero

The version of Mono currently available in the Raspbian repositories is 3.2.8 and isn't compatible with this library. Therefore, we need to do a few extra steps to get a compatible version installed. Luckily, member 'plugwash' from the Raspberry Pi forums has built a version of Mono and provided a repository from which we can install.

In order to install the required version, please open a console window and follow the below steps:

Run sudo nano /etc/apt/sources.list
On a new line, enter deb http://plugwash.raspbian.org/mono4 wheezy-mono4 main
Run sudo apt-get update && sudo apt-get upgrade
Run sudo apt-get install mono-complete

Once completed, if you run mono --version from your command window, you should see the mono version 4.0.2 returned.

Model B 2/3

Using a later model of the Raspberry Pi allows you to install the latest Mono version from the Mono repositories without issue. To do so, please follow the below steps:

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF
echo "deb http://download.mono-project.com/repo/debian wheezy main" | sudo tee /etc/apt/sources.list.d/mono-xamarin.list
sudo apt-get update && sudo apt-get upgrade
sudo apt-get install mono-complete

Continued

Once Mono is installed, a build script is available in the MMALSharp repository which will download all required NuGet packages and then subsequently build the project for you and output a NuGet .pkg file which you can use in your application.

Pre-release builds are available from Myget

.NET Core

.NET Core is currently available on the Raspberry Pi 2 & 3 boards, using an Ubuntu flavoured distribution, e.g. Ubuntu MATE 16.04 (LTS).

Please note: The install instructions for .NET Core have changed since support was added. If you're having any issues running MMALSharp on .NET Core, please raise an issue and I'll look into it for you.

Installation

Follow the instructions here on how to create a self-contained application for use on your Raspberry Pi.
Clone MMALSharp by running git clone https://github.com/techyian/MMALSharp.git
Enter the .paket directory and run paket.bootstrapper.exe
When complete, a new executable paket.exe can be found in the same directory - run paket install which will install all dependencies required for MMALSharp.
Change directory back to the root solution level cd ..
Run dotnet restore which will configure the .NET Core projects.
Within your new .NET Core solution, add the MMALSharpCore, MMALSharpCore.Common and MMALSharpCore.FFmpeg projects.
Apply one of the examples to your Program.cs file in your new .NET Core app, adding any namespaces as required.
Browse to the location of your new app in command prompt
Run dotnet restore which will configure the .NET Core projects.
Run dotnet publish -r linux-arm - this will create a new directory called publish within the debug directory of your new application.
Copy the contents of that folder over to your Raspberry Pi
You should now have a self-contained application that can be ran on your Raspberry Pi.

Building from Source

** These instructions apply to Mono 4.x - for .NET Core build instructions, please see above.**

If you wish to build from source, follow the below steps:

Clone the repository by running git clone https://github.com/techyian/MMALSharp.git
Enter the .paket directory, and run paket.bootstrapper.exe - this will download an executable paket.exe within the same directory
Run paket.exe install to download all NuGet packages required by MMALSharp.
Open the solution in Visual Studio
Build the MMALSharp, this will subsequently build MMALSharp.Common - if you require the FFmpeg helper methods, build the MMALSharp.FFmpeg project too. This will then output the relevant .dll files you need to reference in your application.