2002Apress eBooksRequires access

Building Serviced Components (COM+ Interop)

Andrew Troelsen

Open publisher page 0 citations

Abstract

The .NET platform provides a specific assembly, System. EnterpriseServices.dll, which allows you to build managed code libraries that can leverage the services provided by the COM+ runtime. Thus, using C#, VB.NET, or any other managed language, you are able to build types that can support the same behaviors (for example, automated transactions, JITA, role-based security, and whatnot) as a classic COM+ type. The point of this chapter is to provide an overview of the key features of COM+, as well as to dig into the details of building configured components under the.NET platform. As you will see, building COM+-aware.NET types is similar to the process of exposing .NET types to a classic COM client (as described in Chapters 10 through 12). These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

About this research paper

What this paper is about

The .NET platform provides a specific assembly, System. EnterpriseServices.dll, which allows you to build managed code libraries that can leverage the services provided by the COM+ runtime. Thus, using C#, VB.NET, or any other managed language, you are able to build types that can support the same behaviors (for example, automated transactions, JITA, role-based security, and whatnot) as a classic COM+ type. The point of this chapter is to provide an overview of the key features of COM+, as well as to dig into the details of building configured components under the.NET platform. As you will see, building COM+-aware.NET types is similar to the process of exposing .NET types to a classic COM client (as described in Chapters 10 through 12). These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Why it matters

A significance statement is not available in the OpenAlex record.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

The .NET platform provides a specific assembly, System. EnterpriseServices.dll, which allows you to build managed code libraries that can leverage the services provided by the COM+ runtime. Thus, using C#, VB.NET, or any other managed language, you are able to build types that can support the same behaviors (for example, automated transactions, JITA, role-based security, and whatnot) as a classic COM+ type. The point of this chapter is to provide an overview of the key features of COM+, as well as to dig into the details of building configured components under the.NET platform. As you will see, building COM+-aware.NET types is similar to the process of exposing .NET types to a classic COM client (as described in Chapters 10 through 12). These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Key concepts: Computer science, Net (polyhedron), Leverage (statistics), .NET Framework, Key (lock), Process (computing), Point (geometry), Operating system

Related papers

Back to paper searchBrowse research topicsOriginal source
Building Serviced Components (COM+ Interop) — Research Paper | ScholarLens