Component Technology Notes 3

ITT73 COMPONENT TECHNOLOGY
UNIT – III
The Microsoft way-component object model- From COM, COM+, DCOM to .NET
framework- evolution- web services technologies-XML,WSDL,UDDI,SOAP-Common
Language Runtime- .NET framework class library-ADO.NET,ASP.NET
3.1 THE MICROSOFT WAY - COMPONENT OBJECT MODEL
 Component Object Model (COM) is a binary-interface standard for software components

introduced by Microsoft in 1993.
 It is used to enable interprocess communication and dynamic object creation in a large range of
programming languages.
 It is useful in creating binary software components that can act as interface.
 COM objects can be created with a variety of programming languages.
 A common way to depict a COM object is to draw it as a box with plugs as shown in
figure 3.1.
Fig 3.1 Component Object Model
3.1.1 INTERFACES:
1. Query Interface
2. IUnknown
3. IDispatch
Query Interface:
 Query interface takes the name of the interface and checks whether the COM object
supports it.
 If support exists, it returns the corresponding interface reference.
 An error indication is returned if the interface queried for is not supported.
 The supported interfaces are named using Interface Identifiers (IID’s).
Department of Information Technology, SMVEC Page62

IUnknown:
 All COM objects must have an IUnknown interface.

 The identity of the IUnknown interface node can serve as an identity to the entire COM
object.
 IUnknown interface must be shown on top of a COM object’s diagram.
 The three methods supported by IUnknown interface are Query Interface, AddRef and
Release.
 On creation of an object or node, the reference count is initialized to 1 before handing out
a first reference.
 Each time a copy of a reference is created, the count must be incremented (AddRef).
Each time a reference is given up, the count must be decremented (Release).
 As soon as a reference count reaches zero, the COM object has become unreachable and
should therefore self-destruct.
 Reference counting is a form of cooperative garbage collection. As long as all involved
components play by the rules and cooperate, memory will be safely deallocated.
3.1.2 COM OBJECT REUSE:
 COM supports two forms of object composition to enable object reuse.

1. Containment
2. Aggregation
3.1.2.1 Containment:
 Containment is just the simple object composition technique - one object holds an exclusive
reference to another.
 The first object is called as outer object and the second object is called as inner object. If a
request to the outer object needs to be handled by the inner object, the outer object simply
forwards the request to the inner object as in figure 3.2.
 Consider the above example, the outer object’s IStream interface is implemented by
forwarding the calls to methods Read and Write in the inner object.
 Containment suffices to reuse implementations contained in other components.
 Containment is completely transparent to clients of an outer object.
 A client calling an interface function cannot tell if the object providing the interface handles
the call, or the call is forwarded and handled by another object.

Fig 3.2 COM object composition
3.1.2.2 Aggregation:
 The basic idea of aggregation is simple.

 Instead of forwarding requests, an inner object’s interface reference is handed out directly
to an outer object’s client.
Fig 3.3 COM object Aggregation
 Calls on this interface would then go directly to the inner object, saving the cost of
forwarding.

 It is also important to maintain transparency, as a client of the outer object should not
know that a particular interface has been aggregated from an inner object as in figure 3.3.
 Aggregation is suited only for deeply nested constructions. This results in increase of
complexity.
 Aggregation can be put to work where efficient reuse of component functionality is
needed.
3.1.2 INTERFACES AND POLYMORPHISM:
 COM interfaces can be derived from other COM interfaces using (single) interface
inheritance.
 The true nature of polymorphism in COM is the support of sets of interfaces by COM
objects.
 The type of a COM object is the set of interface identifiers of the interfaces it supports. A
subtype is a superset of interfaces.
Categories:
 Categories are defined as sets of interface identifiers.

 A category has its own identifier (CATID), which is a globally unique identifier.
 A COM object can be a member of any number of categories.
 A category specifies which interfaces must be supported, and also which methods in
these interfaces must at least be implemented.
Interfaces and Versioning:
 An IID in COM serves to identify the version of an interface.

 Interfaces are always requested by IID, all participants in a system agree on the version of
an interface.
 A component may choose to implement several versions of an interface, but these are
handled like any other set of different interfaces.
 Using this strategy, a COM-based system can concurrently support the old and the new
while allowing for a gradual migration.
3.1.3 COM OBJECT CREATION AND COM LIBRARY:
 COM defines a procedural library interface to request new object instances based on their
