Architecture of Microsoft. NET Framework Development Platform

. NET platform Composition

1 underlying operating system Windows

Because Web services and applications that use Web services are still running on computers, and computers have peripherals, we still need an operating system .. XML support is added for windows .. windows XP and Windows .net (now renamed Windows Server 2003) All versions provide the best support for the service-driven world.

Windows XP and Windows 2003 Server are particularly integrated with Microsoft. NET Passport XML Web Service Support. passport is a user authentication service .. when you log on to a passport-certified web site or web service, the efficiency will be greatly improved. in other words, users no longer need to enter the user name and password each time they access different Internet sites.

In addition, both Windows XP and Windows Server 2003 provide built-in support for the. NET Framework.

2 auxiliary products:. NET Enterprise Servers

These products mainly help enterprises with information and information integration.

Microsoft Application Center

Microsoft Biztalk Server 2000 (a new version is available now)

Microsoft Commerce Server 2000

Microsoft Exchange 2000 email server

Microsoft hostintegration Server 2000

Microsoft Internet Security and Acceleration (ISA) Server 2000

Microsoft mobile info Server 2002

Microsoft SQL Server 2000

This product was just launched with us. NET platform does not matter. however, in the future. NET features are integrated into these products, and the latest version of BizTalk is integrated. NET feature, which is poor and developed through vs.net 2003.

3 Microsoft XML Web Service:. Net my servers

Microsoft, as the underlying technology provider of Web Services, also launched its own XML Web Service.

. Net alerts

. Net applicationsettings

. Net calendar

. Net categories

Wait ......

4. Development Platform:. NET Framework

The. NET Framework consists of the Common Language Runtime --- Clr and the. NET Framework class library (framework class libarary -- FCL ).

The. NET Framework is the most critical part of the. NET platform.

This book discusses the development of. NET Framework-oriented applications and XML Web Services.

. NET framework development platform allows us to create a variety of applications: XML Web Services, web forms, Win32 GUI programs, Win32 Cui applications, windows services, utilities, and independent component modules.

Windows 2003 Server has built-in. NET Framework

Microsft. the Net Framework provides developers with more technologies than any previous Microsoft development platform, for example, code reuse, code specialization, resource management, multilingual development, security, deployment, and management. When designing the. NET Framework, Microsoft also felt it necessary to improve some defects of the current Windows platform.

Some services provided by Clr and FCL:

L consistent programming model

In the current Windows operating system, some functions need to be accessed through the dynamic link library DLL, and some functions are accessed through the COM object. Under the. NET Framework, all application services are provided to developers with a consistent and object-oriented programming model.

L simplified programming

One of the goals of CLR is to simplify the complex infrastructure required in Win32 and COM environments. In CLR, we do not need the registry, globally unique identifier, iunknown, addref, release, and hresult.

L reliable version Mechanism

The. NET Framework uses a new version mechanism to isolate application components, ensuring that an application can always load the components used in the original test. The "DLL hell" door was closed completely.

L lightweight Deployment Management

In the. NET Framework, components are no longer referenced by the Registry. Most. NET Framework applications only need to copy files to a directory. Add shortcuts to the desktop and Start Menu.

L extensive platform support

The source code of the compiled. NET Framework is actually a common intermediate language. CLR translates these intermediate languages into CPU commands only at runtime. This means that as long as a machine contains Clr and FCL compatible with ECMA, we can deploy. NET Framework applications on it.

L seamless language integration

CRL requires that all languages targeting it comply with a common type System (CTS) specification and general language specification.

L simple code reuse

L Automated memory management (garbage collection)

CLR automatically tracks resource usage.

L solid type security

CLR ensures that all code is type-safe.

L rich debugging support

CLR fully supports cross-language debugging

L unified error reports

In CLR, all failed calls are reported through exceptions.

L brand new security policies

Traditional security mechanisms are controlled based on user accounts.

Code access security in CLR provides code-centric control.

L powerful interoperability

The. NET Framework fully supports COM and Win32 functions in traditional DLL.

5. integrated development environment Visual Studio. NET

Microsoft Visual stuaio. NET 2003 is the best. NET Framework application development tool.

Summary:

This chapter mainly describes the composition of the. NET platform and the features of the. NET platform, Clr and FCL.

The. NET Framework has 13 major features:

1. Consistent programming model

2. simplified programming

3. Reliable version Mechanism

4. Lightweight Deployment Management

5. Extensive platform support

6. Seamless language integration

7. Simple code reuse

8. Automated memory management (garbage collection)

9. Solid type security

10. Rich debugging support

11. Unified error reports

12. New Security Policies

13. Powerful interoperability

In fact, I personally feel that Article 5th is not very meaningful at present, because until now the. NET Framework can only be used well on windows. I have heard of a mono, but it is not very mature yet? 12th is actually very important. The security mechanism based on user accounts is not secure for the Internet, which will directly affect the popularity of. NET and my job bowl :).

In addition, I only know some of the enterprise servers of Microsoft, and others do not know what to do. There is no time to take the initiative to find relevant information. I participated in Microsoft developer day some time ago to know what BizTalk is. The speaker is also awesome. The dizzy things written on the materials are clearly explained by him and can be understood as soon as they are heard.

Technology, language features, or some integration solutions can only take the initiative to use it if you understand it, but the problem is that in many cases, it can also work normally if you do not use it, it only takes more time and cost. When I solve the problem at a higher cost, I don't know that there is a better solution, and it's just around me. I don't have much time to study the technology and characteristics behind the endless nouns.

There are two ways to solve this problem: Try to understand new things as much as possible, even if you initially think it is different from your work and interests. The other one is to expect those providers (such as Microsoft) to highlight more issues that programmers can use to solve practical applications. (At least it looks like a programmer's publicity)