Search

'asp' is an unrecognized tag prefix or device filter by Rosco1

Closed
as Fixed Help for as Fixed

18
Sign in to vote
0
Sign in to vote
Sign in
 to vote
Type: Bug
ID: 104946
Opened: 4/10/2005 5:43:52 PM
Access Restriction: Public
Duplicates: 102882 103323
2
Workaround(s)
10
User(s) can reproduce this bug
Created a website utilising Master Pages.

Initially I had the ability to add ASP.Net web controls within the <ASP:Content> tags with the assistance of intellisense. A few days into my project, and suddenly each web control tag is highlighting an error with the following message:

"'asp' is an unrecognized tag prefix or device filter"

The project compiles and runs normally, with each web control functioning as expected.
Details (expand)
Product Language
English
Version
Visual Studio 2005 Beta 1 Refresh
Category
Master Pages
Operating System
Windows 2000 Server
Operating System Language
US English
Steps to Reproduce
After these errors appeared for the first time, I created a brand new web site project.

I created all the webforms again, and the master page with the help of intellisense.
Actual Results
Two weeks into the project and suddenly the error is occurring again for all master pages.

"'asp' is an unrecognized tag prefix or device filter" for each ASP.Net control within the <ASP:Content> tags. Intellisense no longer working as ASP.Net controls cannot be added programmatically, but they can be added and administered via design view of the web forms.

Consequently, if I added a new web form to the project that does not use a master page, then I have the ability to add ASP.Net web controls on to this page programmatically.
Expected Results
Expected result is to have the ability to add ASP.Net web controls within the <ASP:Content> tags on a web form that uses a Master Page. The error reported by the compiler should not occur.
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 4/11/2005 at 11:58 AM
Thank you for your report. Can you provide explicit details on the content page and master page in your scenario? Ideally if you can attach repro files that would be great. Are you using a masterpagefile defined through configuration and therefore have no masterpagefile attribute in the page directive?

many thanks.
The Web Platform and Tools Team.
Posted by Rosco1 on 4/13/2005 at 3:56 PM
Master Page
------- ------
Created a master page that contains a TreeView, a SiteMapPath and an empty ContentPlaceHolder control.
The Master Page itself does not generate any tag error and it compiles correctly.

Content Pages
--------- -------
All content pages are web forms using C#. The ASP:Content control can be added without any problems. When attempting to add other controls within theese tags programmatically, they do not appear with intellisense. When added manually via the design view they appear as an error. The pages compile and work as expected. The errors dialog box does not appear.

Application pages and ReflectedSchemas folder has been attached.
Posted by Microsoft on 4/26/2005 at 4:08 PM
Even with the Web and the Schemas folder you sent, we didn't see anything unusual. We opened your site with the Beta 2 build, and didn't see anything - maybe two weeks from now we will. If you see this happen with the Beta 2 build as well, please let us know. If you remember anything about the types of actions you were doing just before you saw it fail, that might also be useful - especially the first time around, when it sounds like your project got into that state relatively early.

Thanks,
The Web Platforms and Tools Team.
Posted by Microsoft on 9/12/2005 at 11:42 PM
Thank you for submitting this issue. At this stage in the Whidbey product cycle, we're taking very few changes into the product. We have evaluated this issue and will not be able to investigate it before release but we’ll reconsider it for the next version of the product at a future date. To help us better evaluate this issue, we would appreciate if you would send email to webntppb@microsoft.com with the FDBK ID of this issue in the subject line so we can contact you later, if necessary. For more information, please refer to the announcement on the MSDN Product Feedback center at http://lab.msdn.com/productfeedback.

Rich Ersek
The Web Platform & Tools Team
Posted by Microsoft on 10/24/2005 at 6:14 PM
This issue has been reactivated as we begin planning for the next version of Visual Studio. Over the coming months we will reconsider feedback that was previously postponed. We welcome your comments and participation in this process.

-- Visual Studio Team
Posted by Microsoft on 1/12/2006 at 2:14 PM
It appears we were using a mechanism to find the master pages that required the files to already be opened in the editor. I've changed the code to no longer call through this code path, and finds the master page file using a different mechanism. Thanks for you input!

-- Todd Grunke
Posted by CelloJ on 10/3/2006 at 2:35 PM
This is happening because MasterPageFile="xyz.master" has been removed from the @Page and into web.config. This is clearly a bug in the IDE, which doens't seem to be able to fetch the <page ...> from the Web.Config.

<pages
     masterPageFile="~/MasterPages/XYZ.master"
     theme="XYZ" />
© 2010 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement