CameraCaptureTask Class
July 26, 2012
Allows an application to launch the Camera application. Use this to allow users to take a photo from your application.
Microsoft.Phone.Tasks.ChooserBase<PhotoResult>
Microsoft.Phone.Tasks.CameraCaptureTask
Assembly: Microsoft.Phone (in Microsoft.Phone.dll)
XMLNS for XAML: Not mapped to an xmlns.
The CameraCaptureTask type exposes the following members.
| Name | Description | |
|---|---|---|
 | TaskEventArgs | The EventArgs for the Completed event. (Inherited from ChooserBase<TTaskEventArgs>.) |
| Name | Description | |
|---|---|---|
| Equals | (Inherited from Object.) |
| Finalize | (Inherited from Object.) |
| FireCompleted | Raises the Completed event. (Inherited from ChooserBase<TTaskEventArgs>.) |
| GetHashCode | (Inherited from Object.) |
| GetType | (Inherited from Object.) |
| MemberwiseClone | (Inherited from Object.) |
| Show | Shows the Camera application. (Overrides ChooserBase<TTaskEventArgs>.Show().) |
| ToString | (Inherited from Object.) |
| Name | Description | |
|---|---|---|
| Completed | Occurs when a Chooser task is completed. (Inherited from ChooserBase<TTaskEventArgs>.) |
Launch the Camera application by calling the Show method of the CameraCaptureTask object. Obtain the result of the chooser operation by handling the Completed event.
| Important Note: |
|---|
On Windows Phone, your application may be deactivated while the Camera application is in the foreground. To ensure that your application receives the result of the CameraCaptureTask, the object must be declared with class scope within the PhoneApplicationPage class and you must call the chooser constructor and assign the Completed event delegate within the page’s constructor. For more information about how to handle the activation and deactivation of your application, see Execution Model for Windows Phone. |
Memory allocated for the Camera Capture Task does not count toward total application memory use. This helps minimize the amount of memory your application uses to capture photos, which is particularly important when your application runs on a 256-MB device. For more information, see Developing for 256-MB Devices.
