Visual Web Developer 2005 Express

Re: 'asp' is an unrecognized tag prefix or device filter

marspd — Mon, 08 Jan 2007 16:47:15 GMT

I'm having this problem and I am not using master pages. I have a custom control with a Telerik RadGrid on it which compiles and works fine but the source editor intellisense does not work and the error 'Unrecognized tag prefix or device filter' is showing. I've cleared the RelectedCahce folder and this does not sort it. I did notice that for each element on the control there is a random named XSD file created. These files are all well formed except for the one for the grid I am haing problems with. The file is too large to post but it seems that the end of the file is missing, here is the last few lines of the file.

<xsd:simpleType name="System.Web.UI.WebControls.WebColorConverterDef">
<xsd:union>
  <xsd:simpleType>
   <xsd:restriction base="xsd:string">
    <xsd:enumeration value="ActiveBorder" />
    <xsd:enumeration value="ActiveCaption" />
    <xsd:enumeration value="ActiveCaptionText" />
    <xsd:enumeration value="AliceBlue" />
    <xsd:enumeration value="AntiqueWhite" />
    <xsd:enumeration value="AppWorkspace" />
    <xsd:enumeration value="Aqua" />
    <xsd:enumeration value="Aquamarine" />
    <xsd:enumeration value="Azure" />
    <xsd:enumeration value="Beige" />
    <xsd:enumeration value="Bisque" />
    <xsd:enumeration value="Black" />
    <xsd:enumeration value="BlanchedAlmond" />
    <xsd:enumeration value="Blue" />
    <xsd:enumeration value="BlueViolet" />
    <xsd:enumeration value="Brown" />
    <xsd:enumeration value="BurlyWood" />
    <xsd:enumeration value="ButtonFace" />
    <xsd:enumeration value="ButtonHighlight" />
    <xsd:enumeration value="ButtonShadow" />
    <xsd:enumeration value="CadetBlue" />
    <xsd:enumeration value="Chartreuse" />
    <xsd:enumeration value="Chocolate" />
    <xsd:enumeration value="Control" />
    <xsd:enumeration value="ControlDark" />
    <xsd:enumeration value="ControlDarkDark" />
    <xsd:enumeration value="ControlLight" />
    <xsd:enumeration value="ControlLightLight" />
    <xsd:enumeration value="ControlText" />
    <xsd:enumeration value="Coral" />
    <xsd:enumeration value="CornflowerBlue" />
    <xsd:enumeration value="Cornsilk" />
    <xsd:enumeration value="Crimson" />
    <xsd:enumeration value="Cyan" />
    <xsd:enumeration value="DarkBlue" />
    <xsd:enumeration value="DarkCyan" />
    <xsd:enumeration value="DarkGoldenrod" />
    <xsd:enumeration value="DarkGray" />
    <xsd:enumeration value="DarkGreen" />
    <xsd:enumeration value="DarkKhaki" />
    <xsd:enumeration value="DarkMagenta" />
    <xsd:enumeration value="DarkOliveGreen" />
    <xsd:enumeration value="DarkOrange" />
    <xsd:enumeration value="DarkOrchid" />
    <xsd:enumeration value="DarkRed" />
    <xsd:enumeration value="DarkSalmon" />
    <xsd:enumeration value="DarkSeaGreen" />
    <xsd:enumeration value="DarkSlateBlue" />
    <xsd:enumeration value="DarkSlateGray" />
    <xsd:enumeration value="DarkTurquoise" />
    <xsd:enumeration value="DarkViolet" />
    <xsd:enumeration value="DeepPink" />
    <xsd:enumeration value="DeepSkyBlue" />
    <xsd:enumeration value="Desktop" />
    <xsd:enumeration value="DimGray" />
    <xsd:enumeration value="DodgerBlue" />
    <xsd:enumeration value="Firebrick" />
    <xsd:enumeration value="FloralWhite" />
    <xsd:enumeration value="ForestGreen" />
    <xsd:enumeration value="Fuchsia" />
    <xsd:enumeration value="Gainsboro" />
    <xsd:enumeration value="GhostWhite" />
    <xsd:enumeration value="Gold" />
    <xsd:enumeration value="Goldenrod" />
    <xsd:enumeration value="GradientActiveCaption" />
    <xsd:enumeration value="GradientInactiveCaption" />
    <xsd:enumeration value="Gray" />
    <xsd:enumeration value="GrayText" />
    <xsd:enumeration value="Green" />
    <xsd:enumeration value="GreenYellow" />
    <xsd:enumeration value="Highlight" />
    <xsd:enumeration value="HighlightText" />
    <xsd:enumeration value="Honeydew" />
    <xsd:enumeration value="HotPink" />
    <xsd:enumeration value="HotTrack" />
    <xsd:enumeration value="InactiveBorder" />
    <xsd:enumeration value="InactiveCaption" />
    <xsd:enumeration value="InactiveCaptionText" />
    <xsd:enumeration value="IndianRed" />
    <xsd:enumeration value="Indigo" />
    <xsd:enumeration value="Info" />
    <xsd:enumeration value="InfoText" />
    <xsd:enumeration value="Ivory" />
    <xsd:enumeration value="Khaki" />
    <xsd:enumeration value="Lavender" />
    <xsd:enumeration value="LavenderBlush" />
    <xsd:enumeration value="LawnGreen" />
    <xsd:enumeration value="LemonChiffon" />
    <xsd:enumeration value="LightBlue" />
    <xsd:enumeration value="LightCoral" />
    <xsd:enumeration value="LightCyan" />
    <xsd:enumeration value="LightGoldenrodYellow" />
    <xsd:enumeration value="LightGray" />
    <xsd:enumeration value="LightGreen" />
    <xsd:enumeration value="LightPink" />
    <xsd:enumeration value="LightSalmon" />
    <xsd:enumeration value="LightSeaGreen" />
    <xsd:enumeration value="LightSkyBlue" />
    <xsd:enumeration value="LightSlateGray" />
    <xsd:enu

