[VS.NET 2005] Nested Master Pages and Unrecognized tag prefix or device filter 'asp'

413 views
Skip to first unread message

Markus R.

unread,
Jan 18, 2006, 4:04:36 AM1/18/06
to
Hi,

I use nested master pages. On a content page I dropped some ASP.NET
controls. The page and the contols work but VS.NET reports an error for each
<asp:...> server control:

Error 1 Unrecognized tag prefix or device filter 'asp'. ´

This is how the content page looks like:

<%@ Page Language="C#" MasterPageFile="~/Contentpage.master"
AutoEventWireup="true" CodeFile="Pwd.aspx.cs" Inherits="Pwd" Title="Change
Password" %>
<asp:Content ID="Content5" ContentPlaceHolderID="_cpMiddleContent"
Runat="Server">
<asp:changepassword runat="server" ID="_cpChange"></asp:changepassword>
</asp:Content>

Contentpage.master has Main.master as Master Page.

I do not recieve this error if I use an ASP.NET control in
Contentpage.master.

What's wrong here?

Markus

Steven Cheng[MSFT]

unread,
Jan 19, 2006, 12:07:30 AM1/19/06
to
Hi Markus,

Welcome to MSDN newsgroup.
As for the design-time error in VS 2005 ide when developing asp.net 2.0
page with Nested master pages, I've just performed some tests through some
simple master pages and concrete aspx pages, however seems didn't get the
same error behavior... Maybe page content specific... Can you run the page
correctly at runtime through browser?

Also, when using master page, it'll raise some errors if the <asp:Content >
or any other server controls tag are put in the aspx template correctly...

regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)


--------------------
| From: "Markus R." <mar...@newsgroups.nospam>
| Subject: [VS.NET 2005] Nested Master Pages and Unrecognized tag prefix or
device filter 'asp'
| Date: Wed, 18 Jan 2006 10:04:36 +0100
| Lines: 29
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
| X-RFC2646: Format=Flowed; Original
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
| Message-ID: <#Q$F24AHG...@TK2MSFTNGP09.phx.gbl>
| Newsgroups: microsoft.public.vsnet.ide
| NNTP-Posting-Host: 80.152.25.19
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.vsnet.ide:17978
| X-Tomcat-NG: microsoft.public.vsnet.ide


|
| Hi,
|
| I use nested master pages. On a content page I dropped some ASP.NET
| controls. The page and the contols work but VS.NET reports an error for
each
| <asp:...> server control:
|

| Error 1 Unrecognized tag prefix or device filter 'asp'. ?

chrishawn

unread,
Jan 24, 2006, 4:26:45 PM1/24/06
to
I am encountering this same issues
seems to be specific to nested masterpages

the page with the content on it still builds fine
just get the red squiggly under the tag and autocomplete no longer
works on the tags.

-shawn

chrishawn

unread,
Jan 24, 2006, 4:45:38 PM1/24/06
to
I may have solved it

seems to have happened when i was using a nested master without a code
behind
and deleted the <script runat=server tag when i put it back in it
worked fine.

chrishawn

unread,
Jan 26, 2006, 10:47:35 AM1/26/06
to
actually it was the building of the master page that solved it
need to ocasionally rebuild the master page that is nested then it will
work.
like it needs to be in active memory for visual studio.

coworker says if you add an html and body tag on the child page it will
see them as well
but of course your html code is not correct.

chrishawn

unread,
Jan 26, 2006, 2:05:08 PM1/26/06
to
okay final statement on the topic..
building makes no difference.
what does make a difference is leaving the nested master page file open
in the IDE editor window.. it recognizes eveything just fine. if you
close that file and work on the child page you will get the asp message

rodjohnson

unread,
Jan 31, 2006, 1:55:43 PM1/31/06
to
I am using nested master pages as well. This problem just showed up, though and it is really annoying. I think that there must have been something that triggered this behavior.
---
Posted via www.DotNetSlackers.com
Reply all
Reply to author
Forward
0 new messages