CLSID.
 A CLSID is also a globally unique identifier to identify classes of COM objects.
 The simplest way to create a new COM object is to call CoCreateInstance. (All COM
library procedure names start with Co for COM.).
 This function takes a CLSID and an IID. It then creates a new instance of the specified
class (CLSID) and returns an interface of the requested type (IID).

 An error indication is returned if COM failed to locate or start a server implementing the
requested CLSID, or if the specified class does not support the requested interface.
 When creating a COM object, COM needs to map the given CLSID to an actual
component that contains the requested class.
 COM supports a system registry that specifies which servers are available and which
classes they support.
 Servers can be of one of three different kinds:
1. In-process servers support objects that live in the client’s process.
2. Local servers support objects on the same machine, but in a separate process.
3. Remote servers support objects on a different machine.
 CoCreateInstance consults the registry to locate the server and, unless already active,
loads and starts it.
 For an in-process server, this involves loading and linking a dynamic link library
 (DLL).
 For a local server, a separate executable (EXE) is loaded.
 Finally, for a remote machine, the service control manager on the remote machine is
contacted to load and start the required server on that machine.
3.2 DISTRIBUTED COMPONENT OBJECT MODEL (DCOM)

3.2.1 OVERVIEW OF DCOM:
 In the last two decades large number of changes took place in object oriented and
distributed component oriented paradigm.
 To satisfy this demand, Microsoft developed the Distributed Component Object Model
(DCOM).
 Both object and component paradigm consists of various issues.
 Interoperability
 Versioning
 Language independence
 Size and complexity of the system.
The development of DCOM began with introduction of the concept Graphical User Interface.
3.2.2 DYNAMIC DATA EXCHANGE:
 The DDE was designed for Microsoft Windows to allow applications to exchange data of
any particular type.
 As DDE protocol is very complex and was interpreted by many software vendors,
Dynamic Data Exchange Management Library (DDEML) was created.

 This library simplified the interfacing with the DDE protocol as well as provided a
common interface for all developers.
3.2.3 DCOM ARCHITECTURE:
 The DCOM architecture is designed for promoting software interoperability.
 The architecture supports a “software bus” on which reusable software components can
be used and integrated with one another seamlessly.
 In order to provide support for this reusable software components the entire object model
is based on an object based programming model.
 The object model was selected because of its inability to provide inheritance.
 This means that the architecture is capable of avoiding te fragile base class syndrome
which exists in other models.
 The fragile base class syndrome appears when one class inherits the members and
behavior of another class.
 The class which provides the behavior and member functions are known as the base class
while the other class is known as the derived class.
 If the member and functionality of the base class changes then the behavior and member
functions of the derived class also changes.
 Changes like this result in having to modify the base class which in turn requires the
compilation of all dependent classes.
 The DCOM architecture 3.4 possesses a unique infrastructure as it supports persistent

storage.
Fig 3.4 architecture of DCOM

3.2.4 FROM COM TO DCOM:
 Distributed COM transparently expands the concepts and services of COM.
 DCOM builds on the client-side proxy objects and the server-side stub objects already
present in COM, to support inter-process communication.
 For the communication between processes within a single machine, proxies and stubs
merely need to map all simple data types to and from streams of bytes.
 As the sending and receiving processes execute on the same machine, there is no need to
worry about how data types are represented.
 An interface reference sent across process boundaries needs to be mapped to an object

reference that retains meaning across process boundaries.
 When receiving such an object reference, COM needs to make sure that a corresponding
proxy object exists on the receiving end as in figure 3.5.
Fig 3.5 services of COM
 A client issuing a call on object A. The called method takes a single parameter, referring
to an interface of object B.

 As object A is in another process, a local proxy object mediates the call. The proxy
determines an object identifier (OID) for object B and an interface pointer identifier
(IPID) for the particular interface being passed.
 The OID and the IPID are sent together with the client process’s ID to a stub in the server
process. The stub uses the OID to locate the local proxy for object B and the IPID to
locate the particular interface.
 The stub then issues the original call, on behalf of the client. It passes the interface reference
of the local B proxy to object A, the receiver of the call.
3.2.5 DCOM STYLE:

 To deal with differences in data representations, DCOM marshal’s data into a representation
called network data representation (NDR), a platform-independent format.
 To form machine-independent object references, DCOM combines the OID and IPID
