Unless you limit yourself to one-page web sites, you’ll need to design navigation. In fact, navigation is among the most important parts of any web design, and requires a great deal of thought if visitors are to move around your site easily.
Very few people will ever achieve their greatest life goals. How many people do you know who have achieved their dream?
In this article you will learn how to successfully setup your own ASP.NET 2.0 application to run as a virtual directory under the Community Server 2.1 website.
The Online Tool for Precision Vectorization
After many months of toiling in our secret underground laboratories, Dust-Me Selectors Version 2.0 is finally here!
If you’re one of the many people who made suggestions or commented on the original version, you’ll be pleased to know that the new version incorporates everything you asked for and more.
It was quite a challenge to bring all this together, particularly since Mozilla’s documentation is so … er … erratic (in fact for some functionality I had to look in Firefox’s source code just to figure out how it’s done!) But there’s nothing like a challenge to exercise the mind, and I think you’ll agree that the final result is well worth the gritty struggle.
- Create a new ASP.NET Web Application, Windows Forms Control Library or Class Library project
- Create a new class and inherit from System.Web.UI.WebControls.WebControl or from a specific control (like TextBox)
- Override the Render method and call writer.write() to write raw HTML to the page. ASP.Net server tags won’t work
- Use WriteBeginTag(), WriteEndTag(), RenderBeginTag(), RenderEndTag(), AddAttribute(), AddStyleAttribute() and WriteAttribute() to create HTML tags and attributes
- Add design-time attributes to properties, like:
[Description(“The text to be shown in the control”)]
- Define a tagprefix attribute:
[assembly: System.Web.UI.TagPrefix(“Anthoro.WebControls”, “awc”)]
- Add a toolbox icon:
- Create a 16×16 pixel bitmap (BMP 16 colors) with the same name as the control.
- Add it to the root of your project
- Set its Build Action to “Embedded Resource”
- Add additional resources (stylesheet, images, text files, …) and mark them as “Embedded Resource” also
- Add an Assembly attribute for each resource to your AssemblyInfo.cs:
[assembly: WebResource(“Anthoro.Controls.style.css”, “text/css”, PerformSubstitution = true)]
When the PerformSubstitution parameter is set to true, the resource will be processed and other webresource URL’s inside it will be parsed and replaced (works only for text-based resources:
background-image: url(‘<%= WebResource("Anthoro.Controls.back.png")%>‘);
- Pay attention to the full namespace and folder structure where your resources are stored. The resource name is build as: Namespace + Subfolders + filename
- At design-time, the control is displayed by running the rendering logic. To override this, use the GetDesignTimeHtml(), GetEmptyDesignTimeHtml() and GetErrorDesignTimeHtml() methods
Update: Unlike in C#, in VB.Net the subfolders are not taken into account with the namespace. So the example above in point 10 will be: Namespace + filename
Great understandable article about the 3 most important subjects in CSS: the cascade, inheritance and specificity!I recently held a workshop for my colleagues covering these as the primary subjects and more advanced CSS techniques. This article explains them in an understandable non-technical language.
Powered by ScribeFire.