You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/communication-services/how-tos/calling-sdk/includes/manage-video/manage-video-windows.md
+13-12Lines changed: 13 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,16 +9,17 @@ ms.author: rifox
9
9
10
10
### Request access to the microphone
11
11
12
-
The app will require access to the camera to run properly. In UWP apps, the camera capability should be declared in the app manifest file.
13
-
he following steps exemplify how to achieve that.
12
+
The app requires access to the camera to run properly. In UWP apps, the camera capability should be declared in the app manifest file.
13
+
14
+
The following steps exemplify how to achieve that.
14
15
15
16
1. In the `Solution Explorer` panel, double click on the file with `.appxmanifest` extension.
16
17
2. Click on the `Capabilities` tab.
17
18
3. Select the `Camera` check box from the capabilities list.
18
19
19
20
### Create UI buttons to place and hang up the call
20
21
21
-
This simple sample app will contain two buttons. One for placing the call and another to hang up a placed call.
22
+
This simple sample app contains two buttons. One for placing the call and another to hang up a placed call.
22
23
The following steps exemplify how to add these buttons to the app.
23
24
24
25
1. In the `Solution Explorer` panel, double click on the file named `MainPage.xaml` for UWP, or `MainWindows.xaml` for WinUI 3.
@@ -46,14 +47,14 @@ using Azure.Communication;
46
47
usingAzure.Communication.Calling;
47
48
```
48
49
49
-
Please keep`MainPage.xaml.cs` or `MainWindows.xaml.cs` open. The next steps will add more code to it.
50
+
Keep`MainPage.xaml.cs` or `MainWindows.xaml.cs` open. The next steps will add more code to it.
50
51
51
52
## Allow app interactions
52
53
53
54
The UI buttons previously added need to operate on top of a placed `Call`. It means that a `Call` data member should be added to the `MainPage` or `MainWindow` class.
54
55
Additionally, to allow the asynchronous operation creating `CallAgent` to succeed, a `CallAgent` data member should also be added to the same class.
55
56
56
-
Please add the following data members to the `MainPage` or `MainWindow` class:
57
+
Add the following data members to the `MainPage` or `MainWindow` class:
57
58
```csharp
58
59
CallAgentcallAgent;
59
60
Callcall;
@@ -91,8 +92,8 @@ The following classes and interfaces handle some of the major features of the Az
91
92
92
93
## Register video handler
93
94
94
-
A UI component, like XAML's MediaElement or MediaPlayerElement, will require the app registering a configuration for rendering local and remote video feeds.
95
-
Please add the following content between the `Package` tags of the `Package.appxmanifest`:
95
+
A UI component, like XAML's MediaElement or MediaPlayerElement, you need the app registering a configuration for rendering local and remote video feeds.
96
+
Add the following content between the `Package` tags of the `Package.appxmanifest`:
96
97
97
98
```xml
98
99
<Extensions>
@@ -107,7 +108,7 @@ Please add the following content between the `Package` tags of the `Package.appx
107
108
108
109
## Initialize the CallAgent
109
110
110
-
To create a `CallAgent` instance from `CallClient` you must use `CallClient.CreateCallAgent` method that asynchronously returns a `CallAgent` object once it is initialized.
111
+
To create a `CallAgent` instance from `CallClient`, you must use `CallClient.CreateCallAgent` method that asynchronously returns a `CallAgent` object once it's initialized.
111
112
112
113
To create `CallAgent`, you must pass a `CommunicationTokenCredential` object and a `CallAgentOptions` object. Keep in mind that `CommunicationTokenCredential` throws if a malformed token is passed.
`<AUTHENTICATION_TOKEN>`must be replaced by a valid credential token for your resource. Refer to the [user access token](../../../../quickstarts/identity/access-tokens.md) documentation if a credential token has to be sourced.
132
+
Change the `<AUTHENTICATION_TOKEN>`with a valid credential token for your resource. Refer to the [user access token](../../../../quickstarts/identity/access-tokens.md) documentation if a credential token has to be sourced.
132
133
133
134
## Place a 1:1 call with video camera
134
135
135
-
The objects needed for creating a `CallAgent` are now ready. It is time to asynchronously create `CallAgent` and place a video call.
136
+
The objects needed for creating a `CallAgent` are now ready. It's time to asynchronously create `CallAgent` and place a video call.
136
137
137
138
The following code should be added after handling the exception from the previous step.
Make sure Visual Studio will build the app for `x64`, `x86` or `ARM64`, then hit `F5` to start running the app. After that, click on the `Call` button to place a call to the callee defined.
286
+
Make sure Visual Studio builds the app for `x64`, `x86` or `ARM64`, then hit `F5` to start running the app. After that, click on the `Call` button to place a call to the callee defined.
286
287
287
-
Keep in mind that the first time the app runs, the system will prompt user for granting access to the microphone.
288
+
Keep in mind that the first time the app runs, the system prompts user for granting access to the microphone.
0 commit comments