I encountered a bug in .Net 2.0 for which I can't find any reference on the web. I have a toplevel masterpage container looking like the one below. It's a simplified version to isolate te problem. The <%=Resources.Search.SearchText %> is actually included in (client side) html control. (it has to be clientside).

Toplevel Masterpage Sniplet:
<asp:ContentPlaceHolder ID="PageHeadingDefaultPlaceholder" runat="server">
                    <asp:HyperLink ID="contact" runat="server" TabIndex="7" NavigateUrl="~/contact.aspx"
                        Text="<%$ Resources: WireFrame, Contact %>" ToolTip="<%$ Resources: WireFrame, ContactToolTip %>" />
                     <%=Resources.Search.SearchText %>
</asp:ContentPlaceHolder>

Above code works. Why shouldn't it? When I create a Nested masterpage inheriting from my toplevel master and create an .aspx based on this nested masterpage, the code works. However: when I want to overwrite the placeholder in my nested masterpage, for example like so:

Nested Masterpage Sniplet:
<asp:Content ID="Content4" runat="server" ContentPlaceHolderID="PageHeadingDefaultPlaceholder" />

Hi,

If you  delete the HyperLink that is in the ContentPlaceHolder  on the top-level master page, make the ContentPlaceHolder is empty, do you still have the problem?

Hi Amada, thanx for the reply

When removing the hyperlink from the masterpage the error does not occur. When removing the <%=Resources.Search.SearchText %> statement and leaving the hyperlink in place, the error does not occur. Leaving them both in place triggers the problem.

The hyperlink itself is not the cause: this code triggers the problem as well, but only when i use the placeholder in the nested master page as described above.

 <%=Resources.Search.SearchText %>
 <asp:Literal runat="server" Text="<%$ Resources: WireFrame, SiteMapToolTip%>" />  

 Rinze

Hi Rinze,

I guess  your peobelm is related to the code Resources.Search.SearchText , how about you put Resources.Search.SearchText  in the codebehind to debug it? Do you still have the problem?

You can try to do like in the codebehind:

string strSearch;

strSearch =  Resources.Search.SearchText;

I'm sorry, it's been a while.

The problem is not the use of the resource. The resource is available and removing either statement causes the other to display correctly. I'm quite convinced this is a bug.
Maybe the bug is only on the declarative side of things, but setting the value programmatically using a codebehind (or code beside) just isn't an option.

Kind regards,

rinze