Master Pages Control ID Naming in Content Pages Introduction

Master Pages  Control ID Naming in Content Pages IntroductionAll ASP.NET server controls include an ID property that uniquely identifies the control and is the means by which the control is programmatically accessed in the code-behind class. Similarly, the elements in an HTML document may include an id attribute that uniquely identifies the element; these id values are often used in client-side script to programmatically reference a particular HTML element. Given this, you may assume that when an ASP.NET server control is rendered into HTML, its ID value is used as the id value of the rendered HTML element. This is not necessarily the case because in certain circumstances a single control with a single ID value may appear multiple times in the rendered markup. Consider a GridView control that includes a TemplateField with a Label Web control with an ID value of ProductName. When the GridView is bound to its data source at runtime, this Label is repeated once for every GridView row. Each rendered Label needs a unique id value.
Read more

Working with Data in ASP.NET 2.0 Handling BLL and DAL Level Exceptions in an ASP.NET Page

Working with Data in ASP.NET 2.0  Handling BLL and DAL Level Exceptions in an ASP.NET PageWorking with data from an ASP.NET web application using a tiered application architecture involves the following three general steps:
1. Determine what method of the Business Logic Layer needs to be invoked and what parameter values to pass it. The parameter values can be hard coded, programmatically assigned, or inputs entered by the user.
2. Invoke the method.
3. Process the results. When calling a BLL method that returns data, this may involve binding the data to a data Web control. For BLL methods that modify data, this may include performing some action based on a return value or gracefully handling any exception that arose in Step 2.
Read more

Working with Data in ASP.NET 2.0 Nested Data Web Controls

Working with Data in ASP.NET 2.0  Nested Data Web ControlsIn addition to static HTML and databinding syntax, templates can also include Web controls and User Controls. These Web controls can have their properties assigned via declarative, databinding syntax, or can be accessed programmatically in the appropriate serverside event handlers.
Read more

Understanding ASP.NET Validation Controls

Understanding ASP.NET Validation ControlsAfter you create a web form, you should make sure that mandatory fields of the form elements such as login name and password are not left blank; data inserted is correct and is within the specified range. Validation is the method of scrutinizing that the user has entered the correct values in input fields. In HTML you can perform validation either by checking the values at client-side or after submitting the form at the server-side. But these methods in HTML take lots of time to create and maintain the code. Moreover, if the user has disabled JavaScript then he or she may not receive the message regarding the error.
Read more

Adding the ASP.NET 2.0 radMenu Control to MOSS 2007 Publishing Sites

Adding the ASP.NET 2.0 radMenu Control to MOSS 2007 Publishing SitesWith the release of Windows SharePoint Services (WSS) v3 and Microsoft Office SharePoint Server (MOSS) 2007, Microsoft has implemented significant architectural changes to the SharePoint platform which simplifies the task of customizing the user interface. Most of these improvements are because WSS v3, unlike its predecessor, is built on top of the .NET 3.0 Framework bringing the native capabilities of ASP.NET 2.0 directly to the SharePoint platform. One such ASP.NET 2.0 concept that is leveraged by WSS v3 is the navigation provider model. The navigation provider model separates the navigation hierarchy (the data portion, otherwise known as site-map data sources) from the rendering (the presentation portion, otherwise known as navigation controls). The role of the site-map data source is to abstract the navigation hierarchy from the underlying system (such as SharePoint) to make it transparent to the navigation control. This allows developers to easily snap ASP.NET 2.0 navigation provider model compatible controls into a SharePoint site by simply configuring them to receive the navigation hierarchy from the provided SharePoint site-map data sources.
Read more

Next Page →