jasells

> I think this is a breaking change, as you are changing a return type. > @drewnoakes what do you think? I didn't realize Run was public. BUT, while technically...

I haven't forgotten about this PR. Been busy with holidays and getting back to work. I will try to address the concerns raised here this week and issue an update.

OK, so I pushed up several new commits to (hopefully) address the breaking API concerns, while still fixing the sync issues by *adding* `Task RemoveAsyc()` and `Task RunAsync()` methods and...

Hopefully, resolved all conflicts, and concerns...

So, just checking in. Haven't seen any response in 10 days.

For some reason, I didn't get any notifications about the comments. I'll look into them over the next few days.

OK, so does this PR have a chance, or are you guys ignoring it. If the latter, I'll just fork and move on with my life.

Is the only remaining issue the `AddAsync` comment? I replied, but never got a response. In case it is unclear, I see no need for `AddAsync`, but they could be...

> Also could you have the FCC Output Window Pane open and provide the progress state when this occurs. Sure thing!

> > FCC item will not expand (sometimes), gives spinny-circle busy cursor when clicked > > close all instance of VS to clear this state, > > How long had...