As you can see, it just stops for no apparent reason at <xsd:enu....

If anyone has any information/help/suggestions please let me know, I would greatly appreciate it.

Regards

Paul

Re: 'asp' is an unrecognized tag prefix or device filter

madkidd — Mon, 27 Nov 2006 02:51:23 GMT

Yeah, it works when I do that. :s

Re: 'asp' is an unrecognized tag prefix or device filter

Mikhail Arkhipov (MSFT) — Fri, 24 Nov 2006 23:35:39 GMT

Try keeping all masterpages in the chain open in the editor.

Re: 'asp' is an unrecognized tag prefix or device filter

madkidd — Fri, 24 Nov 2006 22:32:07 GMT

Hi Todd,

I'm having this same problem in Visual Studio 2005 Pro on Windows Vista RC1 (build 5600), but it is only occuring when I use nested master pages. If I create a new page based on my main master page all works fine, but if I then create a new page and tell it to use my masterpage that is using a masterpage, this issues comes up.

Is there anything I can do about it?

Re: 'asp' is an unrecognized tag prefix or device filter

Mikhail Arkhipov (MSFT) — Sat, 08 Apr 2006 06:49:08 GMT

Not all controls are supported inside head. If you want to change title, try using head runat="server" or programmatically set Page.Title property at page load.

Re: 'asp' is an unrecognized tag prefix or device filter

mpandur — Sat, 08 Apr 2006 00:25:50 GMT

Hi, I'm using a simple Webform without masterpage and get the same error.

However it just appears on an asp:literal which is placed inside the html-title-tag. If I place it within the body-tag the error disappears.

Markus

Re: 'asp' is an unrecognized tag prefix or device filter

steve_t — Wed, 08 Mar 2006 12:02:43 GMT

I've been having the same problem with pages which reference a master page, and I tried deleting the reflected schemas folder with no effect. However I have noticed that if you open the referenced master page aspx in the IDE it sorts the problem out - if you're using nested master pages you need to open all referenced master pages up to the root one. Hope this works for you too.

Re: 'asp' is an unrecognized tag prefix or device filter

jonrmorgan — Thu, 02 Mar 2006 15:09:51 GMT

This is definitely a continuing problem in the production release of VS2005.

I came across it as a result of converting my site to use nested master pages. Before that everything was fine during the Beta program and using the production version.

Now I have to keep my entire nest of master pages open to avoid getting the dratted "asp is an unrecognized etc." message.

Given that we can't use the designer anyway with nested masters I have this uneasy feeling of things closing in on my code - just hope it continues to compile. Either way I guess we have to live with this one until SP1.

Any suggestions for a realistic workaround much appreciated.

