Unrecognized Attribute 'xmlns' when working with VS.NET Express Edition
Symptoms
When using VS.NET Web Developer Express Edition, you may have a site that compiles fine in the development environment but fails when you copy it to the local IIS server.
Cause
ASP.NET 2.0 is not the default .NET version used by IIS. It works in the development environment because VS.NET compiles a virtual web server with the proper .NET version before code compilation begins.
Thinking it occurred because the virtual directory wasn't identified as an application, I created a site (called personal) that mapped to the directory I copied, but still failed.
As it turns out, 'xmlns' is a component in ASP.NET 2.0, and will generate that error when compiled on an IIS server running ASP.NET 1.1. This is delightfully easy to fix:
- Open Internet Information Services and navigate to "Default Web Site" (or the site you're using as your default).
- Right click the Site icon (the one with the globe).
- Select the ASP.NET tab. You'll see a drop-down with the available versions (if you're getting the error, odds are, you'll see 1.1).
- Select the proper build of ASP.NET 2.0.
- Restart IIS.
Your page should now work.
posted on Sunday, August 21, 2005 9:35 AM
# re: Unrecognized Attribute 'xmlns' when working with VS.NET Express Edition 11/4/2005 9:35 AM Paul Campbell
Legend!
Thanks man - very helpful
# re: Unrecognized Attribute 'xmlns' when working with VS.NET Express Edition 11/7/2005 8:36 AM Raj
(FORGOT TO ADD THIS: PLEASE EMAIL ME AT raj@rhealsoft.com or raj@xtremebiz.biz if you have a solution for this)
hi,
can you help me with this:
i have an asp.net 1.1 application folder inside an asp.net 2.0 application folder.
although i have set iis to run the 1.1 application folder under asp.net 1.1 dll, when i try to access my 1.1 application, i get the same xmlns runtime error.
this is happening because asp.net 1.1 first tries to read the web.config of the upper level folder which infact is 2.0 application's web.config file and so it cant recognize this. is there a work around for this
thanks in advance,
raj
# re: Unrecognized Attribute 'xmlns' when working with VS.NET Express Edition 11/7/2005 10:14 AM opsan
That is really interesting; can you run a 1.1 application inside a 2.0 folder? Is the 2.0 folder a virtual directory? If so, I -think- it'd be recognized as a 2.0 application.
That said, what is your need to have a nested 1.1 application? If you run the 1.1 application in it's own 1.1 folder, does it function alongside your 2.0 environment? I would expect IIS to support that.
# re: Unrecognized Attribute 'xmlns' when working with VS.NET Express Edition 11/10/2005 7:34 AM John Doe
Can't you just add a new web.config file in the ASP.NET 1.1 directory? It should use that file rather than the root web.config.
# re: Unrecognized Attribute 'xmlns' when working with VS.NET Express Edition 11/10/2005 8:09 AM opsan
Great suggestion; does that work? I seem to recall being able to assign custom .config files rather than the standard web.config, which might also allow.
I guess I don't quite understand the problem space; maybe Raj can enlighten us.
# re: Unrecognized Attribute 'xmlns' when working with VS.NET Express Edition 11/10/2005 8:16 AM adam
Thanks a bunch. You are a real life saver.
# re: Unrecognized Attribute 'xmlns' when working with VS.NET Express Edition 11/18/2005 6:20 AM Chris
Thank you very much, I was getting quite frustrated with this error!
# re: Unrecognized Attribute 'xmlns' when working with VS.NET Express Edition 11/26/2005 3:34 AM Jim Sneeringer
I have the same error message, but there is no ASP.NET tab. When I look under C:\WINDOWS\Microsoft.NET\Framework, there is no folder for .NET 2.0, but when I try to reinstall .NET 2.0, it tells me it is already installed. I went to Add/Remove programs to try to uninstall, but only 1.0 and 1.1 are there.
Anyone have any ideas?
# re: Unrecognized Attribute 'xmlns' when working with VS.NET Express Edition 11/26/2005 4:05 PM opsan
It does sound like .NET 2.0 is not installed; is it possible you installed a beta version at one time or another?
Are there any other post-.NET 2.0 programs installed? WinFX beta, perhaps?
# re: Unrecognized Attribute 'xmlns' when working with VS.NET Express Edition 11/30/2005 2:02 PM Matthew Parker
Thanx for the help, solved my problem
# Unrecognized Attribute 'xmlns' when working with VS.NET Express Edition 12/18/2005 12:48 AM Anil Kumar
Iam using XP O/S with
.NET Framework 1.1 Configuration
(version 1.1.4322.573
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'
# re: Unrecognized Attribute 'xmlns' when working with VS.NET Express Edition 12/18/2005 8:55 AM opsan
Anil, if this is request for assistance, this article covers your issue. Please step through it and advise if it doesn't resolve the problem.
# re: Unrecognized Attribute 'xmlns' when working with VS.NET Express Edition 12/19/2005 1:53 PM unfrustrated
# re: Unrecognized Attribute 'xmlns' when working with VS.NET Express Edition 3/8/2006 5:19 AM Taj
# re: Unrecognized Attribute 'xmlns' when working with VS.NET Express Edition 4/15/2006 8:23 AM Thiru
Amazing post....i searched for two days to fix this problem.....great...thanx...
# re: Unrecognized Attribute 'xmlns' when working with VS.NET Express Edition 5/11/2006 8:30 AM Daniel
Strange! When I follow the advise and change the ASP.NET version under the ASP.NET tab of the Default Web Site Properties from 1.1 to 2.0 this does not have any effect. Instead, after restarting IIS the ASP.NET version is switched back to 1.1
# re: Unrecognized Attribute 'xmlns' when working with VS.NET Express Edition 5/11/2006 8:48 AM Daniel
Found the reason!
When restarting IIS the ASP.NET version seems to be switched to 1.1 whenever there is at least one application that is set to 1.1
# re: Unrecognized Attribute 'xmlns' when working with VS.NET Express Edition 5/15/2006 8:39 AM Andrea
