Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6779895
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T16:26:32+00:00 2026-05-26T16:26:32+00:00

In looking at various C# Async CTP samples I see some async functions that

  • 0

In looking at various C# Async CTP samples I see some async functions that return void, and others that return the non-generic Task. I can see why returning a Task<MyType> is useful to return data to the caller when the async operation completes, but the functions that I’ve seen that have a return type of Task never return any data. Why not return void?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-26T16:26:32+00:00Added an answer on May 26, 2026 at 4:26 pm

    SLaks and Killercam’s answers are good; I thought I’d just add a bit more context.

    Your first question is essentially about what methods can be marked async.

    A method marked as async can return void, Task or Task<T>. What are the differences between them?

    A Task<T> returning async method can be awaited, and when the task completes it will proffer up a T.

    A Task returning async method can be awaited, and when the task completes, the continuation of the task is scheduled to run.

    A void returning async method cannot be awaited; it is a “fire and forget” method. It does work asynchronously, and you have no way of telling when it is done. This is more than a little bit weird; as SLaks says, normally you would only do that when making an asynchronous event handler. The event fires, the handler executes; no one is going to “await” the task returned by the event handler because event handlers do not return tasks, and even if they did, what code would use the Task for something? It’s usually not user code that transfers control to the handler in the first place.

    Your second question, in a comment, is essentially about what can be awaited:

    What kinds of methods can be awaited? Can a void-returning method be awaited?

    No, a void-returning method cannot be awaited. The compiler translates await M() into a call to M().GetAwaiter(), where GetAwaiter might be an instance method or an extension method. The value awaited has to be one for which you can get an awaiter; clearly a void-returning method does not produce a value from which you can get an awaiter.

    Task-returning methods can produce awaitable values. We anticipate that third parties will want to create their own implementations of Task-like objects that can be awaited, and you will be able to await them. However, you will not be allowed to declare async methods that return anything but void, Task or Task<T>.

    (UPDATE: My last sentence there may be falsified by a future version of C#; there is a proposal to allow return types other than task types for async methods.)

    (UPDATE: The feature mentioned above made it in to C# 7.)

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I was looking at the various windows styles flags, and I noticed that a
Looking at various pages in the Android docs , some of them list Known
I'm currently looking at various middleware solutions that will allow me to create applications
Just looking at various ways of ftp'ing a file in c#. I noticed some
While looking over various PHP libraries I've noticed that a lot of people choose
I've been looking at various PHP/AJAX file upload plugins online, but I'm having some
I was looking at some various sample code for processing mouse click events in
I am looking for various approaches for supporting some level of intellisense on a
Using Pythons (2.7) 'json' module I'm looking to process various JSON feeds. Unfortunately some
I have been looking at various dependency injection frameworks for .NET as I feel

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.