Bug 40097 - Breaking upon all exceptions
Summary: Breaking upon all exceptions
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Android
Classification: Xamarin
Component: Debugger ()
Version: 6.0.1 (C6SR1)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-04-05 08:32 UTC by Jonas Nielsen
Modified: 2017-06-28 10:13 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NOT_REPRODUCIBLE

Description Jonas Nielsen 2016-04-05 08:32:50 UTC
The debugger breaks whenever an exception is fired, even though the Common Language Runtime Exception Box is unchecked. How can you turn off the breaking on exception?

I've tried reseting to default setting, checking and unchecking the Exceptions settings box, restarting Visual Studio 2015, restarting the computer and reinstalling the app on the device.

I'm writing an c# project for android and iOs and the same is happening for iOs.
Comment 1 Prashant [MSFT] 2017-06-28 10:13:22 UTC
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!