.NET platform composition
1 underlying operation system Windows
Since the web service and application using the web service are still running on the computer, and since it is a computer to be peripherals, we still need an operating system .. Windows adds XML support .. Windows XP and Windows.net (now Renamed Windows Server 2003) All versions provide the best support for the world-driven world.
Special WindowsXP and Windows 2003 Server integrate Microsoft .NET Passport XML Web Services support. Passport is a user authentication service .. When logging in to use Passport authenticated Web site and web services will be greatly improved. In other words, When users access different Internet sites, they will no longer need to enter usernames and passwords each time.
In addition, Windows XP and Windows Server 2003 provide built-in support for the .NET framework.
2 auxiliary product: .NET Enterprise Server
These products are mainly helpful for the company's information and information integration.
Microsoft Application Center
Microsoft BizTalk Server 2000 (now a new version)
Microsoft Commerce Server 2000
Microsoft Exchange 2000 Mail Server
Microsoft Hostintegration Server 2000
Microsoft Internet Security And Acceleration (ISA) Server 2000
Microsoft Mobile Information Server 2002
Microsoft SQL Server 2000
This product has just begun to be with our .NET platform. But in the future, it may be integrated into these products in the future. The new version of BizTalk is integrated .NET feature, poor and via vs.net 2003 .
3 Microsoft XML Web Services: .NET My Servers
The Microsoft has also launched its own XML web service while the underlying technology provider of a web service.
.NET ALERTS
.NET ApplicationSettings
.NET Calendar
.NET Categories
and many more……
4 Development Platform: .NET Framework
The .NET framework contains two parts: a common language runtime (Common Language Runtime --- CLR) and a .NET Framework Class Library (Framework Class Libatary - FCL).
The .NET framework is the most critical part of the .NET platform.
This book is discussed to develop applications and XML web services for .NET framework.
The .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 separate component modules.
Windows 2003 Server built-in .NET framework
MicroSft .NET frameworks provide more technologies provided by developers than any previous Microsoft platform, such as code reuse, code specialization, resource management, multilingual development, security, deployment, management, etc. When designing the .NET framework, Microsoft still feels necessary to improve some of the shortcomings of the current Windows platform.
Particular services provided by CLR and FCL:
l consistent programming model
Now Windows operating systems, some features need to be accessed through dynamic link library DLL, and some features are accessible through COM objects. Under the .NET framework, all application services will be provided to developers in a consistent, object-oriented programming model.
l Simplified programming method
One of the purposes of the CLR is to simplify the various complicated infrastructure required for Win32 and COM environments. Under CLR, we can do not need registration, the global unique identifier, IUNKNOWN, AddRef, Release, HRESULT, etc. l Reliable version mechanism
The .NET framework uses a new version mechanism to isolate the application component, ensuring that an application will always load the components used when the generated test is initially loaded. Thoroughly closed the gate of "DLL Hell".
l Light deployment management
Under the .NET framework, the component will no longer be referenced by the registry. Most .NET frameworks need to install the installation work is just to copy files into a directory. Then add a shortcut to the desktop, start the menu.
l Extensive platform support
The source code of the compiled .NET frame is actually a common intermediate language (Common Intermediate Language) only translates these intermediate languages into CPU instructions when running. This means that as long as there is a CLR and FCL compatible with ECMA, we can deploy the .NET framework application on that machine.
l Seamless language integration
CRL requires all languages that face it to follow a normative and general language specification called a common type system (CTS).
l Simple code reuse
l Automated memory management (garbage collection)
The CLR is the usual use of our automatic tracking of resources.
l Ligulent type security
CLR ensures that all code is safe.
l rich debugging support
CLR fully supports cross-language debugging
l Uniform error report
In CLR, all failures are reported by exception.
l New security strategy
Traditional security mechanisms are controlled based on user accounts.
Code Access Security in CLR provides us with code-centric control mode.
l Powerful interoperability
The .NET framework fully supports COM, and Win32 functions in traditional DLL.
5 integrated development environment Visual Studio .NET
Microsoft's Visual Stuaio .NET 2003 is the best .NET framework application development tool.
to sum up:
This chapter mainly tells the configuration of the .NET platform and the most critical part of the .NET platform --- CLR and FCL characteristics.
The 13 major features of the .NET framework:
1. Consistent programming model
2. Simplified programming
3. Reliable version mechanism
4. Lightweight deployment management
5. Extensive platform support
6. Seamless language integration
7. Easy code reuse
8. Automated memory management (garbage collection)
9. Solid type
10. Rich debugging support
11. Unified error report
12. Brand new security policy
13. Powerful interoperability
In fact, I personally feel that Article 5 is not very meaningful, because until now .NET framework can only be used in Windows, I heard a mono but isn't it very mature? Article 12 is actually very important, and the security mechanism based on user account is less secure for the Internet, which will directly affect the popularity of .NET, affecting my rice bowl :).
There is also a Microsoft's corporate server I only know part of the use, and the other part is not known to be used. There is no time to take the initiative to find relevant information. I participated in Microsoft Developer Day for some time, I know what BizTalk is doing. That speaker is also a cow. The dizzy thing written is clear, and he is clear and clear.
Technical or language features or some integrated schemes, only to understand it, they will take the initiative to use it, but the problem is, in many cases, it can be used normally, but it costs are more expensive. When I solve the problem with a higher price, I don't know if there is a better solution, and I am by my side. 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 a new thing, even if you start thinking that it is not equal to your work and interest. Another is expected to provide more issues in actual applications with those products when providing companies (such as Microsoft) can use those products to solve practical applications. (Attached to the programmer's propaganda is like this)
Until the BizTalk lecture, I know this thing is really suitable for our company. We can solve many tricky problems through BizTalk.
