This article provides step-by-step instructions to make and to register an assembly to be available in a WebForm to use with ASP.NET custom server controls.
Sample Assembly Properties
To represent as a Custom Server Control, the assembly must have a class that directly or indirectly derives from System.Web.UI.Control
and you must enclose the class in a namespace. The samples in this article are based on the assumption that the class is enclosed in the CustomControlNamespace
namespace, and that the assembly was successfully compiled into a file named CustomControl.dll.
Make an Assembly Available to ASP.NET Application
To make an assembly available for an ASP.NET application, you must place the assembly's .dll into the /bin folder of the application.
- Navigate to the root directory of the application in Windows Explorer.
To find out what the application project folder is:
- In the .NET environment, on the View menu, click Solution Explorer.
- Right-click a project main item in Solution Explorer, and then click Properties.
- In the Project Properties dialog box, click Common Properties, and then click General.
In the tree pane, you see the list with the Project Folder property. This is typically the root directory of the application.
- In a Web Application project folder, create a folder that is named "bin" if no such folder exists.
- Copy or move the assembly's .dll into this folder.
You can now use the control from any ASP.NET page in your application's root directory (or any of its subfolders).
Register the Assembly in an ASP.NET Application Web Form
In a .NET programming environment, open the Form .aspx source window, and then add the following tag to the top of the code
<%@ Register TagPrefix="Custom" Namespace="CustomControlNamespace" Assembly= "CustomControl" %>
- Custom is an alias that you associate with a namespace.
- CustomControlNamespace is a namespace in which classes of an assembly are enclosed.
- CustomControl is the name of the assembly file without an extension (.dll).
In your code, change these parameters to the appropriate names for your assembly.
Now the assembly is registered in a Web Form. You can use this registered assembly in your ASP.NET code with the chosen names. For example, the tag might be
<Custom:CustomControl id="CustomControl1" parameter1="value1" parameter2="value2" runat="server"/>
is the chosen name for the assembly's namespace, CustomControl
is the custom server control name, and parameter1
are optional control properties that may vary based on your actual code.
Article ID: 321749 - Last Review: June 17, 2003 - Revision: 3.4
- Microsoft .NET Framework 1.1
- Microsoft ASP.NET 1.0
- Microsoft Windows 2000
- Microsoft ASP.NET 1.1
- Microsoft .NET Framework Class Libraries 1.1
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Web Edition