COM Interop
COM Interop in .NET Framework CLR enables COM objects to interact with .NET objects, and vice versa. Here you may find COM Interop related articles and news.

RECENT POSTS

  • ValidationScriptGenerator

    This article gives you a solution for generating a client side validation script in a component model that you can reuse in an ASP.NET project.
  • Mapping Microsoft Excel columns with XML data (XML data integration) programmatically using a .Ne...

    Using this program you can map Excel columns programmatically and generate an XML file containing the cell values that you had in your Excel document. After generating the XML file we can read it into a dataset.
  • DTS Custom Task in C#

    During last year I wrote an article about DTS and how to use it in C#. In that article I stated that I didn’t manage to solve the problem related to CustomTask. Today I finally forced myself to tackle that problem again and here is the result. Writing simple CustomTask in C# is the easiest part.
  • COM Interoperability Part 1: Using COM Components in .NET Framework

    In this article we review the concepts & walk-through an example that demonstrates COM interoperability in .NET framework.
  • Platform Invocation Services in .NET Framework

    This article will cover the details of Platform Invocation Services provided in .Net Framework. Platform Invoke Services acts as a bridge between the managed and unmanaged code. This service enables managed code to call unmanaged functions which are being exposed by any dynamic link libraries (DLL’s) such as Win32 API’s or any custom DLLs.
  • Deploying a COM Component from C#

    Here is some code to help you to deploy a COM component from C#. I needed to programmatically deploy a project that would be registered as COM object (not COM+) and be installed into GAC. The following two classes will help in this objective.
  • .NET COM Interoperability - Part 2: Using .NET Component from COM

    When a COM client calls a DotNet object, the DotNet framework will create a COM callable wrapper (CCW). COM clients use the CCW as a proxy for the managed object.
  • .NET COM Interoperability - Part 1: Using COM Components from .NET Framework

    The DotNet framework exposes COM objects through a proxy called the runtime callable wrapper (RCW). The primary function of RCW is to marshal call between a managed client (.Net) and unmanaged COM object. The runtime maintains a single RCW for each COM object.
  • Creating an Excel Spreadsheet Programmatically

    The Interoperability services make it very easy to work with COM Capable Applications such as Word and Excel. This article reveals using Excel from a managed application. Excel is the spreadsheet component of Microsoft Office 2000.
  • C# and ActiveX DLL

    As you know with Visual Basic 6.0, it is possible develop a COM server and implement them in a Visual Basic client program. But this is being done by using Visual Basic. You may wonder about the idea of calling this DLL in a C# Application. Well, C# language provides us a way to call this COM server in a program. When we compile a C# program an Intermediate Language is generated and it is called as Managed Code.
  • XP, Component Services and .NET

    First of all, COM+ does revolutionize COM; it is not only a superior new version of the COM programming model it is also a new platform to design and develop components. In addition, COM+ Services in XP does have some differences from Windows 2000; also XP and COM+ 1.5 offer a richer set of services than was available in COM+ 1.0. This article will describe the basic component services on the XP.
  • An insight into Code Reusability and COM Interoperability - Part 2

    We have mushrooms of network systems running across the globe based on many proprietary protocols. In order to integrate these systems to communicate with each other in a more meaningful way, developers or organizations have to face an uphill task.
  • Language Independence from COM to .NET

    This article covers the subject regarding Language Independence. This term Language Independent means one can create an application using various languages. This Language independent starts from past COM (OLE & ActiveX) to present .Net.Let us see in detail.
  • Com and Component creation in C#

    Component is nothing but the reusable piece of software in binary form that can be plugged into other components from other vendors.
  • Accessing COM+ component using C#

    This tutorial explains step by step of accessing COM+ application using C#.
  • Using C# and COM Interoperability to Extract from a UML tool into a Microsoft Word Document

    This article allows you to read the classes contained inside of WithClass 2000 into a Word Document using COM Interoperability for Word and COM Interoperability for WithClass and presents your classes in a kind of report.
  • Using ADO RecordSet in ADO.NET

    Using ADO recordset in managed code using ADO.NET data providers is pretty simple. Visual studio .NET provides you to add reference to the COM libraries. In this article I'll show you how to access data using ADO recordset and fill a ADO.NET data provider from the recordset data.
  • Platform Invoke Sample - Changing the Desktop Wallpaper

    In this example we will see how to change the Desktop wallpaper by invoking a Windows API function from C#. The Platform Invoke mechanism allows you to access unmanaged functions implemented in dlls.
  • Web services with Language Interoperability

    A web service in general is a way of exposing the properties and methods through the Internet In other words, it's an URL-addressable resource that programmatically returns information to clients who want to use it.
  • Import data from Excel to Access using ADO.net

    Data interoperability with Microsoft office applications has become easier with ADO.net.
  • Describing COM (Component Object Model)

    Component Object Model (COM) is a method to facilitate communication between different applications and languages.
  • .NET Interoperability at a Glance 3 - Unmanaged Code Interoperation

    This is the last article in this series, it talks about unmanaged code interoperation; that’s, interop between .NET code and other code from other technologies (like Windows API, native libraries, COM, ActiveX, etc.)Be prepared!
  • Creating COM components in .NET

    In this blog I create a COM application for Amazon Marketplace Web Services (Amazon MWS).
  • Split worksheets to individual Excel files using Interop

    In this Blog you will see Split worksheets to individual Excel files using Interop.
  • COM+ Installation at runtime

    This blog shows on how to do a COM+ Installation at runtime.