Export (0) Print
Expand All

CommunicationObject.Open Method

Causes a communication object to transition from the created state into the opened state.

Namespace:  System.ServiceModel.Channels
Assembly:  System.ServiceModel (in System.ServiceModel.dll)

'Declaration
Public Sub Open

Implements

ICommunicationObject.Open

ExceptionCondition
InvalidOperationException

The communication object is not in a Opened or Opening state and cannot be modified.

ObjectDisposedException

The communication object is in a Closing or Closed state and cannot be modified.

CommunicationObjectFaultedException

The communication object is in a Faulted state and cannot be modified.

TimeoutException

The default interval of time that was allotted for the operation was exceeded before the operation was completed.

When a CommunicationObject is instantiated, it begins in the Created state. In the Created state, the object can be configured (for example, properties can be set, or events can be registered), but it is not yet usable to send or receive messages. When called, the Open method causes a CommunicationObject to enter into the Opening state and calls OnOpening, Open, and OnOpened. The OnOpened method completes the Open method by setting the state of the object to the Opened state.

In the

Opened state, the CommunicationObjectis usable (for example, messages can be received), but it is no longer configurable.

There is also an asynchronous version of the open method that is initiated by calling OnBeginOpen(TimeSpan, AsyncCallback, Object) and completed by calling EndOpen.

Credentials Capture with Windows Authentication

When using Windows authentication, credentials used by the service are based on the current context thread. The credentials are obtained when the Open method is called.

NoteNote

For asynchronous calls, credentials are captured when the BeginOpen is invoked. However, the actual credentials cannot be guaranteed. That is, the credentials of the caller may be switched to another identity. For more information, see Message Security with a Windows Client.

.NET Framework

Supported in: 4, 3.5, 3.0

.NET Framework Client Profile

Supported in: 4, 3.5 SP1

Portable Class Library

Supported in: Portable Class Library

Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2

The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.

Community Additions

ADD
Show:
© 2014 Microsoft