Shulou(Shulou.com)06/03 Report--

This article mainly explains "what is the architecture of .NET". The content of the explanation is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn what the architecture of .NET is.

What is the architecture of .NET?

1) first of all, let's introduce the physical layer, which is what we usually call Entity

Entities are some of the objects that we will involve in the process of developing the project. The objects involved (such as news name, news upload time, contributor, name of uploaded file, etc.) are abstracted into a class. Using the encapsulated field method, we can assign values to the properties of our objects by instantiating objects in the view layer (mainly the view layer).

Simply look at a piece of code, may be able to more clearly, understand

PublicclassNewsModel

{

/ / News number

PrivateintnNewsId

PublicintNNewsId

{

Get {returnnNewsId;}

Set {nNewsId=value;}

}

/ / News name

PrivatestringstrNewsName

PublicstringStrNewsName

{

Get {returnstrNewsName;}

Set {strNewsName=value;}

}

}

NewsModel here is an entity class about news, which declares two property fields of private (must be private to prevent illegal assignment). Using the constructor of public, you can assign values to the fields outside.

The following is to instantiate the object in the view layer and assign values to the field as needed, see the following code:

NewsModelnewModel=newNewsModel ()

NewModel.StrNewsName=this.TextBox1.Text

Of course, this is just a piece of code that does not assign a value to the field nNewsId, because I have set it to grow automatically as the id sector of the database. In this way, the call of the view layer to the entity layer is completed.

What is the architecture of .NET?

2) Database access layer

Database access layer, as the name implies, is mainly to complete the access to the database, such as a series of classes for database operation. Why should the operation of the database be abstracted into a separate class? I personally understand that in the development process of the whole project, it is not only necessary to access the database once, but many times. If you write database access code every time, it will increase the programmer's personal workload, and it must be very bad for the ease of use and simplicity of the code. Of course, there may be some other advantages, which I haven't found yet.

Since it is the operation class of the database, and the operation of the database, there are nothing more than four kinds: additions, deletions, modifications and queries. Therefore, a general class that can provide additions, deletions, modifications and queries is essential. This is what we often say, the general database access class (many programmers like to name this class SqlHelper, since it is a name, it can be picked up at will, as long as it does not violate the C # syntax naming specification, of course, such naming is also beneficial, that is, other programmers can roughly determine what this class is going to do according to the name of the class).

Of course, when I was working on my own project this time, the database access class I wrote was not as complex as the database access class I wrote last time when I read Mr. Zhou Jinqiao's book and then imitated it ("[ASP.NET development] ASP.NET 's general database access class to SQLServer"). Of course, my database access class here is mainly for introduction, and easy to use, as long as it meets the needs of my own current project, not every time I do a project, I have to write a full-featured database access class.

The code is as follows. Please refer to which access class you prefer. You can use it directly according to your own taste or need:

/ / /

/ / create a general database access class of SqlHelper to complete all operations on the database

/ / /

PublicclassSqlHelper

{

/ / define the connection string for the database

PrivatestaticreadonlystringconnectionString=ConfigurationManager.ConnectionStrings ["strConnectionString"] .ConnectionString

/ / /

/ / create method to complete the operation of non-query to the database

/ / /

/ sql statement

/ parameters passed in

/ / /

PublicstaticintExecuteNonQuery (stringsql,paramsSqlParameter [] parameters)

{

Using (SqlConnectioncon=newSqlConnection (connectionString))

{

Con.Open ()

Using (SqlCommandcmd=con.CreateCommand ())

{

Cmd.CommandText=sql

Cmd.Parameters.AddRange (parameters)

Stringstr=sql

Returncmd.ExecuteNonQuery ()

}

}

}

/ / /

/ / complete the result value of the query

/ / /

/ sql statement

/ / the parameter array passed in

/ / /

PublicstaticintExecuteScalar (stringsql,paramsSqlParameter [] parameters)

{

Using (SqlConnectioncon=newSqlConnection (connectionString))

{

Con.Open ()

Using (SqlCommandcmd=con.CreateCommand ())

{

Cmd.CommandText=sql

Cmd.Parameters.AddRange (parameters)

ReturnConvert.ToInt32 (cmd.ExecuteScalar ())

}

}

}

/ / /

/ / mainly execute query operations

/ / /

/ / sql statement executed

/ / Parameter array

/ / /

PublicstaticDataTableExecuteDataTable (stringsql,paramsSqlParameter [] parameters)

{

Using (SqlConnectioncon=newSqlConnection (connectionString))

{

Con.Open ()

Using (SqlCommandcmd=con.CreateCommand ())

{

Cmd.CommandText=sql

Cmd.Parameters.AddRange (parameters)

SqlDataAdapteradapter=newSqlDataAdapter (cmd)

DataTabledt=newDataTable ()

Adapter.Fill (dt)

Returndt

}

Thank you for your reading, the above is "what is the architecture of .NET" content, after the study of this article, I believe you have a deeper understanding of what the architecture of .NET has, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.