• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 221
  • Last Modified:

.NET version conflict?

Hello there,

I have a website developed in ASP .NET 2 running off the root of the default website (IIS 6).  I am trying to run an ASP .NET 1.4 inside the same website but when I run it, I get the error:
"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 'xmlns'.

Source Error:

Line 8:      \Windows\Microsoft.Net\Framework\v2.x\Config
Line 9:  -->
Line 10: <configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
Line 11:       <appSettings/>
Line 12:  

Source File: c:\inetpub\wwwroot\web.config    Line: 10"

This is the web.config file that resides on the root of the default website and belongs to the default website.  Why my application reads this file instead of its own.  The app resides in a folder off of the default website root.

I'd like to know if having the 1.4 app inside a  2.0 website will not work in IIS 6 will not work.

Thanks so much!


  • 3
1 Solution
There is no ASP.NET 1.4

There is 1.1 and 2.0

Regardless, you CANNOT run them on the same application pool.  You need separate application pools to run different versions of .NET
You should be able to run both.  Trying changing the ASP.NET version to the older version.  In the Web application properties window you'll see an ASP.NET tab, and if you have multiple versions of the runtime installed you can choose which version to use for which Web application.
This may help too.

ASP.NET 2.0 Web Root ASP.NET 1.1 virtuals and Web.Config Conflicts
I am fine with the split, but think my first comment is more releavant than the second one which is only a link.

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now