[prev in list] [next in list] [prev in thread] [next in thread]
List: mono-list
Subject: [Mono-list] mod_mono-2.10 barking on targetFramework in web.config
From: Guido Van Hoecke <guivho () gmail ! com>
Date: 2013-10-30 17:01:01
Message-ID: m28uxa4rsi.fsf () gmail ! com
[Download RAW message or body]
Hi,
Yesterday I upgraded my OSX to Mavericks and needed to reinstall mod_mono.
All my .net websites targeting asp.net 4.0 now bark:
System.Configuration.ConfigurationErrorsException Error deserializing \
configuration section compilation: Unrecognized attribute 'targetFramework'
So I removed the 'targetFramework="4.0" attribute from the compilation line.
This results in another problem:
System.Configuration.ConfigurationErrorsException Error deserializing \
configuration section pages: Unrecognized attribute \
'controlRenderingCompatibilityVersion'.
So I then remove 'controlRenderingCompatibilityVersion="3.5"' from the pages line and \
got:
System.Configuration.ConfigurationErrorsException Error deserializing \
configuration section pages: Unrecognized attribute 'clientIDMode'.
As the 'clientIdMode="AutoID"' is the only attribute left on the files node, I just \
completely removed the node.
Then it gets a System.TypeLoadException.
I haven't bothered to look into that problem. These sites were running perfectly well \
before the update, so there must be some configuration thing that I missed out.
AFAIKT I run the latest stable versions of all involved software.
Just intrigued by the fact that the youngest mod_mono I found here, dates from \
'14-Feb-2011 20:39'.
Please advise,
guivho.
(copy of stackoverflow entry at \
http://stackoverflow.com/questions/19661649/mod-mono-2-10-barking-on-targetframework-in-web-config)
_______________________________________________
Mono-list maillist - Mono-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic