Why Do We Need Component Services?
COM+ brings an experience to design and developing enterprise applications and making life trouble-free for software designer and developers. Users can now concentrate on developing business sense with simplicity, while being secured from the basic aspects of enterprise application development from beginning to end the use of COM+ components.
Once more, COM+ designed to make it simple to design and develop enterprise-class distributed applications. However, we should decide about what is really an enterprise-class mean. An enterprise-class distributed application is timely implementation and correct application processes also doing critical operation of some business. Additionally, this type application can use with many different user types such as clients, employers, operators etc. All enterprise-class application should be relational with internet/intranet, multi-tier networking with security capabilities. As well, one of Microsoft's goals in developing COM+ has been to offer companies the benefits of multi-tier applications while hiding as much of the inherent complexity as possible. More than the last decade, Microsoft has made many advances in creating this infrastructure for distributed applications. Opposing to common opinion, the .NET Framework does not replace COM+. You still need COM+ services—such as distributed transactions, object pooling, Just-In-Time Activation (JITA), synchronization, and queued components—to build enterprise-class, distributed applications on the Windows platform. In this article, you will learn how to create and deploy a serviced component, which is Microsoft's name for a .NET component that uses the COM+ services.
What is a Component Services?
You must recognize component services are COM+ in Microsoft XP and 2000 Operating Systems; it is the new step in the evolution of the Microsoft Component Object Model with Microsoft Transaction Server (MTS). COM+ handles many of the resource management responsibilities you until that time had to program yourself, such as thread security and allocation. It automatically makes your applications more scalable by providing thread pooling, object pooling, and just-in-time object activation. COM+ also protects the integrity of your data by providing transaction support, even if a transaction spans multiple databases over a network.
Like applications, components as a part of application need a runtime service to work. Briefly, the services, which support COM and .NET components under Windows 2000 and XP, are COM+ Component Services. COM+ is the fundamental COM and a set of additional services such as Transactions, Queued Components (QC), Security, Loosely Coupled Events (LCE), Just-In-Time Activation (JITA), Basic Interception Services, Object Pooling, Deployment, and Administration. The COM enhancements include improvements in both threading and security, along with the introduction of Asynchronous COM. The new services include synchronization, object pooling, and queued components, as well as a new distributed application administration and packaging service (Component Services). For those usual with COM programming, the COM+ improvements are significant. COM+ implements a new threading model called neutral apartment threading, which allows a component to have serialized access but also execute on any thread. In addition to the threading model, COM+ provides role-based security, asynchronous object execution, and a new built-in moniker that represents a reference to an object instance running on an out-of-process server.
Tools to Create a Component Service
Visual Studio .NET has a magnificent tool set for create a component service in XP. Visual Studio .NET and the individual tools and languages it contains are the foundation for building Windows-based components and applications, creating scripts, developing Web sites and applications, and managing source code. Most important ones are C# and VisualBasic.NET. In addition, Visual C++ 7 is an excellent tool for create a component service. Recall that COM+ is a binary standard for building and integrating software components. All languages are tools, which you used them for create component service in .NET environment. When Microsoft developed COM+, it was intended and targeted mainly for Microsoft Visual C++ and Visual Basic developers. Furthermore, Microsoft designed COM+ to manage and deploy applications. In addition to that, in .NET environment you can use some other programming languages and tools such as COBOL, Perl, J#, C# to develop a component services. Visual Studio.NET supports many languages additional to its official languages C#, C++ and VisualBasic.NET. Our main tools will be Visual Studio.NET and Visual C++ 7.0 compiler in this article.
Comments