Hi There,

I have been using Visual Web Developer Express Edition Beta 1 Refresh and Visual Studio 2005 Beta 1 for the past few weeks. For some unforeseen reason VS now reports the error -'asp' is an unrecognized tag prefix or device filter on all my .aspx pages.

The solution compiles and launches without any mishap and the only way to alter page control properties is in design view, as intellisense does not function due to the errors.

I've search the web and found a resolution which was to remove all files in the folder:

C:\Documents and Settings\[Username]\Application
Data\Microsoft\VisualStudio\8.0\ReflectedSchemas

But the issue still exists.

Any assistance would be greatly appreciated.

Ross.

 

Ross,

Does this occur in all of your web sites and pages, or only some specific ones? Does this happen as soon as you create a new web site and add a new page, or is this hapenning for any specific type of content - user controls, data controls, etc.? If this happens in fairly simply pages - could you give me an example of one?

Thanks,

Alex

It's only occurring in pages that inherit from a Master Page. All asp.net web controls within the asp:content place holder have this error. The only control that doesn't cause an error in the asp:content place holder.

If I create a new website, define a master page and reference the master page from a normal web form, the error does not show up. It only occurs after a certain period of time. Not sure why this happens.

 

Ross,

Thanks - that's great info. Unfortunately, I haven't been able to reproduce the problem so far, so I need to ask you a few more things:

1. Are you still using Beta1 code or is Beta2 CTP? (You can do Help->About to get the version number, that would be very helpful)
2. Which language are you using? (VB, C#, J#?)
3. Are you using code separation/code beside files, or are you using single file format (all of the code is in the markup in the <script> blocks, no code besde)
4. Is this happening with file system webs (using the Web Developer Web Server), or is it happening when working with IIS webs, or remote webs (Front Page or FTP)?
5. Did you by any chance notice what action tends to cause those errors to appear (e.g., adding a specific control, or adding more files, building, debugging, etc.)

Thanks,

Alex

Hi Alex,

1. I am using Beta 1.

2. C#

3. Exclusively using code behind files.

4. I'm using the in-built Visual Web Developer Web Server.

5. This is the hard question to answer. I believe it occurs after building and only for web forms that use master pages. If I create a web form that does not use a master page, then the issue does not apply.

If you check out this link, it does provide a solution, but it does not work for me. http://www.dotnetmonster.com/Uwe/Forum.aspx/asp-net/29983/asp-is-an-unrecognized-tag-prefix-or-device-filter

This guy (http://muellerdesigns.net/DasBlog/default.aspx?date=2005-03-09) also seems to have come across the problem.

 

Hi Ross,

  If I understand correctly, this situation always occurs for you within content pages, and isn't resolved by opening/closing the editor, or by deleting the ReflectedSchemas directory.

  First, let's have you close down any instances of VWD, and again delete the ReflectedSchemas directory. Next, crank up VWD and open only the file that experiences the issue. Verify the issue still occurs, and close VWD. Next, crack open the schemas.xml file within the ReflectedSchemas directory. This is the file that we use to cache all the reflection that we've done to create the schemas that the markup intellisense engine uses for intellisense. In the scenario you've just executed, we should have created two schemas (more if you reference user/custom controls within the opened page). One is for standard web forms, and the other is for content pages. Search for "__DESIGNER_ASP_CONTENT" within this file, then open the file referenced to by the SchemaPath attribute on the same line.

  This should be the file that we use for intellisense within content pages. If you open this file, you should notice one top-level element with type="System.Web.UI.WebControls.ContentDef". If you look at the definition of the type, you should see that it contains an <xsd:group ref="System.Web.UI.ControlExtendedElementsGroupDef" />. This group's definition should contain a whole bunch of valid top-level asp controls.

  Can you let us know how this checks out? If everything looks good at this point, I think I would need to see your content page to investigate further. Thanks for your input, we really do appreciate it.

-- Todd

Thanks Todd,

I followed your steps and when I open the file that experiences the issue in VWD, the errors disappear. But if I open the entire site, the errors remain.

I can confirm that the schema files are as set out in your message.

Ross.

Ross,

  At this point, I need to see the website you are working on to make a diagnosis. My gut feeling at this point is that there is some error in the web that is causing schema generation issues. Errors in the web certainly shouldn't be able to mess up intellisense for content pages. Files of interest are the opened content page and it's master(s), the web.config, code directory files, and bin directory assemblies. Thanks.

-- Todd

Hey I was having this problem for a long time and was ignoring it.  I think I fixed it will working on another problem as seen in my post here:

http://forums.aspfree.com/showthread.php?t=22489

The gist is to remove attribute urlLinePragmas="true" from your configuration tag if it's there.  It made all my tags show up normally anyway.

Hope that helps

hey, I have the same problem. I just started helping this company and they coded everything without VS studio. Code is a mess, architecture is to throw up but I have same problem with their pages. Also no events show up for asp controls They mixed some classic asp and what not but here is the page code. I also do not see any of the events for the control.

<%@ Page Language="C#" %>

<!--#INCLUDE virtual="/includes/WCC_ASPX.aspx"-->

<!--#INCLUDE virtual="/includes/standard_report.aspx"-->

<%@ Import Namespace=System %>

<%@ Import Namespace=System.Web %>

<%@ Import Namespace=System.Web.UI %>

<%@ Import Namespace=System.Web.UI.WebControls %>

<%@ Import Namespace=System.Data.SqlClient %>

<%@ Import Namespace=System.Data %>

<script runat="server" type="text/C#">

bla bla

</script>

<form method="post" runat=server>

   <asp:DropDownList  Id="ddlCaller" runat="server"/>

/form>

Can you try adding an <html> and <body> tags around the form, and see if this helps?

yep, that worked. Thanks

This problem seems to have disappeared with Beta 2.

Thanks to everyone for your help.

Ross.

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.

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!