Bug 4192 - [CorDebugger] Windows ASP.NET debugger does not support 4.0 framework
Summary: [CorDebugger] Windows ASP.NET debugger does not support 4.0 framework
Status: RESOLVED DUPLICATE of bug 3708
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: Trunk
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
: 4224 4355 ()
Depends on:
Reported: 2012-04-02 14:52 UTC by Peter Kornfeld
Modified: 2012-10-22 18:08 UTC (History)
7 users (show)

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:

Description Peter Kornfeld 2012-04-02 14:52:23 UTC

I have an ASP.NET project - originally developed on VS 2010 - that runs on
framework 4.
MonoDevelop 2.6 b3 opened it with no problems and I also can run it just fine.
However, when trying to debug I got errors that indicates that the debugger
loaded the framework 2...

/* ERROR */
Server Error in '/' Application.

Configuration Error

Description: An error occurred during the processing of a configuration file
required to service this request. Please review the specific error details
below and modify your configuration file appropriately. 

Parser Error Message: Unrecognized attribute 'targetFramework'. Note that
attribute names are case-sensitive.

Source Error: 

Line 12:  </connectionStrings>
Line 13:  <system.web>
Line 14:         <compilation debug="true" targetFramework="4.0">
Line 15:         </compilation>
Line 16: 

Source File: C:\m2000_net\Local\ControlTest\ControlTest\web.config    Line: 14 

Version Information: Microsoft .NET Framework Version:2.0.50727.5444; ASP.NET

Comment 1 Peter Kornfeld 2012-04-02 14:54:48 UTC
Checked also with version - same results...
Comment 2 Mikayla Hutchinson [MSFT] 2012-04-02 15:54:10 UTC
This is a known limitation of MD's debugger addin, though I don't believe we have another bug open right now. You can work around it by installing Mono and setting the target runtime to Mono - that way you'll use the Mono debugger.
Comment 3 Mikayla Hutchinson [MSFT] 2012-04-02 15:54:37 UTC
Clarification: known limitation of MD's *.NET* debugger addin
Comment 4 Peter Kornfeld 2012-04-03 12:32:04 UTC

I installed mono and added it to MD - the debugger works perfectly.
Mono 2.10.8

(Status change? I do not know the rules...)
Comment 5 Mikayla Hutchinson [MSFT] 2012-04-03 13:23:52 UTC
It's still a valid bug, there's just happens to be a good workaround :)
Comment 6 Jeffrey Stedfast 2012-04-10 15:38:31 UTC
*** Bug 4224 has been marked as a duplicate of this bug. ***
Comment 7 Jeffrey Stedfast 2012-04-10 15:41:36 UTC
*** Bug 4355 has been marked as a duplicate of this bug. ***
Comment 8 Jeffrey Stedfast 2012-04-24 12:11:23 UTC
Michael: how would I fix this? I'm not clear what needs to change.
Comment 9 Mikayla Hutchinson [MSFT] 2012-04-25 12:46:52 UTC
Dunno, ask Lluis, he wrote it.
Comment 10 Jeffrey Stedfast 2012-04-26 15:53:11 UTC
*** Bug 3537 has been marked as a duplicate of this bug. ***
Comment 11 Peter Kornfeld 2012-05-10 15:11:43 UTC
Just for follow-up...

I tried on:

Fedora 16
mono 2.10.5
MD 2.8.1
Apache 2.22.2
mod_mono 2.10

And debugging .NET 4 works perfectly...
Comment 12 Jeffrey Stedfast 2012-05-10 15:24:11 UTC
This is a bug only when using the Microsoft debugger (which obviously you can't use on Linux).
Comment 13 Peter Kornfeld 2012-05-10 16:33:24 UTC
Of course. I only added this information for people who looking for - like me - to leave Microsoft Windows. I thought that a bug like this can stop them on the way. Even this bug was linked to the Microsoft debugger it can be a serious 'what if...' on the way. I was sure that knowing that no problem will await at the other end can help...
Comment 14 Jeffrey Stedfast 2012-10-22 14:06:19 UTC
*** Bug 3807 has been marked as a duplicate of this bug. ***
Comment 15 Jeffrey Stedfast 2012-10-22 18:08:57 UTC
ok, it was a duplicate afterall...

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