Bug 12603 - [CorDebugger] COMException while attempt to debug ASP.NET application
Summary: [CorDebugger] COMException while attempt to debug ASP.NET application
Status: RESOLVED DUPLICATE of bug 13508
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: 4.0.8
Hardware: PC Windows
: Normal normal
Target Milestone: master
Assignee: Bugzilla
Depends on:
Reported: 2013-06-07 22:55 UTC by J.Fan
Modified: 2013-09-16 17:18 UTC (History)
3 users (show)

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

Screenshot of the exception (46.28 KB, image/png)
2013-06-07 22:55 UTC, J.Fan

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 J.Fan 2013-06-07 22:55:19 UTC
Created attachment 4084 [details]
Screenshot of the exception

Description of Problem:

Steps to reproduce the problem:
1. Create a new non-empty web application(or mvc application)
2. run with debug

Actual Results:

Expected Results:
no exception

How often does this happen? 
every time

Additional Information:
Comment 1 Jeffrey Stedfast 2013-06-08 14:11:00 UTC
you are probably trying to debug a 64bit application. you can only debug 32bit when running on the Microsoft .NET runtime right now.
Comment 2 Marius Ungureanu 2013-09-16 17:18:28 UTC

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