with information that suffices to locate an object exporter.
 An object exporter is an object provided by DCOM that knows how to bind the objects
exported by a server. Each object exporter has a unique ID (OXID), and this OXID is
included in an object reference.
 If the object exporter has been contacted recently, the OXID is known locally, together with
contact information of the remote machine.
 This caching mechanism speeds up the resolution of object references, even in the
presence of large numbers of objects.
 If the object exporter referred to in an object reference is seen the first time, a final field
of the object reference is consulted. This field contains the symbolic information (a URL-
like stringbinding) needed to contact the OXID resolver object on the remote machine.
 The remote OXID resolver is contacted and the contact information for the remote object
exporter with the given OXID is retrieved.
3.3 COM+
 COM+, an extension of COM, was first released in mid-2000.

 COM+ integrates COM with technologies such as transactional processing, asynchronous
messaging, load balancing, and clustering.
 The most prominent predecessor products were the Microsoft Transaction Server (MTS)
and the Microsoft Message Queue server (MSMQ).

 MTS separates declarative attributesabout infrastructure requirements from the code of

components and applications.
 COM+ provides an attribution model that allows for the automatic mapping between
procedural invocations and message queuing.
 A component can be marked as communicating via messages and the methods on all the
component’s interfaces can be restricted to one-way semantics.
 The COM+ context wraps such a component’s instances with special proxies that accept
incoming messages from MSMQ queues and send outgoing messages to MSMQ queues.
3.4 .NET FRAMEWORK
 .NET is a framework for developing web-based and windows-based applications within

the Microsoft environment.
 The .NET Framework is a software framework developed by Microsoft that runs
primarily on Microsoft Windows.
 It includes a large library and provides language interoperability (each language can use
code written in other languages) across several programming languages.
VB VC++ VC# JScript
COMMON LANGUAGE SPECIFICATION (CLS)
ASP.NET WEB SERVICES AND WEB WINDOWS

FORMS FORMS VISUAL
ADO.NET DATA AND XML STUDIO.NET
BASE CLASS LIBRARY
COMMON LANGUGE RUNTIME (CLR)
Fig 3.6 framework of .net
 Programs written for the .NET Framework in figure 3.6 execute in a software
environment , known as the Common Language Runtime (CLR), an application virtual
machine that provides services such as security, memory management, and exception
handling. The class library and the CLR together constitute the .NET Framework.

 Presently, Microsoft supports four languages: C#, JScript, Managed C++, and Visual
Basic.NET.
 .NET framework moves application development from client-centric to server-centric.
 .NET framework consists of
1. Common Language Runtime(CLR)
2. Windows Forms
3. ASP.NET
Web Forms
Web Services
4. ADO.NET
5. Visual Studio.NET
 .NET is not a language but it is runtime and a library for writing and executing programs
in any compliant language.
 The .NET Framework's Base Class Library provides user interface, data access, database
connectivity, cryptography, web application development, numeric algorithms, and
network communications.
 Programmers produce software by combining their own source code with the .NET
Framework and other libraries.
3.4.1 COMMON LANGUAGE RUNTIME:

 CLR works like a virtual machine in executing all languages.
 All .NET languages must obey the rules and standards imposed by CLR. Examples:
– Object declaration, creation and use
– Data types,language libraries
– Error and exception handling
– Interactive Development Environment (IDE)
 CLR is an implementation of the common language infrastructure(CLI) Specification.
 CLR offers
1. Dynamic loading and unloading
2. Garbage collection
3. Context interception
4. Metadata reflection
5. Remoting
6. Persistence
7. Other runtime services that are fully language independent
 CTS is a rich type system built into the CLR
a. Implements various types (int, double, etc)
b. And operations on those types
 CLS is a set of specifications that language and library designers need to follow.This will
ensure interoperability between languages

3.4.2 INTERMEDIATE LANGUAGE:
 .NET languages are not compiled to machine code. They are compiled to an Intermediate
Language called as Microsoft Intermediate Language (MSIL).
 CLR accepts the IL code and recompiles to machine code. The recompilation is Just-in-
Time (JIT) meaning it is done as soon as a function or subroutine is called.
 The JIT code stays in memory for subsequent calls. In cases where there is not enough
