Added functionality to the UI and Agent that will help to intergrate Crank into D-Crank

(My 2 cents) I personally don't like async void methods used to implement fire-and-forget. As per http://msdn.microsoft.com/en-us/magazine/jj991977.aspx "Avoid Async Void. (...) Void-returning async methods have a specific purpose: to make asynchronous event handlers possible" so using them for fire and forget is a way of abusing the design. Another concern is - how (in general) you are going to test async void methods? Because they do not return a Task they cannot be awaited so you will never be able to assert that the method works correctly. If using async avoid is just a means to suppress the warning then you probably can use `Task.Run()` and you should not get the warning. I also think this increases the readability/intentionality of using the fire-and-forget pattern because if you wanted to use the method in the regular async way you would just use await and not Task.Run.