4

I am using async await as well as Task.Factory.StartNew in my application but one thing that i noticed changed is that visual studio is no more breaking when an unhandled exception occured

Here is what i mean by before using await enter image description here

but after i turn a method into a Task and use await

enter image description here

It is only captured in the output area in visual studio...

BTW : It is very strange for me as i am new to .Net4.5 please excuse me if failed to illustrate what i need specifically but again what i want to know is

  • How could i make visual studio break on the exceptions when using async await
Gennady Vanin Геннадий Ванин
  • 10,136
  • 11
  • 75
  • 106
Roman Ratskey
  • 5,101
  • 8
  • 44
  • 67

2 Answers2

6

When the debugger says "Exception was unhandled by user code", what it means is that an exception has propagated up to the framework. Since an async Task method places its exceptions on its returned Task, the exception does not propagate to the framework. An exception like this is unobserved.

If you want the debugger to break when exceptions are thrown, then use Debugger -> Exceptions -> Check the "Thrown" box for CLR Exceptions.

If you want to observe the exception, then change from TaskFactory.StartNew to Task.Run and call Wait on the returned Task. This will propagate the exception (wrapped in an AggregateException) through Main and up to the framework.

Stephen Cleary
  • 437,863
  • 77
  • 675
  • 810
1

That's why void returning async methods are evil.

On the first case the exception is not caught and the debugger is alerting you of just that.

On the second case it will be on the resulting task.

If you handle the exceptions inside the method you'll see similar behavior.

Task.Run is just a streamlined version of TaskFactory.StartNew: Task.Run vs Task.Factory.StartNew

Paulo Morgado
  • 14,111
  • 3
  • 31
  • 59