February 2007
Revised August 2007Applies to:
Microsoft .NET Framework 3.0
Windows Vista
Microsoft Internet Information Services
Microsoft Visual Studio 2005Summary: This article will detail step by step instructions to consume COM+ application services from WCF clients. We will also discuss how legacy applications can use applications that expose WCF services built on .NET 3.0. The content for this article is based on Chapter 10 of Pro WCF : Practical Microsoft SOA Implementation by APress. This book is targeted towards beginner to intermediate readers and part of Apress series that discusses WPF, WCF and WF. (30 printed pages) Contents
.NET Enterprise Services and COM+ Components Consuming WCF Services from COM+
Introduced in 1993, Component Object Model (COM) was the basis for other emerging technologies from Microsoft such as Object Linking and Embedding (OLE), ActiveX, and Distributed COM (DCOM). COM was initially introduced to compete with Common Object Request Broker Architecture (CORBA), a language-independent and cross-platform distributed system technology. They did share some core principles, but they were not compatible. Concepts and techniques such as Interface Definition Language (IDL) are present in both technologies. However, binary interoperability didn’t exist.
Read more: MSDN
Revised August 2007Applies to:
Microsoft .NET Framework 3.0
Windows Vista
Microsoft Internet Information Services
Microsoft Visual Studio 2005Summary: This article will detail step by step instructions to consume COM+ application services from WCF clients. We will also discuss how legacy applications can use applications that expose WCF services built on .NET 3.0. The content for this article is based on Chapter 10 of Pro WCF : Practical Microsoft SOA Implementation by APress. This book is targeted towards beginner to intermediate readers and part of Apress series that discusses WPF, WCF and WF. (30 printed pages) Contents
- Integrating WCF Services with COM+
- Running a COM+ Application as a WCF Service
- COM+ Application WCF Service Wrapper
- Using SvcConfigEditor.exe Utility
- Using ComSvcConfig.exe Utility
- Client Proxy Generation
- Visual Basic 6 COM+ Hiding Interfaces
- Client Proxy generation
- Typed Contract Service Moniker
- Metadata Exchange Contract Service Moniker
- WSDL Contract Service Moniker
Introduced in 1993, Component Object Model (COM) was the basis for other emerging technologies from Microsoft such as Object Linking and Embedding (OLE), ActiveX, and Distributed COM (DCOM). COM was initially introduced to compete with Common Object Request Broker Architecture (CORBA), a language-independent and cross-platform distributed system technology. They did share some core principles, but they were not compatible. Concepts and techniques such as Interface Definition Language (IDL) are present in both technologies. However, binary interoperability didn’t exist.
Read more: MSDN
Posts
0 comments:
Post a Comment