Understanding the .NET Platform

<< n-tier Application | .NET Platform Architecture >>

We may also have a data input validation rule component on the client to check simple
rules such as required fields and formatting. These are rules that you do not want to make
a trip across the network just to check. You may then also add a business rule layer on the
same tier as the data layer component to check complicated business rules that compare
the data from one table to another.

These are just a few different configurations that you may utilize. Of course, you could
come up with something unique that fits your specific situation. Regardless of how you
structure the physical implementation of the components, make sure that the logical
structure of the program is broken up into components as shown in the above figures.

2.4 Understanding the .NET Platform and its layers

Here in this section we will be covering what the .NET Platform is made up of

and we will define its layers. To start, .NET is a framework that covers all the layers
of software development above the Operating System. It provides the richest level of
integration among presentation technologies, component technologies, and data

technologies ever seen on Microsoft, or perhaps any, platform. Secondly, the entire
architecture has been created to make it easy to develop Internet applications, as it

is to develop for the desktop.

Constituents of .NET Platform

The .NET consists of the following three main parts

.NET Framework a completely re-engineered development environment.

.NET Products applications from MS based on the .NET platform, including
Office and Visual Studio.

.NET Services facilitates 3

party developers to create services on the .NET

Platform.