Eight Key Practices for ASP.NET Deployment 28 Jun 2008 00:40 GMTDiscover some best practices for deploying ASP.NET applications as well as a few useful procedures that you can follow to improve your application's performance.
Source: DevX Examining ASP.NET 2.0's Membership, Roles, and Profile - Part 11 25 Jun 2008 00:00 GMT
Many websites that support user account allow anyone to create a new account, but require new users to undergo some form of verification before their
account is activated. A common approach is to send an email to the newly created user with a link that, when visited, activates their account. This
approach ensures that the email address entered by the user is valid (since it is sent to that user's email address). This workflow not only ensures the
valid data entry, but also helps deter automated spam bots and abusive users.
In past installments of this article series we've seen how to use the CreateUserWizard control to allow users to create new accounts. By default, the
user accounts created by the CreateUserWizard control are activated; new users can login immediately and start interacting with the site. This default
behavior can be customized, however, so that new accounts are disabled. A disabled user cannot log into the site; therefore, there needs to be some manner
by which a newly created user can have her account enabled.
There are many ways by which an account may be activated. You could have each account manually verified by an administrative user. If your site requires
users to pay some sort of monthly fee or annual due, you could have the account approved once the payment was successfully processed. As aforementioned,
one very common approach is to require the user to visit a link sent to the email address they entered when logging on.
This article explores this latter technique. Read on to learn more!
Read More >
Source: 4GuysFromRolla Enable WPF/Windows Forms Interoperability with WPF Commands 20 Jun 2008 01:10 GMTWindows Presentation Foundation (WPF) can interoperate with Windows Forms, letting you add legacy controls to your new interface—or new WPF controls to your existing Windows Forms applications. Either way, you need to make them play nicely together.
Source: DevX Building Interactive User Interfaces with Microsoft ASP.NET AJAX: Using the Timer Control 18 Jun 2008 00:00 GMT
Microsoft's ASP.NET AJAX framework ships with a mere five Web controls: the ScriptManager and ScriptManagerProxy;
the UpdatePanel; the UpdateProgress; and the Timer. Previous installments in this article series have examined all but one control, the Timer.
As we've seen from the first installment, all web pages that use the framework
must have precisely one ScriptManager control on the page. The UpdatePanel control
defines a region on the screen whose content is updated via partial page postbacks, and the UpdateProgress
control provides visual feedback during the execution of a partial page postback. The Timer
control, which is the focus of this installment, raises a postback every time a specified number of milliseconds has elapsed.
The Timer control is useful in scenarios where a portion of the screen needs to be updated every so often. For example, many financial websites display
stock quotes that are refreshed periodically. Prior to AJAX, refreshing the stock quote entailed reloading the entire document, which would result in
a screen flash and necessitate the browser re-downloading the entire content of the page (even though the only change that has occurred is the
stock quote). Using AJAX techniques we can have the page asynchronously communicate with the server to get the latest quote every n millisconds
and seamlessly update the quote on screen. The Timer control, along with the UpdatePanel, make implementing such scenarios a breeze.
This article shows how to use the Timer control to trigger a partial page postback every five seconds. It also shows how to start and stop the Timer
through both server-side and client-side code. Read on to learn more!
Read More >
Source: 4GuysFromRolla