ansaurus

Question

Why does the asp.net head control mangle link elements?

Answer 1

A:

Well what you're doing is (no offence) a bit silly, that is - having a <head> server-side element, with a nested <link> client-side element with server-side href attribute

You are dynamically rendering the href value from server code anyway, so a better solution would be to dynamically render the link tag from the server altogether.

Example (code-behind of page)

// Define an HtmlLink control.
HtmlLink myHtmlLink = new HtmlLink();
myHtmlLink.Href = "/css/page.css";
myHtmlLink.Attributes.Add("rel", "stylesheet");
myHtmlLink.Attributes.Add("type", "text/css");

// Add the HtmlLink to the Head section of the page.
Page.Header.Controls.Add(myHtmlLink);

Your ASPX then becomes much neater:

<head runat="server">
    <title>My Snazzy Page</title>
    <!-- CSS/JS included dynamically -->
</head>

RPM1984 2010-08-11 02:51:18

I agree it's odd and there is more than one reasonable alternative. I'm wondering if there's some underlying principle at play with interpolation of markup in built-in controls like head.

Thomas H 2010-08-11 15:03:58

So im getting the impression you're not so much looking for a solution, but an explanation.

RPM1984 2010-08-11 22:23:15

ansaurus

tags:

views:

answers:

Why does the asp.net head control mangle link elements?

related questions