vb.net code 39 generator source code Grouping Properties in VS .NET

Encoding Code 128 Code Set B in VS .NET Grouping Properties

Like <property>, the <profile> section can also accept the <group> element. The <group> element allows you to group a few related properties as if they are properties of an intermediate object. The following code snippet shows an example of grouping:

<profile> <properties> <group name="Font"> <add name="Name type="string defaultValue="verdana /> <add name="SizeInPoints type="int defaultValue="8 /> </group> </properties> </profile>

The font properties have been declared children of the Font group. This means that from now on, any access to Name or SizeInPoints passes through the Font name, as shown here:

MyCtl.Style["font-name"] = Profile.Font.Name; MyCtl.Style["font-size"] = String.Format( {0}pt", Profile.Font.SizeInPoints);

Note Default values are not saved to the persistence layer. Properties declared with a default value make their debut in the storage medium only when the application assigns them a value different from the default one.

In ASP.NET 2.0, the personalization API is composed of two distinct elements the access layer and the storage layer. The access layer provides a strongly typed model to get and set property values and also manages user identities. As you ll see in the next section, personalization data is associated with identities even though anonymous users can still connect and exploit the feature. The access layer guarantees that the data is retrieved and stored on behalf of the currently logged on user.

In general, an ASP.NET 2.0 provider is defined as a pluggable component that extends or replaces system functionality. The personalization provider is just one implementation of the new ASP.NET 2.0 provider model. Other examples of providers are the membership provider and role manager provider, both of which we ll discuss in 10. At its core, the provider infrastructure allows customers to extend some of the out-of-the-box system functionality and change the underlying implementation while keeping the top-level interface intact. Providers are relatively simple components with as few methods and properties as possible. Only one instance of the provider should exist per application domain.

The second element of the personalization system is the underlying data storage. The system uses ad hoc providers to perform any tasks involved with the storage and retrieval of values. ASP.NET 2.0 comes with two personalization providers, each of which uses a different data engine. The default provider uses an Access database; the other provider is for SQL Server. You can also write custom providers. The provider writes data into the database of choice and is responsible for the final schema of the data. A personalization provider must be able to either serialize the type (by using XML serialization and binary object serialization, for example) or know how to extract significant information from it.

All features, such as personalization, that have providers should have a default provider. Normally, the default provider is indicated via a defaultProvider attribute in the section of the configuration file that describes the specific feature. By default, if a preferred provider is not specified, the first item in the collection is considered the default. As for ASP.NET 2.0 personalization, the default provider is based on an Access database and is named AspNetAccessProvider. If you don t mind having your personalization data saved on a per-user basis in an Access database, you don t have to do anything. Otherwise, you can select an alternative provider. ASP.NET 2.0 provides a SQL Server based provider named AspNetSqlProvider. Providers are registered in the <providers> section of the configuration file under the main node <profile>, as shown here:

<profile enabled="true defaultProvider="AspNetAccessProvider > <providers> <add name="AspNetAccessProvider" type="System.Web.Profile.AccessProfileProvider" connectionStringName="AccessFileName" description="Stores and retrieves personalization data from the local Microsoft Access database file /> <add name="AspNetSqlProvider" type="System.Web.Profile.SqlProfileProvider" connectionStringName="LocalSqlServer" description="Stores and retrieves personalization data from the local Microsoft SQL Server database /> </providers> </profile>

The <add> nodes within the <providers> section list all the currently registered providers. The previous code is an excerpt from the machine.config file. Attributes such as name and type are common to all types of providers. Other properties are part of the provider s specific configuration mechanism. Tightly