Section 6 Components

Presentation Transcript

Section 6 .NET Components

Objectives of Chapter 6 .NET Components Introduce .NET structure Introduce the ideas of .NET parts Discuss the sorts of .NET segments, associations of segments, and their arrangements Distinguish nearby and dispersed segments Distinguish conglomeration and control creations Distinguish synchronous and offbeat strategy summons Provide well ordered instructional exercises on building, conveying, and utilizing .NET segments

Overview of .NET Framework The .NET system is one of the most current advancements presented by Microsoft Corporation. Its first Beta variant was discharged in 2000. The .NET system is a stage for quick and simpler building, conveying, and running secured .NET programming parts to be coordinated in applications and for fast creating XML web administrations and applications. It gives an exceedingly gainful, segment based, multi-dialects condition for coordinating existing applications with web to meet the difficulties of new applications for organization and operation of web scale applications.

Overview of .NET Framework (cont.) The .NET system envelops a virtual machine that gives another stage to programming improvement. The center of the .NET system incorporates XML and Simple Object Access Protocol (SOAP) to give web benefits over Internet. The idea of the .NET structure is to encourage the advancements of desktop, window, and electronic application benefits on Windows stage and make them accessible and available on Windows stage as well as on different stages through regular conventions, for example, SOAP and HTTP.

Overview of .NET Framework (cont.) First, .NET streamlines the componentization particularly for Component Object Model (COM), Distributed COM (DCOM) innovation. In spite of the fact that COM segments can be reused as module play programming segments in part programming and application developments however the advancement procedure is excessively mind boggling and COM does not bolster forming (next to each other execution), which may bring about variant clash (DLL Hell issue). The .NET innovation underpins part gathering arrangement which permits various adaptations of same named segments to coincide with no contention. .NET innovation disentangles the creation, and arrangement of parts notwithstanding securing dependable and adaptable administrations gave by segments.

Overview of .NET Framework (cont.) Secondly, .NET encourages advancements of dispersed parts by Remoting Channel innovation. .NET system bolsters the interoperability amongst COM and .NET segments. The XML web administration is another sort of part. A .NET part can work with any current COM segments. At the end of the day, .NET can give administrations to COM parts and COM segments can likewise be utilized by any .NET segments. .NET is considerably less demanding to create segments than COM. Web administration is a trade of MS DCOM innovation for Internet applications upheld by XML, SOAP and HTTP conventions. .NET liberates designer's coding from substantial undertaking programming, for example, exchange administration through Enterprise Service. .NET web benefit conquers DCOM's absence of support for firewall and makes administrations accessible crosswise over stages by means of approximately coupled XML SOAP conventions.

Overview of .NET Framework (cont.) The .NET structure is accessible in .NET Framework SDK and Visual Studio.NET IDE SDK, both of which can be downloaded from MS site and they are likewise accessible in a CD pack. The .NET Framework SDK is the establishment of Visual Studio .NET and is a piece of Visual Studio .NET when Visual Studio .NET is introduced. The .NET structure comprises of two primary parts (as appeared in Figure 6.1): Common Language Runtime (CLR) and an arrangement of brought together system essential class libraries including ASP.NET web frames for building web applications, Windows Forms for building desktop applications, and ADO.NET for information get to. The SDK incorporates all your need to compose, construct, test, and convey .NET applications. It underpins every single .NET dialect, for example, VB .NET, VC.NET, C#, and others. .NET SDK and Visual Studio .NET can get to administrations of all layers in the .NET structure stage.

Foundation of .NET structure – CLR Common Language Runtime (CLR) is a virtual machine condition sitting on the highest point of Windows working framework. CLR comprises of Common Type System (CTS), Just-In-Time IL Compiler (JIT), Execution unit, in addition to some other administration administrations, for example, waste gathering and security administration. CLR resembles JVM in Java. All these product parts are gathered in a bundle of get together (simply like Java document record .jolt document) which comprises of MS Intermediate Language (MSIL) code and show (Metadata about this parcel). The IL code is converted into local code by JIT compiler in CLR. IL code is confirmed by CTS first to check the legitimacy of information sort utilized as a part of the code.

