Data access principal for . NET application

[Christina 80]

Hi all,

I am building .net application .I want to connect the .net application with database. I already use SQL 2005, but i want to know that some Data access principal for . NET application. Please advice. Thanks in advance.

[kelfro]

. NET Framework components of the work of developers is to achieve a core data access functionality, they established data access layer is the essential parts of the application. You can use of Visual Studio. NET and the. NET Framework components to establish data access layer needs to be considered the idea. Using the base class the use of object-oriented technology. NET Framework component-based structure, so are easily inherited, in determining the display method and external interface for pre-test requirements carefully.

[Zecho]

The most basic object-oriented transaction is to build an abstract class using inheritance. This base class can include all of your data access classes by inheritance able to use the service. If those services are adequate, and they can through the base class distribution of the entire organization to achieve re-use. For example, the simplest situation is the base class for derived classes to handle the process of establishing the connection. Check and reply.

[Reegan]

Sharing Methods can also be used to expose all instances of data access class to access fields, properties and methods. Although members can not share with the use of Component Services together with the use of the class, but for a shared data access class constructor to retrieve all instances and is read by read-only data is useful. Using shared members of the read / write data to be careful, because in order to access the shared data, implementation of multiple threads may be competitive. Best of luck.

[opaper]

. NET Framework components, including some classes and structures, they can deal with the usual supporting infrastructure-related matters, such as device and exception handling. Through the base class and inheritance of these concepts combined will be very strong. For example, you can consider in the System.Diagnostics namespace exposure tracking. In addition to providing Trace and Debug classes on, the name space also includes Switch and TraceListener derived from the class. Switch class BooleanSwitch and TraceSwitch can be configured to open and close applications and configuration files, in the TraceSwitch can be exposed to multi-level tracking. TraceListener class TextWriterTraceListener and EventLogTraceListener methods, respectively, Trace and Debug the input location to a text file and event log. Check and reply.

[MindSpace]

Design data access classes in your way, you need to consider how they accept and return data. For most developers, there are three options: direct use of ADO.NET objects, using XML, use a custom class. If directly exposed to ADO.NET objects, you can use one or two programming model. The first includes data sets and data table objects, they are not connected to the data access very useful. There are many data sets and data tables associated with it an article, but when you have to use disconnected from the underlying data store the data when it is most useful. Best of luck.