memory it is discarded.
3.4.3 COMPILATION IN DOT NET
CODE IN VB.NET CODE IN C# CODE IN JSCRIPT
VB.NET COMPILER C# COMPILER JAVA COMPILER
MICROSOFT INTERMEDIATE LANGUAGE
CLR JUST-IN-TIME COMPILATION
Fig 3.7 compilation in .net
3.5 COMMON LANGUAGE INFRASTRUCTURE:
 The common language infrastructure (CLI) specification establishes a language-neutral platform

for .NET framework.
 The purpose of the Common Language Infrastructure (CLI) is to provide a language-neutral
platform for application development and execution, including functions for exception
handling, garbage collection, security, and interoperability as in figure 3.8.
 By implementing the core aspects of the .NET Framework within the scope of the CLI
 This functionality will not be tied to a single language but will be available across the many
languages supported by the framework. Microsoft's implementation of the CLI is called the
Common Language Runtime, or CLR.
 CLI comprises the following specifications:

1. Execution engine services (such as loader,JIT compiler, and garbage-collecting

memory manager)
2. The Common Type System (CTS)
3. Common Language Specification (CLS)
 The CTS scope is the superset of many languages’ core concepts in the type space.
 For code implemented in different languages to interoperate, the CLS space is useful.
 CLS is a strict CTS subset that is constructed in such a way that a wide variety of languages
can cover it completely.
 CTS defines a single root type – System.Object – for all types.
 Reference types are split into interfaces, classes, arrays, and delegates.
 Classes are split into marshal-by-value and marshal-by-reference; marshal-by-reference is
further split into context agile and context bound.
 Traditional web servers that serve web pages for consumption by people. Web services offer
computational services to other systems.
 For example, an online bookstore could offer its database as a web service in such a way that
other services can build on it.
 Web services as in figure 3.9 describes a standardized way of integrating web-based
applications using :
1. WSDL
2. UDDI
3. SOAP
 WSDL XML web services provide a way to describe their interfaces in detail to allow a user
to build a client application.
 UDDI XML web services are registered so that potential users can find them easily.
 SOAP XML web services expose useful functionality to web users through this standard
web protocol.

Fig 3.8 common language infrastructure
3.6 XML WEB SERVICES
UNIVERSAL DISCOVERY
DESCRIPTION AND INTEGRATION
(UDDI)
WSDL WSDL
SERVICE REQUESTER SERVICE PROVIDER

SOAP
Fig 3.9 XML web services
3.7 WSDL
 WSDL stands for Web Services Description Language.

 WSDL is an XML based language for locating and describing web services.

 WSDL file is an XML document that describes a set of SOAP messages and how the
messages are exchanged.
 This file uses XML schema standard to describe message formats.
 In describing message contents, WSDL defines where the service is available and what
communication protocol is used to talk to the service.
 There are several tools available to read a WSDL file and generate the code required to
communicate with an XML web service.
3.8 UDDI
 UDDI stands for Universal Description, Discovery and Integration.
 It is an XML based standard for describing, publishing and finding web services.
 UDDI is a specification for a distributed registry of web services.
 UDDI is platform independent, open framework.
 It can communicate via SOAP, CORBA, Java RMI protocol.
 UDDI uses WSDL to describe interfaces to web services.
 UDDI registries are available on the internet. Companies or industry groups may choose to
implement their own private UDDI registries.
 Three types of information can be registered into an UDDI registry:
 White pages – describes the company offering the service (name, address, contacts).
 Yellow pages – include industrial categories.
 Green pages – describes the interface to the service in detail to write an application.
3.9 SOAP
 Simple Object Access Protocol (SOAP).
 SOAP is a successor of XML-RPC.
 SOAP is a proposal for an XML-based standard that enables invocations on remote objects,
typically using HTTP.
 It is a light weight protocol for exchange of messages in a distribute environment.
 The SOAP standard provides standard ways to:
Describe the addressee of an invocation;
Encode a wide range of typical programming data types into invocation messages;
Defines what parts of a message must be understood or can be ignored.
 A SOAP message contains the following elements as in figure 3.10:
An Envelope element that identifies the XML document as a SOAP message.
A Header element that contains the header information.
A Body element that contains the call and response information.
A Fault element that contains the error and status information.
 The SOAP standard defines namespaces for,
SOAP envelopes - (schemas.xmlsoap.org/soap/envelope/).
SOAP encoding - (schemas.xmlsoap.org/soap/encoding/).

 SOAP messages must use these envelope and encoding namespaces.
