Create C# .NET wrapper to call a wordpress json plugin

Create a C# library that serves as a wrapper to call the JSON WordPress plugin. The library implements a class called: WordPressWrapper, which implements the following methods: - CreateOrUpdateBlogPost(...) - CreateOrUpdatePage(...) - CreateOrUpdateImage(...) All three methods should first check whether the blog page already exists. If it does not exists, the content should be added. If it already exists it should be updated. The content in the blog posts and pages will contain mark-up, html links and the uploaded images. This content should be read from a plain text file, ASCII encoding, Windows and Linux style CR+LF should both be supported. This project will have two phases: Phase 1 - Delivery of the design The design is a word document describing the approach and a list of identified risks. Phase 2 - The actual implementation The primary deliverable is a solution is a Visual Studio solution that contains the library project, and a project containing the unit tests (NUnit or MSTest). The standard Microsoft .NET Coding guidelines should be followed, an 80% code coverage is expected. Dependency injection should be done with either Unity or NInject, Mocking with RhinoMocks. All configuration items should be read from the app.config. No third party libraries (except .NET obviously) should be used without upfront permission. If the JSON plugin is missing the features required to implement the functionality in the wrapper library, it's up to you to extend the plugin so that it does. You'll be following the open source guidelines set by the wordpress group, so that the extensions are contributed back to the open source world. Delivery back to the open source world is in scope for this project and will delay project close down and therefore payment. The second deliverable is a word document describing how to configure WordPress and/or the JSON plugin to enable the integration. It is up to you to take care of the development environment like Visual Studio, WordPress, etc including licensing / hosting fees. An incremental approach is needed to ensure the library to also work outside your development environment. So the first code drop would be as soon as possible, with the least amount of functionality to test the portability to both a windows and a Linux environment (running on Mono). We can discuss the details of that later. Payment will happen after the design, the first drop and at the end of the project. Successful applicants will be able to demonstrate similar successful achievements in the past.