Using COM+ Services in .NET

Add new Microsoft .NET components to existing COM and COM+ applications and they will be able to work together; this will help you if you need to develop a .NET application that can do things like participate in transactions, take advantage of role-based security, or interact with a queue. (14 printed pages) Objectives * Learn about using COM+ Services in Microsoft® .NET. * Create a serviced component. * Deploy a serviced component. Assumptions The following should be tr

Creating Office Managed COM Add-Ins

I demonstrated how to use Microsoft® Visual Studio® .NET to create console applications, Windows Forms applications, Web Forms applications, and XML Web services that interact with Microsoft Office. In this month's column, I will show you how to create an Office managed COM add-in using Visual Studio .NET. Before COM add-ins were invented, you could only create Office application-specific add-ins (except Microsoft Outlook® and Microsoft FrontPage®). These application-specific add-ins have

Understanding Enterprise Services (COM+) in .NET

This article requires some familiarity with the Microsoft®.NET Framework and COM+ services. Familiarity with Enterprise Services is not necessary but would be helpful. For a good background on these topics, refer to: Derek Beyer's book, C# COM+ Programming (Professional Mindware, 2001) Tim Ewald's article, COM+ Integration: How .NET Enterprise Services Can Help You Build Distributed Applications Jeffrey Richter's article, Part 2: Microsoft .NET Framework Delivers the Platform for an Int

Using Components in ASP.NET

In any real-world Web-based application, the foremost role of a Developer is to normalize the business logic and encapsulate said logic in business components to extend the capabilities of application as a whole. In classic ASP developers turned to creating COM objects in VisualBasic, Visual C++, or Java to implement their custom business rules. For example, an eCommerce site might have a suite of custom business objects that had methods like CalculateShippingCosts(options, totalWeightOfOrderedG

Decouple Components With LCE

Decoupling subscribers from publishers yields easier long-term maintenance, faster time to market, and more robust applications. Of course, doing this efficiently requires that you be able to add and remove subscribers without changing the publisher's code. I'll explain the publish/subscribe model in detail, then show you how to decouple your own apps in .NET using Loosely Coupled Events (LCE). LCE lets subscribers subscribe to types of events, so when publishers change, subscriber code doesn

Use COM+ Services With .NET Components

Contrary to popular opinion, the .NET Framework doesn't 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'll learn how to create and deploy a serviced component, which is Microsoft's name for a .NET component that uses the COM+ services. Creating a serviced component is simple. Fir

Using Managed Components from Unmanaged Code

Basics of Building .NET applications" (see http://www.15seconds.com/issue/010129.htm), my last article, discussed how to use the legacy code from managed/.NET code. In this article, I will cover how to use managed components from unmanaged code. .NET runtime allows us to use legacy COM code from .NET components. We can call it backward compatibility. In the same way, .NET runtime also provides us forward compatibility, means accessing .NET components from COM components. Download complet

Using COM components in ASP.NET

In today's article I will deal with a topic of interest for most new convertites to ASP.NET: how can I use my own or third party COM components in the ASP.NET environment? The basic problem lies in the fact that ASP.NET is based on the Common Language Runtime, a so called Managed Execution Environment. The code itself then is called Managed Code and the Runtime obtains the information for management of the code out of the Metadata which was generated by the compiler for the description of th

COM Interoperability in .NET

In this article I cover the area Interoperability issues. There is no doubt that with the help of .Net one can create powerful components and Distributed applications than any other language. But we have to think over about the past reusable components, which were created by many languages such as VB etc. Is it the Usage of those past components is end after evolving of .Net? No we can use those components in the .Net and the .Net types in the Classic COM clients. Are there any possibilit

Calling COM Components from .NET Clients

In this document, you'll learn the details of calling COM servers from .NET clients. (14 printed pages) Objectives Understand the concept of Runtime-Callable Wrappers Use TLBIMP to create an Assembly from a COM component Reference a COM component directly from Microsoft® Visual Basic® .NET code Assumptions The following should be true for you to get the most out of this document: You are familiar with Visual Basic programming You are familiar with COM concepts. In particular,

Calling a .NET Component from a COM Component

When a COM client calls a .NET object, the .NET Framework will create a COM callable wrapper (CCW). COM clients use the CCW as a proxy for the managed object. The role of CCW is to marshal calls between managed and unmanaged code and also to manage object identity and object lifetime of the managed objects they wrap. The purpose of this article is to create a demo project to show how to call .NET component from COM client and to implement events raised by the .NET component. The example we cr

Understanding Classic COM Interoperability With .NET Applications

After playing around with the .NET Beta 1 & Beta 2 bits, there's no doubt in most developers' mind that the .NET technology is a powerful way to build components and distributed systems for the enterprise. But then, what about the tons of existing reusable COM components that you've built through the last few years, not to mention all those cups of coffee & sleepless nights. Is it the end of all those components in the .NET world?. Will those components work hand-in-hand with the .NET managed ru

Using Automation Objects in ASP.NET

Sometimes we are tempted to believe that .NET is a cure for all of our development problems and that every technique used in the pre .NET days should be sent to the recycle bin this moment. A technique which suffers greatly from this misunderstanding is ActiveX, also known as (OLE) automation or COM. The CreateObject function creates COM objects and is often used in classical ASP server side scripts to customize Web pages. It has not always led to the best coding practices, but it worked. The AS

Building User Defined Components in ASP.NET

Construction of custom components or user-defined GUI components has been one of the greatest power of Object Oriented Programming (OOP afterwards). In almost all the OOP languages this is possible. VC++ enables this with the help of MFC (Microsoft Foundation Classes), java with JFC/Swing (Java Foundation Classes). Several other applications like Delphi, VB, etc. also achieve this by the magical power of OOPS. GUI programming with windows mainly concentrates on Window based components, which wou

Chunky interfaces for .NET distributed components

A chunky interface may be a new concept to some, but chunkiness is an idea you need to be familiar with if you plan to develop distributed .NET applications anytime soon. In this article, I’ll explain the basic idea behind the term, which flies in the face of traditional object-oriented design doctrine, and clue you in to why chunkiness may be the way to go. advertisement Click Here What is chunky? In basic terms, a chunky interface is one that accomplishes a maximum amount of work wit

Using a transacted C# component

Several people have asked questions like "is COM+ dead", "how does COM+ relate to .NET", etc. The answer is that COM+ is definitely not gone. It remains and will continue to be an important part of the overall programming model, and it can be fully leveraged from ASP.NET and the overall .NET Framework. You can continue to create COM+ components using VS6 and other compilers and then call them from ASP.NET pages. You can also take advantage of COM+ services with new classes built using the .NET F