SOAP STRUCTURE:
SOAP – ENV : ENVELOPE
SOAP – ENV : HEADER
SOAP – ENV: BODY
Fig 3.10 structure of SOAP
SKELETON SOAP MESSAGE:
<?xml version = “1.0”?>
<soap:Envelope
Xmlns:soap=http://www.w3.org/2001/12/soap-envelope
Soap encodingStyle=http://www.w3.org/2001/12/soap-encoding>
<soap:Header>
…….
</soap:Header>
<soap:Body>
………
<soap:Fault>
………
</soap:Fault>
</soap:Body>

</soap:Envelope>
ADVANTAGES:
 Soap uses HTTP which is widely used and scalable.

 Wide remote system interoperability.
3.10 DOT NET FRAMEWORK CLASS LIBRARY

 The .NET framework class library provides the core functionality of .NET framework
architecture.
SYSTEM.WEB SYSTEM.WINDOWS.FORMS
DESCRIPTION HTML CONTROLS DESIGN COMPONENT

MODEL
DISCOVERY
WEB CONTROLS SYSTEM.DRAWING
PROTOCOLS
DRAWING 2D PRINTING
CACHING SECURITY
IMAGING TEXT
CONFIGURATION SESSION STATE
SYSTEM.DATA SYSTEM.XML
OLEDB SQL CLIENT XSLT SERIALIZATION
COMMON SQL TYPES XPATH
COLLECTIONS IO SECURITY RUNTIME
CONFIGURATION NET SERVICE PROCESS INTEROPSERVICES
DIAGONISTICS REFLECTION TEXT REMOTING
GLOBALIZATION RESOURCES THREADING SERIALIZATION

Fig 3.11 .net framework class library
EROPSERVICES
 The organization of the class library is similar to the file system. Each folder is a Namespace.
 Each file is an assembly exposing one or more types.
 The root of the class library is the System Namespace.
 Traditional libraries are language independent, operating systems independent, and contain
simple subroutine calls.
 In .NET all services fall into a single, hierarchy organized, language independent class
library.
 It includes a huge collection of reusable classes, interfaces, and value types that optimize the
development process and provide access to system functionality.
 The class library contains 25 second level namespaces that in turn contains thousands of
types exposing all services of the operating system.
 All components developed by the users must be added to the class library before they can be
used.
NAMING CONVENTIONS:
 .NET framework uses a dot syntax naming scheme that describes a hierarchy.
 First part of the full name upto the right most dot is the namespace name. The last part of the
name is the type name.
 Example: System.Collections.ArrayList
 Naming scheme makes it easy for library developers extending the .NET framework.
 Classes are accessed by namespaces, which resides within assemblies.
System.Object:
 System.object is the base class for each and every type.

 Inheritance from System.object is implicit.
o System.Object.Equals(object o)
Test if two types are equal
o System.Object.ReferenceEquals(object o)
Test if two references are two the same object.
o System.Object.Finalize()
Called when object is garbage collected.
3.11 ADO.NET
ADO.NET is a set of computer software components that programmers can use to access data and
data services based on disconnected DataSets and XML. It is a part of the base class library that is
included with the Microsoft .NET Framework.It is commonly used by programmers to access and
modify data stored in relational database systems.
 ADO.NET provides consistent access to data sources such as SQL Server and XML, and
to data sources exposed through OLE DB and ODBC. Data-sharing consumer applications
can use ADO.NET to connect to these data sources and retrieve, handle, and update the
data that they contain.
 ADO.NET separates data access from data manipulation into discrete components that can
be used separately.

 ADO.NET includes .NET Framework data providers for connecting to a database,

executing commands, and retrieving results.
 Those results are either processed directly, placed in an ADO.NET Data Set object in order
to be exposed to the user in an ad hoc manner, combined with data from multiple sources,
or passed between tiers.
Fig 3.12 .net 3.0 stack
 The dataSetobject can also be used independently of a .NET Framework data provider to
manage data local to the application or sourced from XML.
 The ADO.NET classes are found in System.Data.dll, and are integrated with the XML
classes found in System.Xml.dll.
 ADO.NET provides the most direct method of data access within the .NET Framework.
3.12 ASP.NET
 ASP.NET is a server-sideweb application framework designed for Web development to

