Re: Master Page Best Practice

From: "Steve C. Orr [MVP, MCSD]" <Steve@xxxxxxx>
Date: Thu, 14 Sep 2006 18:58:38 -0700

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?

Follow-Ups:
- Re: Master Page Best Practice
  - From: AG
- Re: Master Page Best Practice
  - From: LaptopHeaven

References:
- Master Page Best Practice
  - From: LaptopHeaven

Prev by Date: Re: What is the best practice to have a user control placed multiple times on a page?
Next by Date: Re: Embbed .NET Custom Control (ActiveX) into ASP .NET page
Previous by thread: Master Page Best Practice
Next by thread: Re: Master Page Best Practice
Index(es):
- Date
- Thread

Relevant Pages

Re: Master Page Best Practice
... 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)