1.NET is the concept of a platform, an abstract platform.
. NET platform its own implementation of the way is actually a library, at the level of abstraction is a platform.
The. NET framework consists of two key constituent elements:
A.common Language Runtime, Common language Runtime (CLR)-provides features such as intrinsic management, code security detection, and more
B.. NET Framework Class Library,. NET Framework class Library (FLC)-Provides a large number of application class libraries to improve development efficiency
Learning the. NET Framework is a must for all. NET developers, otherwise developed. NET program is always stuck in ' drilling ', the net Framework is one of the ' internal skills ' of the. NET development guru.
2, C # is a programming language, is only a language.
Programming language is just for the convenience of developers and computer communication tools, although C + + syntax is more than C and C + +, but relative to the C # syntax is relatively fixed, so it is easy to use. I agree with a friend that C # is more rigorous in grammar!
Come back here and see. NET and C # relationships, it has to be mentioned. NET program to execute the process.
C # conforms to the common language runtime specification in the. NET CLR. Cls:common language Specification, of course, all of the. NET language are compliant with this specification for example: VB.net, XAML, and C + +/cli .... Wait a minute.
C # needs to conform to the. NET CLS because the. NET CLR is similar to a Java Virtual machine and has an intermediate language common to the machine to execute. All of the different languages. NET code is compiled into the same intermediate language (MSIL) before execution, so all. NET support language must conform to the CLS-compliant specification.
P.S: If you're a friend of a. NET 3.0 XAML developer, you can try to look at the XAML application under Ildasm.exe, and you'll find that the original XAML is really simple.
3. ASP. NET is a programming framework built on the common language runtime that can be used to build powerful WEB applications on the server.
Compared to the previous Web development model, ASP. NET provides several important advantages: enhanced performance.
ASP. NET is the compiled common language runtime code that runs on the server. Unlike the explained predecessors, ASP. NET can take advantage of early binding, real-time compilation, native optimization, and out-of-box caching services. This is equivalent to significantly improving performance before writing lines of code.
World-class tool support: The ASP. NET Framework complements a large number of toolboxes and designers in the Visual Studio integrated development environment. WYSIWYG editing, drag-and-drop server controls, and automatic deployment are just a few of the features provided by this powerful tool.
Power and flexibility: because ASP. NET is based on the common language runtime, WEB application developers can take advantage of the power and flexibility of the entire platform. The Web Framework class library, message processing, and data access solutions are all seamlessly accessible from the website
Asp. NET is also language-independent, so you can choose the language that best suits your application, or a split application that spans multiple languages. In addition, the interoperability of the common language runtime guarantees that existing investments in COM-based development are preserved when migrating to ASP.
Simplicity: ASP. NET makes it easy to perform common tasks, from simple form submission and client authentication to deployment and site configuration. For example, ASP. NET page framework allows you to clearly separate the application logic and presentation code from the user interface and handle events in a simple form-processing model like Visual Basic.
In addition, the common language runtime simplifies development with managed code services such as automatic reference counting and garbage collection. Manageability: ASP. NET uses a text-based hierarchical configuration system that simplifies the application of settings to server environments and WEB applications.
Because the configuration information is stored as plain text, you can apply the new settings without the help of the local administration tools. This "0 local management" philosophy is also extended to the deployment of ASP. You can deploy an ASP. NET Framework application to a server by simply copying the necessary files to the server. You do not need to restart the server, even when you are deploying or replacing a running compiled code. Scalability and availability. The design of ASP. NET is designed with scalability in mind, adding features specifically designed to improve performance in clustered environments and multiprocessor environments.
In addition, processes are closely monitored and managed by the ASP. NET runtime, so that when the process behaves abnormally (leaks, deadlocks), new processes can be created in place to help keep the application always available for processing requests. Customization and Extensibility: ASP. NET comes with a well-designed architecture that allows developers to "insert" code at the appropriate level. In fact, you can extend or replace any subcomponents of the ASP. NET runtime with custom components you write. It makes it easier to implement custom authentication or State services.
Security: With built-in Windows authentication and per-application-based configuration, you can keep your applications secure.
4. ADO. NET is a standard-based program design model that can be used to create distributed applications for data sharing in ADO, the dataset occupies an important position, which is a part of the data in the database in-memory copy. Unlike a recordset in ADO, a dataset can include any data table, and each data table can be used to represent data from a database table or view.
The dataset resides in memory and is not connected to the original database-the underlying technology that does not need to remain connected to the original database is XML, which is the storage and transport format used by the dataset.
During run time, the data in the dataset needs to be exchanged between components, such as a business logic object or an ASP. The data is transferred from one component to another in the form of an XML file, and the receiving component restores the file to the DataSet form. The method of the dataset is exactly the same as the relational data model