produce dynamic Web pages. It was developed by Microsoft to allow programmers to build
dynamic web sites, web applications and web services.ASP.NET is a development
framework for building web pages and web sites with HTML, CSS, JavaScript and server
scripting.
 .NET Framework is the successor to Microsoft's Active Server Pages (ASP) technology.
ASP.NET is built on the Common Language Runtime (CLR), allowing programmers to write
ASP.NET code using any supported .NET language.

 ASP.NET Web pages, known officially as Web Formsare the main building blocks for
application development. Web forms are contained in files with a ".aspx" extension; these
files typically contain static (X)HTML markup, as well as markup defining server-side web
Controls and User Controls for the Web page.
 ASP.NET uses a visited composites rendering technique. During compilation, the template
(.aspx) file is compiled into initialization code which builds a control tree (the composite)
representing the original template.
 The initialization code is combined with user-written code (usually by the assembly of multiple
partial classes) and results in a class specific for the page. The page doubles as the root of the
control tree.
 Actual requests for the page are processed through a number of steps. First, during the
initialization steps, an instance of the page class is created and the initialization code is
executed. This produces the initial control tree which is now typically manipulated by the
methods of the page in the following steps.
 As each node in the tree is a control represented as an instance of a class, the code may
change the tree structure as well as manipulate the properties/methods of the individual
nodes. Finally, during the rendering step a visitor is used to visit every node in the tree,
asking each node to render itself using the methods of the visitor. The resulting HTML
output is sent to the client.
 After the request has been processed, the instance of the page class is discarded and with it
the entire control tree. This is a source of confusion among novice ASP.NET programmers who
rely on the class instance members that are lost with every page request/response cycle.
TWO MARKS
1) Write about COM.

 Component Object Model (COM) is a binary-interface standard for software components
introduced by Microsoft in 1993.
 It is used to enable inter process communication and dynamic object creation in a large
range of programming languages
2) What is the use of COM?

COM is used in applications such as the Microsoft Office Family of products.
For example COM OLE technology allows Word documents to dynamically link to data
in Excel spreadsheets.
COM Automation allows users to build scripts in their applications to perform repetitive
tasks or control one application from another.
3) Define DCOM.

DCOM is the abbreviation for Distributed Component Object Model.

It is an extension of Component Object Model protocol (COM). DCOM was first
introduced by Microsoft in 1996, shortly after COM was introduced.
DCOM allows an application to be built from many COM objects that reside in different
machines.
4) What are the advantages of DCOM?

Speeding up development processes.
Improving deployment facility.
Lowering maintenance costs.
Improving scalability.
Load balancing.
5) Compare COM and DCOM.

COM DCOM
1. COM is a local component 1. DCOM is a distributed component
object model on one single object model working across several
machine. machines.
2. Com is used for Desktop 2. Dcom is used for distributed
Applications environment.
3. COM is collection of tools 3. DCOM is a Distributed component
which are executed on client object Model runs at the given server.
side environment
6) Write about .NET components.

.Net Language (C#,J#,VB.Net)
JIT(Just In Time Compiler)
Common Language Intermediate(CLI)
.Net framework(Console,ADO.Net,ASP.Net)
Common Language Runtime(CLR)
7) COM objects reuse.

Since DCOM is built on top of COM, all COM-compliant objects are automatically
supported by DCOM.
Organizations will be able to reuse their existing COM objects, reducing the cost of
developing new distributed applications.
Developers will be able to find an existing component to use with their distributed
applications

8) Write about WSDL.

Web Services Description Language (WSDL).
It is a proposed standard for describing the web services at meta level.
WSDL builds on XML and defines an extensible framework to describe web services.
Other two proposals of same functionality are:
 IBM’s WSFL(Web Service Flow Language)
 Microsoft’s XLANG
9) What is UDDI?
Universal Description, Discovery and Integration (UDDI).
UDDI is also a regular web service , it serves as a directory of web services.
With the help of UDDI it is easy to find a web service from a group of web services of
same kind.
10) Write about SOAP.

Simple Object Access Protocol(SOAP)
SOAP is a proposal for an XML-based standard that enables invocations on remote
objects by using HTTP.
It provides standard ways to:
 Describe the address of invocation.
 Encode a wide range of typical programming data types into invocation messages.
 Defines what parts of a message must be understood or can be ignored.
11) What is CLR?

