Re: Master Page Best Practice

Thanks. That what I was guessing.
How about handling the <script...></script> tag inside the <head>. The ~/
does not seem to work.


"Steve C. Orr [MVP, MCSD]" <Steve@xxxxxxx> wrote in message
news:uirz3pG2GHA.4648@xxxxxxxxxxxxxxxxxxxxxxx
I prefer the second option you mentioned for most situations.
<a href="~/somewhere.aspx"> runat="server">

It is optimal, giving as much functionality as is needed without any
additional overhead.
WebControls (such as Hyperlink) require more server resources than the
simple href, and the last option you mentioned is usually more of a
maintenance headache.

--
I hope this helps,
Steve C. Orr
MCSD, MVP, CSM
http://SteveOrr.net


"LaptopHeaven" <LaptopHeaven@xxxxxxxxxxxxxxx> wrote in message
news:%237IHllF2GHA.4388@xxxxxxxxxxxxxxxxxxxxxxx
When using Master Pages, what is the best Best Practice when it comes to
images and hyperlinks on the master page? Is it better to use WebControls
(<asp:Hyperlink/>), HtmlControls (<a href="~/somewhere.aspx"
runat="server">) or using ResolveClientUrl("~/somewhere") inline?







.

Relevant Pages

  • Re: Master Page Best Practice
    ... I prefer the second option you mentioned for most situations. ... additional overhead. ... WebControls (such as Hyperlink) require more server resources than the ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Master Page Best Practice
    ... discuss at adhdata dot com ... giving as much functionality as is needed without any ... WebControls (such as Hyperlink) require more server resources than the ...
    (microsoft.public.dotnet.framework.aspnet)
Loading