Export (0) Print
Expand All

[MS-DCOM]: Distributed Component Object Model (DCOM) Remote Protocol Specification

Click here to view this version of the [MS-DCOM] PDF.

Click here to download a zip file with all of the PDF files.

Intellectual Property Rights Notice for Protocol Documentation

  • Copyrights. This protocol documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the protocols, and may distribute portions of it in your implementations of the protocols or your documentation as necessary to properly document the implementation. This permission also applies to any documents that are referenced in the protocol documentation.
  • No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
  • Patents. Microsoft has patents that may cover your implementations of the protocols. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, the protocols may be covered by Microsoft’s Open Specification Promise (available here: http://www.microsoft.com/interop/osp). If you would prefer a written license, or if the protocols are not covered by the OSP, patent licenses are available by contacting protocol@microsoft.com.
  • Trademarks. The names of companies and products contained in this documentation may be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights.

Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than specifically described above, whether by implication, estoppel, or otherwise.

Tools. This protocol documentation is intended for use in conjunction with publicly available standard specifications and network programming art, and assumes that the reader either is familiar with the aforementioned material or has immediate access to it. A protocol specification does not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments you are free to take advantage of them.

Revision Summary
Date Revision History Revision Class Comments

03/14/2007

1.0

Version 1.0 release

04/10/2007

1.1

Version 1.1 release

05/18/2007

1.2

Version 1.2 release

06/08/2007

1.2.1

Editorial

Revised and edited the technical content.

07/10/2007

2.0

Major

Converted to unified format; updated technical content.

08/17/2007

3.0

Major

Updated and revised the technical content.

09/21/2007

4.0

Major

Added an interface.

10/26/2007

4.0.1

Editorial

Revised and edited the technical content.

01/25/2008

4.0.2

Editorial

Revised and edited the technical content.

03/14/2008

4.1

Minor

Updated the technical content.

06/20/2008

5.0

Major

Updated and revised the technical content.

07/25/2008

5.1

Minor

Updated the technical content.

08/29/2008

6.0

Major

Updated and revised the technical content.

10/24/2008

6.1

Minor

Updated the technical content.

Show:
© 2014 Microsoft