What is the accepted pattern for naming methods that return Tasks?

Question

APM uses BeginXXX/EndXX pairs and the Event-based Asynchronous Pattern (EAP) uses XXXAsync and XXXCompleted pairs, but I haven't seen anything standard on how to name methods that return a task.

I have been using XXXTask:

Data GetData() 
Task<Data> GetDataTask()

but was wondering if a more standard approach has developed

Answer 1

You may consider to provide a Property instead of a GetXXX-Method, which is more usual in C#. You could then write

Task<Data> DataTask { get; set; } //auto-implemented

Answer 2

Not sure what you are doing, but you could wrap tasks into a seperate class.

So instead of having GetPrintTask you'll have MyCustomTasksClass.GetPrint

Answer 3

I'd recommend using the patterns in the ParallelExtensionsExtras library since that's done by the same team that made the TPL in the first place :)

http://blogs.msdn.com/b/pfxteam/archive/2010/05/04/10007557.aspx

Their pattern seems to be the same as yours: [SyncAction]Task for the method that does SyncAction async via a Task (which is returned) - DownloadDataTask, SendTask, etc.