« Previous Next »

• 06-23-2009, 9:04 AM

  mtanneryd Joined on 12-13-2007, 11:17 AM Posts 1

  Failing to publish wep application due to providerOption element in web.config Reply Contact Hi! I'm trying to publish my web application, using WebDav, to a windows web server 2008 x64 and it almost works. Request filtering is off so all files, except web.config, are properly uploaded. Web.config fails to upload because the validation of the file fails. Looking in the logfile it says "Unrecognized element 'providerOption'". It seems to me as if, whoever is doing the validation, does not recognize the following section in my web.config:  <system.codedom>     <compilers>       <compiler language="c#;cs;csharp" extension=".cs" type="Microsoft.CSharp.CSharpCodeProvider,System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" warningLevel="4" compilerOptions="/warnaserror-">         <providerOption name="CompilerVersion" value="v3.5"/>       </compiler>     </compilers>   </system.codedom> Any ideas on how to resolve this? Can the validation be disabled? Can the validator be forced to understand the above config section? After all, it is Microsoft generated... /Måns

• 06-23-2009, 3:25 PM

  In reply to

  keithmo Joined on 01-08-2004, 2:50 AM Posts 30

  Re: Failing to publish wep application due to providerOption element in web.config Reply Contact Validation fails because the web.config conflicts with the FX_schema.xml file installed on the server. You need to update the schema file. I don't know the exact process for this; I hope someone else will chime in with details. You cannot disable web.config validation, and even if you could, it would be a very bad idea. If not for validation, the server would see the invalid web.config at run time and generate 500-level HTTP status codes until corrected. If this were to happen, the only way to correct the invalid web.config would be through some mechanism other than HTTP (local file system, SMB sharepoint, etc).