Examining ASP.NET 2.0's Membership, Roles, and Profile - Part 9   05 Sep 2007 00:00 GMT

ASP.NET 2.0's Membership, Roles, and Profile systems were designed using the provider model, which enables these systems to seamlessly use different implementations. ASP.NET ships with a provider for managing members and roles through SQL Server and another for using Active Directory. It is also possible to plug in other implementations that have been built from the ground up or downloaded from other sources. For example, you can download alternative providers from Microsoft that store membership and role information in a Microsoft Access database (see Part 8 of this article series). Most of the articles in this series, however, have focused on using the SQL Server provider (SqlMembershipProvider, SqlRoleProvider, and SqlProfileProvider). The SQL Server providers are typically the provider of choice for Internet-based web applications, whereas the Active Directory providers are more commonly used in intranet scenarios.

The SQL Server providers create a number of tables, views, and stored procedures in the specified SQL Server database. Therefore when using these providers it is possible to add, modify, or delete membership or roles or profile-related data through T-SQL statements. In this article we'll look at a common membership need - deleting users. While users can certainly be deleted through the .NET Membership API, there are scenarios where it may be much easier to use a T-SQL script. However, bypassing the managed APIs and working directly with the database is not without its own host of challenges. By the end of this article we'll have addressed these issues, discussed the pros and cons of using T-SQL in lieu of the managed APIs, and have examined both the managed API methods and T-SQL commands for deleting a single user and deleting all users. Read on to learn more!
Read More >

Source: 4GuysFromRolla

Creating an ASP.NET 2.0 Polling User Control: Creating Administration Web Pages   05 Sep 2007 00:00 GMT

The polling User Control examined in the first two installments (Design Decisions and the Data Model and Building the Polling User Control) is functionally complete at this point. A page developer can add, edit, or delete new polls and poll answers by manually inserting, updating, or deleting records into or from the corresponding database tables; they can view a poll's results by running a query against the UserResponses table.

Having to work directly with the database in terms of SELECT, INSERT, UPDATE, and DELETE queries can be a pain, of course, especially for commonly performed techniques. A more palatable option is to provide a web-based interface for these common tasks. The download available at the end of each installment of this article series includes, in addition to the polling User Control, a set of administration web pages that make it easy to create, edit, and delete polls and poll questions and to view the results of any poll in the system.

In this third and final installment we'll examine these three administration pages' functionality, declarative markup, and code. Read on to learn more!
Read More >

Source: 4GuysFromRolla

Changing Assembly Versions During Runtime Using the Web.Config File   04 Sep 2007 22:50 GMT
You can change the assembly version quickly by including the bindingRedirect element in the web.config file.
Source: DevX

How Do I: Deploy a Visual Studio Package?   04 Sep 2007 10:21 GMT
In this video, Hilton Giesenow discusses the key concepts of deploying a VSPackage and shows the final output of a deployed package. Then, he demonstrates how to use a Setup and Deployment project to perform these steps in an installer, with tips on testing this process.
Source: MSDN