Beginning ASP.NET 4.5 in CSharp and VB Opsylum

Introduction to User Controls x 293
Normally, when you put an element inside an element to link it, the browser draws a border
around the image. The border is usually blue for unvisited links and purple for links you have visited
before, though you could have some CSS code targeting a elements that overrides these default colors.
To remove that border completely, you need to add the following CSS:
img
{
border: none;
}
When you add a user control to a page, VS usually refers to the control using a relative path. In this
exercise, this path first contained two dots (..) to indicate the parent folder, followed by the Controls
folder, and finally by the name of the control:
By changing the two dots to the tilde symbol, it becomes easier to move your pages around in your site
because the Src attribute now always points to the Controls folder at the application’s root, no matter
where the page that consumes the control is located. If your Src attribute already contained the tilde,
you don’t have to change anything.
Though the tilde syntax makes your pages with user controls a little easier to manage, there is an
even easier way to register your user controls sitewide.
Sitewide Registration of User Controls
If you have a control that you expect to use quite often on separate content pages in your site, like
the banner in the previous examples, you can register the control globally in the Web.config file.
This way it becomes available throughout the entire site, without the need to register it on every
page. The following exercise shows how to do this.
TRY IT OUT
Registering User Controls in the Web.config File
In this exercise, you register the Banner.ascx user control in the Web.config file. You can then
remove the @ Register directive from the master page because it isn’t needed anymore. After you
have changed the Web.config file, adding the same user control to other pages will no longer add the @
Register directive to the page.
1. Open the Web.config file from the root of the site. If you’re familiar with versions of ASP.NET
prior to .NET 4, you may find the Web.config worryingly empty. But don’t worry; the functionality
it included has not been removed from .NET. The configuration information placed in the website’s
Web.config file has now been moved to the central Web.config and Machine.config files
that apply to the entire machine instead. This gives you a much cleaner configuration file, making it
easy to focus on your own stuff that you put in there.
2. Locate the element that you used in Chapter 6 to apply the theme, and within its tags
add the following bolded code that contains a element with a child element.