RegisterAsyncFunction in 2.1.0.1 fires callback on dispatcher

[darkmyst]

When running the Awesome People sample app for v2.1.0.1, the flickr picture fetching code uses ReactiveAsyncCommand.RegisterAsyncFunction(..). It should fire the callback on some other thread (the Taskpool by default, it looks like), but it seems to be firing on the dispatcher thread. I've made some cursory attempts to get it to fire on another thread by passing in an explicit scheduler to the ReactiveAsyncCommand constructor and the RegisterAsyncFunction method but one way or another it seems to either fire on the dispatcher thread (blocking the ui) or crash complaining about accessing an object that belongs to another thread.

[darkmyst]

This may not be an issue at all with the recent rewrite, of course.

[anaisbetts]

Thanks for the bug report! This is fixed in the upcoming release