Show description

We can always add to the system as our needs increase. Our permissions system will simply encompass a name/role (Administrator, Editor, Restricted, and so on). ). As long as we keep our pages to serve a single functionality, this should always suit our needs. As this is a good design practice anyway, we shouldn't have any problems here. Of course, a user can have many permissions tied to their accounts so that they can traverse various sections of our site. Once this is in place, all we need to do is have a system that checks a user's permissions upon entering each page to ensure that they have the permission that the page requires.

For that reason, we created a simple Person table for us to work with. It has the following fields: PersonID, FirstName, LastName, and Email. We then created four entries in the database for us to work with. edmx file). Building Extensibility using Managed Extensibility Framework (MEF) To support extensible architecture we need to build several extensibility points that if needed can be easily replaced seamlessly with different implementations. For example, replace one caching implementation with another caching one.

Presentation Layer: This layer would normally hold anything pertaining to the user interface of your application—the buttons, links, and other controls that a user would click on and interact with while using your application. • Business Logic Layer: This is where the rules of your application would live. This could be as simple as formatting the currency of a price in your product catalogue to something more complex such as enforcing rules regarding data input. • Services Layer: While building Service Oriented Architecture (SOA), services layer is built on top of the business logic layer.