Examining ASP.NET's Membership, Roles, and Profile - Part 15 01 Jul 2009 00:00 GMT
When a visitor registers a new account on an ASP.NET website that uses the Membership system, they are prompted (by default) for their username, password, e-mail address,
and other pertinent information. Along with functionality for registering new accounts, the ASP.NET Membership system provides page developers techniques for modifying
information about users. For instance, with just a couple of lines of code you can change an existing user's e-mail address, approve a user, or unlock them (if their account was
locked out). However, there are certain bits of user information that cannot be modified through the Membership API, such as the username.
For most sites this is a non-issue. Once a visitor has registered an account that username is fixed; if they want a different username, well, they'll just have to register
a new account. But consider a website that has customized the account creation process so that instead of prompting the user for both a username and e-mail address, the user
is only asked to enter an e-mail address and that it is used as both their username and e-mail address on file. Anytime a user switched e-mail addresses - which can happen
when changing jobs, changing ISPs, or moving to the new, hip, web-based e-mail provider of the day - they need to also change their username on your site.
In order to change a user's username we'll need to bypass the Membership API and work directly with the user store. This article shows how to interface directly with the
SQL Server database schema used by the SqlMembershipProvider to change an existing user's username. Read on to learn more!
Read More >
Source: 4GuysFromRolla ASP.NET Master Page Advice, Tips, and Tricks 24 Jun 2009 00:00 GMTMaster pages are an important part of any ASP.NET website. In a nutshell, a master page allows the page
developer to define a website template, indicating what portions of the template are to remain fixed across pages that use the template and what regions of the template
are customizable on a page-by-page basis. Having the site design and layout centralized in one (or more) master pages makes it easy to add new pages to the site that inherit
the same look and feel and greatly simplifies changing the site design or adding or removing content that is common to all pages, such as content in the <head>
element, footers, and references to CSS and JavaScript files.
This article presents advice for using master pages, along with assorted tips and tricks that I've picked up over the years in using master pages. Read on to learn
more! And if you have additional recommendations and advice on using master pages, please don't hesitate to drop me a line
and I'll be happy to add your insight to this article.
Read More >
Source: 4GuysFromRolla Monitoring the Long-Term Health of .NET Applications 17 Jun 2009 22:15 GMTToday's organizations have realized that the total cost of applications includes not only development, deployment, and training costs, but also costs associated with the long-term monitoring and maintenance of the application.
Source: DevX