Foundation of .NET structure – CLR (cont.) .NET system coordinates different programming dialects (VB, oversaw VC#, C# and so forth) by Common Language CLR execution. Not just a part in one dialect can get to the administrations gave by different segments in different dialects, additionally a class in one Language can acquire properties and techniques from related classes in different Languages. The United Class Library gives an arrangement of reusable classes for segment advancement. The CTS characterizes a standard arrangement of information sort and principles for making new sorts. The CLR knows how to execute these sorts. There are two classes of sorts: Reference sort and Value sort. The code focusing on LCR and to be executed by LCR is called .NET oversaw code. All MS dialect compilers create oversaw codes that adjust to the CTS.

Foundation of .NET structure – CLR (cont.) The IL code resembles Java byte code. Despite the sorts of source code programming dialects IL codes can speak with each other by backings of the CLR. The IL code can be either in the organization of executable (.EXE) or Dynamic Link Library (.DLL). On the off chance that these IL codes are created by .NET compiler, they are called overseen code . The oversaw code can be executed just on .NET mindful stage. Some DLL or EXE created by non .NET compilers, (for example, early form of VC++) are called un-oversaw code.

Foundation of .NET structure – CLR (cont.)

In rundown, The CLR is a superior execution motor. It gives a code-execution condition which deals with the code focusing on the .NET structure. The code administration incorporates administration of memory, string, security, code check and IL aggregation.

The .NET Framework Class Library The .NET structure class library is an accumulation of reusable fundamental classes which are efficient by namespaces. The structure class library gathers all classes including Windows Foundation Classes (WFC) into a bound together arrangement of class, which is a solitary arrangement of classes. The namespace is much the same as a bundle in Java innovation and the class library is much the same as the Java API structure. A namespace comprises of many classes and sub-namespaces. It is sent as a segment class library itself and is sorted out in a component–based chain of importance.

The .NET Framework Class Library (cont.) The root namespace in the class library is System namespace, which contains numerous fundamental classes, for example, Object, Console, and may contain sub-Namespaces, for example, IO, Net, Data, Remoting, and so on. For instance, XML is a sub-Namespace of System namespace which is conveyed as System.XML.dll, ADO.NET is accessible in System.Data.dll which relates to System.Data namespace, and Form based UI classes are accessible in System.Windows.Forms.dll comparing to namespace System.Windows.Forms.

The .NET Framework Class Library (cont.) Developers can make custom namespace and sort out related classes in a custom namespace. A namespace can be conveyed as a get together of paired parts. Same name classes can be set in various namespaces in light of the fact that they are referenced by various namespace prefix. Keeping in mind the end goal to utilize classes in a namespace a mandate utilizing <namespace> in C# or import <namespace> in VB must be incorporated toward the start of code. The framework worked in fundamental class library is conveyed in mscorlib.dll document.

The Component Model of .NET MSIL DLL segments are supplanting COM Components, the MSIL Remoting Channels EXE segments are supplanting DCOM Component, and the Web Service segments are new SOAP segments expected to be cross-stage, and cross-dialect electronic parts. .NET parts are significantly less demanding to create than COM and DCOM. Additionally, the .NET part innovation is brought together dialect arranged. Any .NET part is in the arrangement of pre-ordered MSIL, which can be twofold connected to by some other MSIL segments or some other .NET good customers.

The Component Model of .NET (cont.) The .NET structure itself is developed in a segment show, for instance, System namespace System.Runtime.Remoting is accessible in mscolib.dll and System.XML namespace is accessible in System.XML.dll. A .dll document is a .NET sent part (Assembly). A namespace is much the same as a coherent bundle in Java to sort out related classes together. A get together may have numerous namespaces and one namespace may traverse over different get together record. The subtle elements of .NET get together will be talked about in the accompanying segments.

The Component Model of .NET (cont.) A .NET part is a solitary pre-incorporated and self portrayed MSIL module worked from at least one classes or numerous modules sent in a DLL get together record. A gathering comprises of up to four sections: 1) Manifest (table of information records): name of get together, key data adaptation, solid name, culture information, documents that make up get together, reference depended congregations traded information. 2