Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
A version of this page is also available for
4/8/2010

Notifies the container that one of its objects is being activated in place.

Syntax

HRESULT OnInPlaceActivate();

Return Value

This method supports the following return values:

Value Description

S_OK

The container allows the in-place activation.

E_UNEXPECTED

The call to the method unexpectedly failed.

Notes to Callers

IOleInPlaceSite::OnInPlaceActivateis called by the active embedded object when it is activated in-place for the first time. The container should note that the object is becoming active.

Notes to Implementers

A container that supports linking to embedded objects must properly manage the running of its in-place objects when they are UI-inactive and running in the hidden state. To reactivate the in-place object quickly, a container should not call IOleObject::Closeuntil the container's IOleInPlaceSite::DeactivateAndUndomethod is called. To help protect against the object being left in an unstable state if a linking client updates silently, the container should call OleLockRunningto lock the object in the running state. This prevents the hidden in-place object from shutting down before it can be saved in its container.

Requirements

Header Oleidl.h
Windows Embedded CE Windows CE .NET 4.0 and later
Windows Mobile Windows Mobile Version 5.0 and later

See Also

Reference

IOleInPlaceSite

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.