As I said earlier, ASP.NET 2.0 is packed with set of new controls called Login controls through which we can implement forms authentication with less effort. This section will take us through how best to use these Login controls in our projects. By default, Login controls will use the default membership provider and role provider which will have their own database schema. So, it is not advisable to use this controls as it is because enterprise applications itself will have its own database schema and architecture. The solution for this problem is to develop our own custom provider or our own custom code that solves our application specific requirements. However, we can still use some of the login controls, like LoginView, LoginName and LoginStatus, in our applications. In this article I will explain our subject matter with a custom implemented login form without using any login control on it. Also, we will have a look on how to use some of the login controls effectively with role based forms authentication. Moving forward, I will explain a sample scenario where we can use role based forms authentication and will use the same scenario throughout this article for easy understanding.