Stepping through OxyPlot code while debugging

It is now possible to step through the OxyPlot code while debugging your software. This is available in the latest prerelease and will be available in the next official version. Below is an image that shows the actual OxyPlot code without local source files of OxyPlot:

The advantage of this feature is that the end-developers can get a better understanding of the inner workings of OxyPlot. This is great to encourage pull requests or to find out why something is not working as expected.

To enable stepping through the source code, it is no longer required to set up the SymbolSource.org symbol source. The only thing a developer has to do is the enable the source server support checkbox as shown in the image below.

Support for iOS/Mac Unified APIs

OxyPlot implementations for [Xamarin.iOS] and Xamarin.Mac are now available! To use it, install the NuGet package OxyPlot.Xamarin.Mac or OxyPlot.Xamarin.iOS.

The example plot rendered on a retina display:

Chat room at gitter.im

A chat room has been added at gitter.im. Hopefully this can be a nice supplement to the discussion forum and twitter.

Continuous integration

OxyPlot is now built at AppVeyor. This change has simplified the build system significantly and removed the need for a local build server. AppVeyor provides a great service that does both continuous integration and deployment for all platforms except the Xamarin ones.

The build is configured in the appveyor.yml file and handles both the develop and master branches.

The StyleCop, Gtk# and Lynx Toolkit prerequisities are now installed by chocolatey.

The NuGet packages will be updated by each build. The Xamarin.Android and Xamarin.iOS packages are not included in the AppVeyor build, and are still built locally on a Mac. It would be great if we could get a similar build and deployment solution also for these projects…

The Silverlight “Example browser” will also be updated by each build.

Builds on the develop branch will get a pre-release suffix -alpha in the version numbers. This will make it possible to select between “Stable Only” and “Include Prerelease” versions in the NuGet manager.

Another great feature is that every pull request on GitHub will automatically trig a build on AppVeyor. A broken build will be shown on the pull request page!!

Branches

The origin repository has been split in two branches as described in “A successful Git branching model”:

• master
• develop

The master branch contains the latest stable version of the library.

The develop branch contains all the latest changes and pull request. This is the default branch and all pull requests should be based on this branch.