【正文】 that we must get started now!! Chapter1 Introduction of the Microsoft .NET Platform Introduction The .NET platform is the foundation upon which the next generation of software will be built. Microsoft has invested a lot of capital in its development and attempted to make it as the new standard. A list of Microsoft partners has also supported .NET tools and ponents. You can check for a current list of vendors who have .NET offerings. The .NET platform is anything more than a mere new language, software development kit (SDK), or even an operating system. It offers powerful new services, a new processorindependent binary format, new managed languages, managed language extensions to existing languages, and so forth. Effectively using these new tools makes possible a firm background of the platform that will enhance your applications. In this chapter, we take a look at the various ponents of the .NET platform. We not only introduce the concept and technology, but explain the terminology used to describe them as well. This will enable you to have a strong understanding of the internal workings of the .NET platform, thus reaping more benefits from the following chapters. Introduction of the .NET Platform The precept behind the .NET platform is the shift from one of PCs connected to servers through works such as the Inter, to one where all manner of smart devices, puters, and services work together to provide a richer user experience. The .NET platform is Microsoft’s answer to the challenges this change will provide to software developers. How many ponents the .NET platform have? Different people have different answers. Servers such as BizTalk and SQL Server, as well as services such as .NET My Services and its first visible ponent, .NET Passport, are being described by some as integral parts of the .NET platform. Noheless, the .NET Framework, as far as many of us are concerned, can be anything that we can imagine when referring to .NET. It 重慶大學(xué)本科生畢業(yè)論文翻譯 9 prises Visual (), the .NET Common Language Runtime (CLR), and the .NET Base Class Libraries (BCL). The other ponents may be required by specific applications, but they are not the necessary part of all .NET applications. Looking at the overall architecture, .NET consists of three primary ponents: ■ The .NET Framework A pletely new application development platform. ■ Several .NET products Various applications from Microsoft based on the .NET Framework, including new versions of Exchange and SQL Server, which are Extensible Markup Language (XML)–enabled and integrated into the .NET platform. ■ Several .NET services Provided by Microsoft for developing applications running under the .NET Framework. Microsoft’s Hailstorm project actually attempts to package some of the most crucial Web Services under the Microsoft brand name. The .NET Framework itself can be divided into three parts: ■ The CLR A managed execution environment that handles memory allocation, error trapping, and interacting with the operatingsystem services. ■ The Base Class Library An extensive collection of programming ponents and application program interfaces (APIs). ■ Two toplevel development targets One for Web applications () and the other for regular Windows applications (Windows Forms) The advantages offered by the .NET Framework include shorter development cycles (code reuse, fewer programming surprises, support for multiple programming languages), easier deployment, fewer data typerelated bugs due to integral type safety, reduced memory leaks attributed to the garbage collector, and, in general more scalable, reliable applications. Microsoft .NET and Windows DNA If the propagation regarding .NET sounds familiar, there’s a good reason: The .NET platform is the next generation of Windows DNA. However, although Wi ndows DNA offer some of the building blocks for creating robust, scalable, distributed systems, it generally had little substance in and of itself. Windows DNA was a technical specification that focused on building software based on Microsoft server products, utilizing numerous technologies and languages (ASP, HTML, JavaScript, MTS, COM, and so on), many of which are quite unrelated from a developer’s point of view. The servers and languages involved all have varying APIs and type systems, making interoperability a challenge at best. Herein lies the big difference: .NET is much more than a specification. A product in its own right, it includes the tools and languages required to make developing these types of ntiered applications easier, neatly packaged as a single coherent and prehensive API. Microsoft .NET Architecture Hierarchy The pile of .NET families of languages are, in essence, different from the 重慶大學(xué)本科生畢業(yè)論文翻譯 10 output of Microsoft Intermediate Language (MSIL, or just IL) rested on the Common Language Specification. The primary types of application development are Web Forms, Web Services, and Windows Forms applications. These applications municate by way of using XML and Simple Object Access Protocol (SOAP), getting their functionality from the Base Class Library and running within the Common Language Runtime environment. Visual Studio .NET is not required in order to develop .NET Framework applications。 譯文原出處 : C.NET 開(kāi)發(fā)者指南 C . N ET Web Developer39。您最終可能會(huì)在不同的情況使用不同的代碼 ■調(diào)用 DLL函數(shù) 現(xiàn)在有許多函數(shù)都綁定了 DLL。 其實(shí)是 各種服務(wù)器和應(yīng)用程序在后臺(tái) 運(yùn)行，當(dāng) 訪問(wèn)幾個(gè)遠(yuǎn)程站點(diǎn)的信息 時(shí) ， 服務(wù)器 結(jié)合自己的用戶信息數(shù)據(jù)庫(kù)， 合并成一個(gè)集成產(chǎn)品 ，用戶 則瀏覽 傳遞到瀏覽器上的 信息 。即使 專(zhuān)門(mén)設(shè)計(jì) 一種 第三方 軟件 ，使 得 更容易開(kāi)發(fā) 一些 工具，但要正確 地 在檢索中 安裝一個(gè)應(yīng)用仍然是一項(xiàng)艱巨的任務(wù)。因?yàn)?SOAP 是一個(gè)類(lèi)似于 HTTP 的簡(jiǎn)單的基于文本的協(xié)議，它可以輕易地穿過(guò)防火墻，不像 DCOM或 CORBA。如果應(yīng)用程序安裝運(yùn)行后，應(yīng)用程序應(yīng)該始終運(yùn)行。 但是，如果 現(xiàn)在他們的新軟件不工作 了 ， 那么 就是 DLL HELL發(fā)揮作用了。因此，除非它們是隱式解構(gòu)，不然他們的內(nèi)存可能永遠(yuǎn)不會(huì)被發(fā)現(xiàn)。該小組正在開(kāi)發(fā)一個(gè) C＃語(yǔ)言的編譯器，以及 .NET公共語(yǔ)言運(yùn)行庫(kù)，而且關(guān)于基類(lèi)庫(kù)的工作也開(kāi)始了。 .NET應(yīng)用程序可以 在任何平臺(tái)上支持寫(xiě)、新建以及托管，這樣就可以支持 .NET公共語(yǔ)言運(yùn)行庫(kù)?，F(xiàn)