There are two basic kinds of queues: public and private. A public queue is registered in Active Directory and as such can be discovered by browsing the network. A private queue is created on a machine and can only be accessed from another machine if you know the exact name of the machine and queue. Private queues are usually used if operating in Windows workgroup mode or if the queue is meant to connect two applications running on the same machine. In workgroup mode, private queues are the only option, but even in domain mode, consider the following advantages of using private queues: 

·         Private queues have all the features of public queues except that private queues are not listed in Active Directory and are not discoverable. If you know the queue is available, you can still connect remotely.

  ·         Private queues are faster to create than public queues because they require no extra time for Active Directory activity.

  ·         Private queues do not cause Active Directory replication problems.            

   Queue Type Description Syntax

There are three general value types:

•  Built-in types

•  User-defined types

•  Enumerations

Each of these types is derived from the System.Value base type.

Built-in Value Types

Built-in types are base types provided with the .NET Framework, with which othertypes are built. All built-in numeric types are value types. You choose a numeric typebased on the size of the values you expect to work with and the level of precision you require. 

Type forwarding works only for components referenced by existing applications. When you rebuild an application, there must be appropriate assembly references for any types used in the application.

To move a type from one class library to another, follow these steps:

• Add a TypeForwardedTo attribute to the source class library assembly.

• Cut the type definition from the source class library.

• Paste the type definition into the destination class library.

• Rebuild both libraries. The following code shows the attribute declaration used to move TypeA to the DestLibclass library:‘ VBImports System.Runtime.CompilerServices

  <Assembly:TypeForwardedTo(GetType(DestLib.TypeA))]>

  // C#

  using System.Runtime.CompilerServices;

  [assembly:TypeForwardedTo(typeof(DestLib.TypeA))] 

• They automatically create a data store. When you attempt to use membership features, ASP.NET 2.0 checks whether the specified data store is configured. If it is not, ASP.NET creates it.
• They include server controls for creating and validating users and displaying user- specific information and login status. New controls such as the Login, LoginStatus, CreateUserWizard, and ChangePassword controls provide pre-built user-interface building blocks, including functionality for the most common membership-related tasks. These controls are highlighted in the New Web Controls application.
• They provide an application programming interface (API) for programmatically manag- ing users. The Membership API is accessed via the Membership class and includes help- ful methods such as CreateUser, DeleteUser, and ValidateUser.

With ASP.NET 2.0 Membership, you can actually create a Web site with protected pages, automatic redirects to a login page, user creation (registration), and user login without writing any code.

 Benefits of Partial Classes
One of the greatest benefits of partial classes is that they allow a clean separation of business logic and the user interface (in particular, the code that is generated by the Visual Studio Designer). Using partial classes, the UI code can be hidden from the developer, who usually has no need to access it anyway. Partial classes also make debugging easier, as the code is partitioned into separate files. This feature also helps members of large development teams work on their pieces of a project in separate physical files.