Bug 11304 - [CorDebugger] COMException when trying to run/debug a console app
Summary: [CorDebugger] COMException when trying to run/debug a console app
Status: RESOLVED DUPLICATE of bug 13508
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: 4.0.2
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
: 11959 12699 ()
Depends on:
Reported: 2013-03-20 16:09 UTC by Redth
Modified: 2013-09-16 17:18 UTC (History)
4 users (show)

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

Screenshot of Error (88.93 KB, image/png)
2013-03-20 16:09 UTC, Redth

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:

Description Redth 2013-03-20 16:09:58 UTC
Created attachment 3667 [details]
Screenshot of Error

Trying to run/debug a console app that was made in visual studio, but getting a COMException as seen in the attached image...
Comment 1 Jeffrey Stedfast 2013-03-20 16:14:57 UTC
Try with Debug | x86

The CorDebugger currently only supports 32bit mode.

Another workaround would be to install the Mono runtime and target that instead so that Xamarin Studio ends up using Mono's Soft Debugger (which is far better than the CorDebugger backend).
Comment 2 Jeffrey Stedfast 2013-04-25 10:28:35 UTC
*** Bug 11959 has been marked as a duplicate of this bug. ***
Comment 3 Confused 2013-06-14 16:47:14 UTC
*** Bug 12699 has been marked as a duplicate of this bug. ***
Comment 4 Marius Ungureanu 2013-09-16 17:18:32 UTC

*** This bug has been marked as a duplicate of bug 13508 ***