if Task.Run runs a task in async then why and when i should write asyn

Question

q1) does Task.Run creast async task? (it is writen it runs on an other thread.) q2) if it does create async task then why and when we need Task.Run(async ()={}). pls explan with examples.

Jack Abroy · Answer

Use async to write clear, non-blocking code that naturally handles asynchronous work. Task.Run just offloads work to a thread async is better for I/O tasks and responsiveness.

Deepika Sawant · Answer

Q1: Does Task.Run create an async task? Yes , but with a nuance. Task.Run queues work to the thread pool and returns a Task that represents that work. If you pass a synchronous delegate , it runs on a background thread. If you pass an async delegate , it still starts on a background thread, but the await inside the delegate allows the thread to be released during I/O-bound operations. Q2: Why and when do we use Task.Run(async () => { ... }) ? This pattern is useful when: You're in a non-async context (like a button click handler or legacy code). You need to run async code without changing the method signature to async . You want to offload async I/O-bound work to avoid blocking the UI thread. When NOT to use Task.Run(async () => { ... }) If you're already in an async method , just await the async call directly. Don't use it to wrap async code unnecessarily—it adds overhead and can lead to thread pool exhaustion.

if Task.Run runs a task in async then why and when i should write asyn

Insert Link

Embed YouTube Video

Table Options

Insert Image

Answers (2)