Common Language Runtime (CLR).
CLR is a part of Microsoft .NET Framework.
This is the implementation part of Common Language Specification (CLI), which
establishes the language-neutral platform to .NET applications.
The main aim is to convert the source code into managed code (0’s and 1’s).
12) What is CLR context?

The CLR context infrastructure is probably the first mainstream attempt to provide a genuinely
extensible infrastructure for contextual composition.
13) What are the flavors in CLR objects?

Value types
Pass-by-value type
Pass-by-reference type

Context-bound type
14) Explain ADO.NET.

Visual Studio .NET provides access to databases through the set of tools and namespaces
collectively referred to as ADO.NET
Data access in ADO.NET is standardized to be independent of the data sources.
Four layers to data access are:
 Data store
 Data provider
 Data set
 Data view
15) Explain ASP.NET.

Active Server Pages(ASP.NET)
ASP.NET is a programming framework to create web applications.
These applications are accessible on a global basis leading to efficient information
management.

Component Technology Notes 3

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Component Technology Notes 3

Hochgeladen von

Copyright:

Verfügbare Formate

ITT73 COMPONENT TECHNOLOGY

3.1 THE MICROSOFT WAY - COMPONENT OBJECT MODEL

 Component Object Model (COM) is a binary-interface standard for software components

Fig 3.1 Component Object Model

Department of Information Technology, SMVEC Page62

 All COM objects must have an IUnknown interface.

3.1.2 COM OBJECT REUSE:

 COM supports two forms of object composition to enable object reuse.

Department of Information Technology, SMVEC Page63

Fig 3.2 COM object composition

 The basic idea of aggregation is simple.

Fig 3.3 COM object Aggregation

Department of Information Technology, SMVEC Page64

3.1.2 INTERFACES AND POLYMORPHISM:

 Categories are defined as sets of interface identifiers.

 An IID in COM serves to identify the version of an interface.

3.1.3 COM OBJECT CREATION AND COM LIBRARY:

Department of Information Technology, SMVEC Page65

3.2 DISTRIBUTED COMPONENT OBJECT MODEL (DCOM)

3.2.2 DYNAMIC DATA EXCHANGE:

Department of Information Technology, SMVEC Page66

3.2.3 DCOM ARCHITECTURE:

 The DCOM architecture is designed for promoting software interoperability.

 The DCOM architecture 3.4 possesses a unique infrastructure as it supports persistent

Fig 3.4 architecture of DCOM

Department of Information Technology, SMVEC Page67

3.2.4 FROM COM TO DCOM:

 Distributed COM transparently expands the concepts and services of COM.

 An interface reference sent across process boundaries needs to be mapped to an object

Fig 3.5 services of COM

Department of Information Technology, SMVEC Page68

3.2.5 DCOM STYLE:

 COM+, an extension of COM, was first released in mid-2000.

Department of Information Technology, SMVEC Page69

 MTS separates declarative attributesabout infrastructure requirements from the code of

3.4 .NET FRAMEWORK

 .NET is a framework for developing web-based and windows-based applications within

VB VC++ VC# JScript

COMMON LANGUAGE SPECIFICATION (CLS)

ASP.NET WEB SERVICES AND WEB WINDOWS

ADO.NET DATA AND XML STUDIO.NET

BASE CLASS LIBRARY

COMMON LANGUGE RUNTIME (CLR)

Fig 3.6 framework of .net

Department of Information Technology, SMVEC Page70

3.4.1 COMMON LANGUAGE RUNTIME:

Department of Information Technology, SMVEC Page71

3.4.2 INTERMEDIATE LANGUAGE:

3.4.3 COMPILATION IN DOT NET

CODE IN VB.NET CODE IN C# CODE IN JSCRIPT

VB.NET COMPILER C# COMPILER JAVA COMPILER

MICROSOFT INTERMEDIATE LANGUAGE

CLR JUST-IN-TIME COMPILATION

Fig 3.7 compilation in .net

3.5 COMMON LANGUAGE INFRASTRUCTURE:

 The common language infrastructure (CLI) specification establishes a language-neutral platform

Department of Information Technology, SMVEC Page72

1. Execution engine services (such as loader,JIT compiler, and garbage-collecting

Department of Information Technology, SMVEC Page73

Fig 3.8 common language infrastructure

3.6 XML WEB SERVICES

SERVICE REQUESTER SERVICE PROVIDER

Fig 3.9 XML web services

 WSDL stands for Web Services Description Language.