12

Getting this error:

The value for the 'compilerVersion' attribute in the provider options must be 'v4.0' or later if you are compiling for version 4.0 or later of the .NET Framework. To compile this Web application for version 3.5 or earlier of the .NET Framework, remove the 'targetFramework' attribute from the element of the Web.config file.

It was working on our dev system, and we are now deploying to QA using an xcopy type deploy.

We don't have a "compilerVersion" anywhere in the web.config, and the targetFramework is set to "4.0". We have done an IISReset. 

<system.web>

        <compilation debug="true" targetFramework="4.0">
        <assemblies>
            <add assembly="System.Data.Linq, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
            <add assembly="System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
            <add assembly="System.Web.Extensions.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
            <add assembly="System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
        </assemblies>
    </compilation>

UPDATE 2: when we removed the entire section, we got past the error. So my question is, what is wrong with leaving in this section if we are on .NET 4.0?

We just did a full xcopy of exactly what was in Test to QA, and in QA it gets the error and DEV doesn't. So the software and configs are identical. Why would it work on one server and not another? IIS options seem to be identical.

Cœur
  • 37,241
  • 25
  • 195
  • 267
NealWalters
  • 17,197
  • 42
  • 141
  • 251
  • Possible solution http://stackoverflow.com/questions/3314469/asp-net-4-0-how-do-i-fix-the-compilerversion-iis-error – Raghav Jul 21 '12 at 07:16

4 Answers4

8

taken from: http://www.asp.net/whitepapers/aspnet4/breaking-changes#0.1__Toc256770150

you should go to your server root web.config and include the whole <system.codedom>...</system.codedom> tag content into a <location path="" inheritInChildApplications="false">...</location> tag

Fabio Napodano
  • 1,210
  • 1
  • 16
  • 17
5

Possible solution here - asp.net/whitepapers/aspnet4/breaking-changes#0.1__Toc256770150

Dan
  • 29,100
  • 43
  • 148
  • 207
Naraen
  • 3,240
  • 2
  • 22
  • 20
  • Thanks, but we do want 4.0, and IIS ASP.NET version is set to 4.0.30319. – NealWalters Apr 04 '11 at 23:53
  • 3
    @Neal. That article is for 4.0. Look at the answer. The title is misleading. Somewhere in your web.config hierarchy (application level, site level etc) there is a / tag pointing to .NET 3.5 which is confusing the web server. – Naraen Apr 04 '11 at 23:57
  • the difference is they have – NealWalters Apr 05 '11 at 00:38
  • 5
    the link above is not working anymore. for those who are in trouble, check this MS article: http://www.asp.net/whitepapers/aspnet4/breaking-changes#0.1__Toc256770150 – Fabio Napodano Aug 05 '13 at 10:57
  • @Naraen nailed it. Our main site had the tag specifying v=2.0 and a providerOption v=3.5. I removed them both, and our main site still works, along with the apps in that site that are targetFramework 4.0 and above (now we can leave that compilation tag in the web.config and compile the correct version) – deebs Dec 22 '21 at 16:12
1

After fighting with this for a while, I ended up creating a new IIS site using a different port and adding my ASP.Net 3.5 application to the new site and it is working perfectly.

Mike Verhaagen
  • 11
  • 1
1

I got the same error and found out that my v4.0 website was hosted under the default website that was v2.0. If you've such setup then you need to remove the following line from your web.config:

<compilation defaultLanguage="c#" debug="true" targetFramework="4.0"/>

I hope that helps.

Vijay Bansal
  • 737
  • 7
  • 10