Jon

Re: 'asp' is an unrecognized tag prefix or device filter

Joink! — Thu, 09 Feb 2006 14:09:25 GMT

I was experiencing the same problem in the released version of VS2005 and keeping the master page open solved the problem for me...

Re: 'asp' is an unrecognized tag prefix or device filter

Mikhail Arkhipov (MSFT) — Tue, 13 Dec 2005 00:24:08 GMT

Try to keep master page open, it may eliminate the error.

Re: 'asp' is an unrecognized tag prefix or device filter

rosst — Mon, 12 Dec 2005 23:02:46 GMT

Hi Brian,

I haven't seen the problem resurface since I installed the Beta 2 Refresh of VS2005. I am using the full suite - rather than an express edition.

My only suggestion is to upgrade (if you haven't already). Another work around that we discovered here was to start with a brand new web project/solution and then add your existing aspx pages, classes etc., into this newly created project. Make sure that you regularly backup your source code. We use Visual Source Safe. That way, if the issue occurs again, you can try and rollback your code to determine the problem.

It's a real pain of a problem and it tooks me weeks to fix it. I hope you're able to resolve it.

Cheers,

Ross.

Re: 'asp' is an unrecognized tag prefix or device filter

beaudetious — Mon, 12 Dec 2005 19:21:45 GMT

Has there been any resolution to this problem for any of you? I'm getting it in my released version of VS2005 and it's driving me crazy. In fact, I can't even compile now.

This is happening in a ContentPage for a subnested MasterPage (which, by subnested, I mean the MasterPage itself is a ContentPage for another MasterPage). Anyhow, if I copy my code out and paste it into a blank webform between the <form> tags, no problems.

Thanks,

Brian

Re: 'asp' is an unrecognized tag prefix or device filter

DJGray — Tue, 13 Sep 2005 20:27:28 GMT

Greetings friends. Please forgive my astonishing ignorance here. I've been moving to .Net for only the past few days and my learning curve is almost straight up.

Getting the exact same error as is being discussed in this forum, but with a little different twist.

My "content file" is calling an include virtual. That is the file that is having the issue. Is it possible to place .Net code in a virtual include?

I've been hacking away with a number of different attempts, but at the moment the simple code looks like this. I'm sure there is a very simple solution, but at the moment it eludes me.

<script language="VB" runat="Server">

</script>

<form id="Form1" method="post" runat=server>

<asp:AccessDataSource id="IT_QA" runat="server" selectcommand="SELECT FirstName, LastName, Phone, eMail FROM Testers ORDER BY LastName" datafile="~/data/eBusinessSQA.mdb"></asp:AccessDataSource>

</form>

Re: 'asp' is an unrecognized tag prefix or device filter

javierz — Wed, 17 Aug 2005 22:27:19 GMT

Todd,

I've been experiencing this problem as well. I don't know what to do to fix it short of recreating my entire web, but that's not really going to be a good solution. None of the other solutions posted here in this thread have helped at all.

blah blah blah... anyways...

I was able to create a fresh new web and reproduce the problem. I'd be glad to e-mail the web files to you or post them somewhere if you think it would help. (Grand total of 5k zipped.) If not, I suppose I could try to retrace the steps involved in reproducing the problem.

FYI...
Running VS2005 beta 2 July CTP (Professional ed.) on Windows XP w/sp2.

Re: 'asp' is an unrecognized tag prefix or device filter

EdwardC — Fri, 05 Aug 2005 08:08:05 GMT

EdwardC wrote:
Hi all,

I am having the same old problem with Beta 2 now. I did not install via the normal web setup. Rather, I install those Framework 2, VWD Express 2005 Beta 2 and etc by running individual setup.

I can't find the mentioned folder in .NET Beta 2: C:\Documents and Settings\[Username]\Application
Data\Microsoft\VisualStudio\8.0\ReflectedSchemas

regards.

Follow up on this:
The Beta 2 'system' seems able to recover itself. Just run Control Panel > Add/Remove Program.
I have checked and verified that ReflectedSchemas is not there before. After I decided to repair the installation, I fire up Add/Remove Program. Just like that. I did not do anything further. I did not run any repair.
The \Application Data\Microsoft\VWDExpress\8.0\ReflectedSchemas appears!
Check the folder date, it is created on current date and time. Now, everything doing fine.
Believe or not....believe it!