Updated: July 12, 2020 (September 23, 2002)

  Sidebar

Windows .NET Server Component Concepts

My Atlas / Sidebar

821 wordsTime to read: 5 min
Rob Helm by
Rob Helm

As managing vice president, Rob Helm covers Microsoft collaboration and content management. His 25-plus years of experience analyzing Microsoft’s technology... more

COM+ and Microsoft Message Queuing (MSMQ) are Windows services that help develop and manage middle-tier components—blocks of application code that enforce business rules and carry out data access functions (e.g., the component that manages shopping carts in a consumer e-commerce application). Explained below are some important concepts for understanding these services in Windows .NET Server.

Component Models and Types

Components are created with a component model, software that enables applications to send requests to a component and receive its responses over a network, and takes care of activating components (loading them into memory and starting their execution) and deactivating them when they are no longer needed.

Windows .NET Server actually supports three distinct component types and corresponding component models:

Unmanaged components created with the Component Object Model (COM), which was introduced with OLE 2.0 in 1995

Managed components created with unnamed component model implemented by the Common Language Runtime (CLR), which was introduced in 2002 as part of the .NET Framework.

Atlas Members have full access

Get access to this and thousands of other unbiased analyses, roadmaps, decision kits, infographics, reference guides, and more, all included with membership. Comprehensive access to the most in-depth and unbiased expertise for Microsoft enterprise decision-making is waiting.

Membership Options

Already have an account? Login Now