Will you ever need to pass relative paths to your control? Does your control function as a container for markup? If so, you should subclass Control instead of using a .ascx file.
The ability to reference style sheets and scripts from within content pages is greatly needed, but link and meta tags only work in the root master page. Here’s how to add full link, meta, and script parsing to your entire application.
Installation and configuration instructions for the Image Resizer
Server-side image resizing is one of those tiny features that can have incredible ROI. It can save webmasters several hours each day, and gives you the ability to change the resolution of an image without having to hunt up the original.
ASP.NET is primarily concerned with “virtual paths”, the portion of the path following the hostname or port number. When working with ASP.NET, you must understand the following types of URIs thoroughly, and know how they are handled by ASP.NET and the browser.
Virtual path providers are awesome – you can serve a site from a .zip file, perform XSLT transformations to generate .aspx files as the compiler reads them, and do all sorts of unusual things. However, using them can make the StaticFileHandler buffer entire downloads in memory before sending the data to the client.
The query string is handled differently from the rest of the virtual path. It is neither URL decoded or case-normalized before it reaches ASP.NET, although each name-value pair is URL decoded before being stored in the Request.QueryString collection.
ASP.NET introduces a new URI component to the equation: PathInfo. It’s not very well known, possibly due to poor implementation and consequent lack of usefulness. However, it is important that you understand how it can affect you.