.NET Interop for Visual FoxPro Applications
This article discusses in detail how to execute code dynamically by creating code and compiling it at runtime. This is a useful feature for extending applications with user extensions or for adding support for advanced templating. The article discusses the process of compiling code and utilizing the new assembly. Also provided are classes that simplify the process and an ASP like script parser that can be plugged into any application with a few lines of code.
.NET Interoperability: .NET <-> Win32
This article uses Delphi for .NET Preview to show how .NET managed code can interoperate with unmanaged Win32 code using the PInvoke and Inverse PInvoke mechanisms. In particular, it focuses on:
- .NET applications using unmanaged Win32 APIs and entry points exported from your own DLLs
- Win32 applications using managed methods exposed from managed .NET assemblies
.NET Interoperability: COM Interop
This article uses Delphi for .NET Preview to show how .NET managed code can interoperate with Win32 COM clients and servers using the COM Interop mechanism. In particular, it focuses on:
- .NET client applications using unmanaged COM objects
- COM client applications using managed .NET objects
Achieving Backward Compatibility with .NET Interop: Excel as Case Study
There is one way to make explicit reference to a particular version of an ActiveX COM component for .NET Interop. The example used here is to make automation of Microsoft Excel backward compatible. Visual Studio will not allow you to reference older versions if Excel 2003 is already installed on your machine--so your program will not work once deployed to other machines that may have prior versions. This article includes a method for building your own Interop DLL for deployment using a command line tool from the .NET SDK.
COM Interoperability in .NET Part 1
In the first part of this series, Arun Ganesh introduces interoperability between the new .NET technologies, and how to use old Win32 API calls in your .NET applications.
COM Interoperability in .NET Part 2
This article elucidates how to build and install-managed code that will be used from COM applications. A classic COM server is activated using the Service Control Manager (SCM).
Interface Component Interoperability
The fundamental concept behind both COM and DCOM is the interface. An interface is an agreement between a client and an object about how they will communicate with each other.
Microsoft .NET/COM Migration and Interoperability
The interoperability features of the Microsoft .NET Framework will enable developers to continue using traditional Active Server Pages, Component Object Model applications, and Microsoft Win32 DLLs, making it easier to choose if and when to migrate existing managed code to .NET.
Real Stories of .NET Interop: C#, VB.NET and VB6
This article attempts to provide a tutorial as well as help with the troubleshooting of your own interop issues. I will describe the issues with using libraries written in C# or VB.NET in your VB6 applications. The reason, this is an issue, is because there is a lot of new code available only in C# or VB.NET that access new functionality of the OS. Or it could simply be the case that there is already existing C# code that's not available as a COM library, that you want to use.
Understanding Classic COM Interoperability With .NET Applications
Ever wondered how all those COM components that you've have written through the years play along with the .NET runtime. If you are a diehard COM developer interested in knowing how Classic COM Components are positioned in the .NET world or how COM aware clients could consume .NET components, read on.
Using Automation (ActiveX/COM) 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 ASP.NET server side controls and the truly object oriented .NET Framework are a huge step forward. A lot of problems COM used to solve are now better in .NET, but that does not mean that COM no longer exists. Some of your existing COM classes work very well, why should you convert them to .NET? That's not what COM promised you! Relax, there are still a lot of things you can do with COM in ASP.NET. In this article I will show you some of the great COM support it has to offer.
Using P/Invoke to Access Win32 APIs
.NET provides access to COM components through its P/Invoke facility. P/Invoke allows developers to invoke native unmanaged methods from managed code. In this article, we will walk through an example of COM interoperability from within C#.
XP, Component Services and .NET
Learn about the changes introduced by COM+, new features included in Windows XP for COM+, and how to use COM+ services from your .NET programs.
Articles
