CodeSnip: One Application, Several Languages   12 Dec 2005 00:00 GMT
In this code snippet, Bilal Haidar will demonstrate how we can have an ASP.NET 2.0, VB.NET Web application with its own C# and VB.NET classes placed in the App_Code directory.
Source: AspAlliance

Microsoft ASP.NET 2.0 Member/Role Management with IIS, Part 2: Implementation   09 Dec 2005 04:25 GMT
This is the second article in a two part series on creating an application to maintain the membership databases for ASP.NET 2.0. In this article, Peter Kellner outlines the implementation of the solution.
Source: MSDN

Microsoft ASP.NET 2.0 Member/Role Management with IIS, Part 1: Security and Configuration Overview   09 Dec 2005 04:22 GMT
This is the first of two articles where Peter Kellner looks at creating an application to manage ASP.NET 2.0 membership databases. This article looks at securing the solution to ensure only proper administrators can access this data.
Source: MSDN

CodeSnip: Resolving Domain Names and IP Addresses   09 Dec 2005 00:00 GMT
Using the Dns class in System.Net namespace in .NET, we can easily resolve domain names and IP addresses. In this CodeSnip, Rajesh gives us a sweet, simple sample showing how to do this.
Source: AspAlliance

Manage Custom Security Credentials the Smart (Client) Way   07 Dec 2005 03:03 GMT
By default, you can only manage the security credentials of the SQL Server database that ships with ASP.NET 2.0 using a local instance of Visual Studio 2005. This article shows how to extend the management capabilities by wrapping the ASP.NET 2.0 providers with a Web service and using a Windows Forms application to manage the credentials store.
Source: DevX

Examining ASP.NET 2.0's Membership, Roles, and Profile - Part 1   07 Dec 2005 00:00 GMT

There's one thing messageboard websites, eCommerce websites, social network websites, and portal websites share in common: they all provide user accounts. These websites, and many others, allow (or require) visitors to create an account in order to utilize certain functionality. For example, a messageboard website, like ASPMessageboard.com, allows anonymous and authenticated visitors to view and search the posts in the various forums. However, in order to be able to post a new thread or reply to a message a visitor must have an account and must log into the site.

Providing user account support for a site involves the same set of steps: creating a database table to store user account information, creating a login page, defining a system by which authenticated users' logged on status is remembered across postbacks, specifying which pages are only available for authenticated users (authorization), creating a page for visitors to create a new user account, creating a page for the site's administrators to manage the user accounts, and so forth. Prior to ASP.NET, developers had to decide how to implement all of these facets on their own. ASP.NET introduced the concept of forms-based authentication, which provided a FormsAuthentication class to ease signing in and out of a site, as well as a protected authentication ticket to remember users' logged on status across page requests. (See Simple Authentication for an article on implementing authentication with classic ASP; refer to Using Forms Authentication in ASP.NET and Dissecting Forms Authentication for more information on ASP.NET's forms-based authentication capabilities.)

Even with forms-based authentication, though, ASP.NET developers are still on the hook for defining and creating the structure for storing user account information, for creating login and logout web pages, for enabling visitors to create new accounts and administrators to manage accounts, and so on. Thankfully ASP.NET version 2.0 has lightened developers' loads by providing the membership system and the security Web controls in ASP.NET 2.0. In a nutshell, membership is an API that provides programmatic access to common user account-related tasks. For example, there are methods to create a new user account, authenticate a user's credentials, delete a user, return all user information in the site, and so on. Furthermore, there are a number of security Web controls built atop this API that make performing common user account tasks as simple as dragging and dropping a control on the page.

In this article series we will be examining the ins and outs of version 2.0's membership, roles, and pofile systems and the various security Web controls. This particular article will examine the basics of membership with a look at configuring and using the built-in SqlMembershipProvider. As we will see, this particular provider stores user account information in a pre-defined database schema. Read on to learn more!
Read More >

Source: 4GuysFromRolla

64-Bit Programming Home Page   05 Dec 2005 18:17 GMT
The current version of 64-bit Windows supports the Intel Itanium Processor Family (IPF) and is built for the highest levels of scalability, with support for up to 64 processors and 16-terabyte (TB) of memory (architectural limit). This page contains links
Source: MSDN

An Extended Look at the Profile Object - Part 3   05 Dec 2005 00:00 GMT
This article is the third in the series of articles on the new personalization feature of ASP.NET 2.0, the Profile object. In this article, we are going to discuss the Profile provider-model, which is a new concept implemented by most of the new features in ASP.NET 2.0. In addition, the default SQL Profile provider that is configured with SQL Server 2005 will be studied in depth and a trick on how to use the same provider with SQL Server 2000 will be presented.
Source: AspAlliance

A Big Thanks to Miguel Castro   02 Dec 2005 15:47 GMT
Web Controls Presentation at Richmond's .NET User Group
Source: O'Reilly

MSDN TV: Late Binding in Visual Basic   02 Dec 2005 06:45 GMT
Paul Vick and Erik Meijer discuss how late binding in Visual Basic allows more dynamic programming than is possible in some other .NET languages. They also show future ideas for how late binding may make programming against data like XML radically easier.
Source: MSDN