The 'MonoDevelop' package in your SoftwareCenter includes Monodevelop 2.8.6.3 and Mono 2.10.8.1.
You may check the mono version by typing "mono -V" in a terminal.
Using these tools and AsyncWcfLib, you may develop applications exchanging messages with their counterparts on Windows boxes.
In order to be linked to the correct framework (.NET3.5 - 4.5 or Mono) the applications must be compiled both for Windows and Linux.
Applications using the async-await programming pattern may not be compiled for Linux.
The Mono framework supports Task based asynchrony as in .NET 4.0 but not async-await keywords as in .NET 4.5.
Test1 may be started in a linux terminal. Test2 is running with WinForms.
For startup, graceful- and exceptional shutdown of these mono applications the class 'WcfApplication' has been added. It handles the different exit procedures on Windows and Unix.
Ubuntu 10.4 was distributed with mono 2.4.
You can build AsyncWcfLib with 'monodevelop'. The projectfiles are included starting from AsyncWcfLib 2.0 (trunk).
The tests will start, but WCF communication cannot be established with mono 2.4.
Mono's WCF assemblies were still under heavy development.
It was recommended to build mono and monodevelop from source and install it in '/opt/mono-2.6', parallel to your standard installation in '/usr'.
This is a very safe way to keep your essential mono assemblies untouched while experimenting with latest mono developments.
To start a program under new mono, you will have to prefix the commandline with 'mono-2.6'.
To set environment variables in a terminal to new mono, you will have to enter 'source mono-2.6-environment'.
The scripts in AsyncWcfLib, e.g Test1.cmd.sh are prepared for the parallel mono environment.
Links: