Introduction
Microsoft is known for given that good tools for RAD (Rapid Application Development) tools for developers. MS Access, Visual Studio 6, Visual Interdev and others have given surroundings to visually unite controls, properties, and generated code for fast applications. Visual Studio .NET has combined the best of the previous tools into a great development environment with several unlike coding languages.

There are a lot of wizards in Visual Studio .NET (VS) that assist new users in creating applications. Unluckily, they are likely not to support good programming habits--specifically present is not a division of code into layers and they do not attach to OOP standards dividing business logic. The default replica of VS is to drag and drop data matter onto the shape we are building. VS make the code essential, but combine the data access code and the business logic code straight in the user interface form thing. This limits the reusability of the code and tends to photocopy code where the similar table data is used on other than one form.

Most architects suggest more of an n-tiered come up to where the code is divided into different layers. There should as a minimum be a data access layer, business logic layer, and a presentation layer. When working with distributed applications additional layers can require to be added.

There are two main advantages for extrication the layers: code reusability and de-coupling code as of the database. By unraveling out the data access and business logic layers, a lot of different forms may be used to gather and display the information with no rewriting the code to access and utilize the information. The de-coupling helps remain your code from flouting when the database plan changes and makes it easier to still change data storage providers without a good deal code change.

Microsoft .NET has completed great treads in supporting and hopeful developers to move toward Object Oriented Programming (OOP) standards. While OOP is a large and deep subject, one surface that should attention developers of database applications is the idea of a business object. Although database tables and fields do a good job of realizing entities and attributes, business substance bring jointly both the properties and actions of an exacting entity. When the application instantiates a business entity class to stand for each entity table, the attributes can be accessed from end to end properties and the actions of the entity can be called through methods. This concept as well brings all the code for a body together keen on one place that can be referenced easily from additional parts of the application. During inheritance and polymorphism, the business objects can be fairly supple and have considerable power to complete much with small code.

Part 2 - Using Visual Studio 2005
The new version of .NET and Visual Studio presents quite a few developments that change the method we expand database centric applications. In the context of this article, we will be appearing especially at Data Sources and incomplete Classes.

The Binding framework Manager has been extensive and greatly simplified into Binding Sources module that permits forms to offer better data binding to datasets, Web services, and business objects.

Partial Classes gives a way to expand classes across various files which will be shared together at compile time. The typed Dataset class has been extensive to contain partial classes, separating generated code from hand made code, allowing us to put in business logic to the dataset class with no the difficulties of inheritance.