i want to konw which is better mvc or 3-tier.pls dont say both are simillar.i have to chose which should be chose if i select to one only and why
View Complete Post
I am a beginner in c#.I heard that writing program with three tier architecture are easy and maintainable.
I just wanted to know with a small example on how to write three tier architecture programs.
Started in middle of a new project. Our design architecture uses an n-tier (not MVC - no controllers) structure with Presentation, Data, Business and Service tiers. However the lead analyst has the majoriety of code all in the Business tier claiming it all contains Business logic. Our data tier is nothing more than a single .dbml model of the primary database to support all of the Linq queries in the Business tier. To my mind Linq queries and classes they use are data access and belong in the data tier but our lead analyst says they contain business logic therefore have to be in business layer.
Hi i want to develop an application in asp.net using 3 tier architecture .
i know that there are three layers
I am confused between Data Access Layer and Business Logic Layer.
In data access layer we develop the property classes and main class function which returns datasets, datatables and data reader to Presentation layer.
what is the use of Business Logic Layer ? what actually we do in Business logic Layer ?? we can pass data directly from data access layer to presentation layer ?? can anyone give any small example to understand ??
Tier interaction profiling (TIP) is a feature of the Visual Studio profiling tools that measures the duration of synchronous calls to ADO.NET-compliant data stores. We'll show you how TIP works and provide some best practices for using TIP to diagnose performance problems in your apps.
MSDN Magazine August 2010
This article is the third in a series about n-tier programming with the Entity Framework, specifically about building custom Web services with the Entity Framework and WCF. This article looks at features coming in the second release of the Entity Framework (EF4) and how you use them to implement the Self-Tracking Entities and Data Transfer Objects (DTOs) n-tier patterns.
MSDN Magazine November 2009
This article examines n-tier patterns for success and some of the key APIs and issues specific to the Entity Framework. It also provides a sneak peak at features coming in the Microsoft .NET Framework 4 that should make n-tier development significantly easier.
MSDN Magazine August 2009
Danny Simmons explores some anti-patterns you should look out for when building n-tier applications with the Entity Framework.
MSDN Magazine June 2009
Authorization Manager in Windows Server 2003 represents a significant improvement in the administration of role-based security, making it more scalable, flexible, and easier to implement. Using Authorization Manager, you can define roles and the tasks those roles can perform. You can nest roles to inherit characteristics from other roles, and you can define application groups. In addition, Authorization Manager lets you use scripts to modify permissions dynamically, and it allows you to wrap your security logic in a security policy that can be stored in Active Directory. Authorization Manager also includes an easy-to-use API for running access checks. The author discusses all of these topics and demonstrates them with a working sample.
MSDN Magazine November 2003