Book Image

NHibernate 2 Beginner's Guide

By : Aaron Cure
Book Image

NHibernate 2 Beginner's Guide

By: Aaron Cure

Overview of this book

<p>NHibernate is an open source object-relational mapper, or simply put, a way to retrieve data from your database into standard .NET objects. Quite often we spend hours designing the database, only to go back and re-design a mechanism to access that data and then optimize that mechanism. This book will save you time on your project, providing all the information along with concrete examples about the use and optimization of NHibernate.<br /><br />This book is an approachable, detailed introduction to the NHibernate object-relational mapper and how to integrate it with your .NET projects. If you're tired of writing stored procedures or maintaining inline SQL, this is the book for you.<br /><br />Connecting to a database to retrieve data is a major part of nearly every project, from websites to desktop applications to distributed applications. Using the techniques presented in this book, you can access data in your own database with little or no code.<br /><br />This book covers the use of NHibernate from a first glance at retrieving data and developing access layers to more advanced topics such as optimization and Security and Membership providers. It will show you how to connect to multiple databases and speed up your web applications using strong caching tools. We also discuss the use of third-party tools for code generation and other tricks to make your development smoother, quicker, and more effective.</p>
Table of Contents (19 chapters)
NHibernate 2
Credits
About the Author
About the Reviewers
Preface
Index

User roles


Now that we have the ability to log a user in, we can filter data based on whether or not they are logged in, and even allow access to pages based on the same. But what if we need more granular control? What if we need to only allow access to certain controls to "Administrators", or "DataManagers"? Using the System.Web.Security.RoleProvider abstract classes, we can extend our control to a much tighter level.

A number of controls allow restricting access to roles, but my particular favorite is the <asp:LoginView> control. Not only does it let us restrict a user, whether logged in or not, but it can also restrict them by role. Have a look at the following code snippet:

<asp:LoginView ID="loginView" runat="server">
  <AnonymousTemplate>
    <asp:Login ID="login" runat="server" />
  </AnonymousTemplate>
  <LoggedInTemplate>
    Thanks for Logging In
  </LoggedInTemplate>
</asp:LoginView>

Now, when you navigate to the page, if you are logged...